Sponsored Content
Full Discussion: DNS Server with IPv6 support
Special Forums IP Networking DNS Server with IPv6 support Post 302123748 by skanatiker on Wednesday 27th of June 2007 04:10:40 AM
Old 06-27-2007
Thanks a lot for your answers so far.

Here is my output from the following command

netstat -ant -f inet6| grep "\.53":
Code:
tcp6       0      0  *.53                   *.*                    LISTEN
udp6    4142      0  *.53                   *.*

tcpdump is available on my machine. I have played around a bit with tcpdump, but i didn't find anything interesting in the output. Which parameters should i use to start tcpdump with?

In my named.conf i have set the listen-on-v6 directive to any.

And @porter: Thanks for the information. But i wasn't able to determine whether aix uses the parallel stack or unified stack approach. And if it uses the unified stack approach, where do i have to set the SO_REUSEADDR flag?


Another thing i'm not sure about is ip6.arpa zone. Do i need this zone at all? Does IPv6 not work without a correct ip6.arpa? It is only there for the reverse lookup, isn't it? so the dig request i had sent should also have been executed without the zone, or? Well, if i need it, how should it look like? I use one at the moment, and it is also loaded without any errors, but well, i'm not sure whether it is correct.

Are there any other zones that are necessary for IPv6 to work? So only the basic ones. I have a zone where my AAAA records are in.


I found out something very interesting now. When i execute "dig @::1 host1.v6mainzlab.com aaaa" the first time, i get an error in my bind.log. I have turned on logging in named.conf. The error is the following:

Code:
27-Jun-2007 10:24:03.450 general: error: client.c:1575: unexpected error:
27-Jun-2007 10:24:03.450 general: error: failed to get request's destination: failure
27-Jun-2007 10:24:08.458 general: error: client.c:1575: unexpected error:
27-Jun-2007 10:24:08.459 general: error: failed to get request's destination: failure

--------EDIT---------
I have played around a bit and tried to get the dns server started on another AIX 5.3 machine. There i have Bind 9.2.1 installed. It's the default package that comes with AIX 5.3. When i started bind i got an error message in the system log. He couldn't bind the IPv4 socket, because it is already in use. So, well, i think now we know, that AIX uses unified stack. Now i would have to know, where i have to set the flag SO_REUSEADDR. Just for testing i have set the dns not to listen on IPv4 by setting "listen-on port 53 {none};" in named.conf (btw - i did the same on the other machine with Bind 9.4.1 and it didn't work there).

On that machine, all my dig commands work fine now. I have changed /etc/resolv.conf to the following:
Code:
nameserver ::1
search v6.mainzlab.com

But when i want to ping host1 or host1.v6mainzlab.com the host cannot be found. Any ideas what is the problem here?

Last edited by skanatiker; 06-27-2007 at 06:18 AM.. Reason: set up dns on another machine
 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

2. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

3. Solaris

NTP server to support IPv4 and IPv6 client

Hi I am looking to have an NTP server that will support both ipv4 and ipv6 clients. Is there anything specific about the configuration that I should be looking at? (7 Replies)
Discussion started by: eeisken
7 Replies

4. Solaris

checking Solaris 10 DNS server for IPv6

hi, i have a Solaris 10 DNS server, how do you check whether it can support IPv6 networking ? (0 Replies)
Discussion started by: Exposure
0 Replies

5. Solaris

IPv6 for Solaris DNS

I have Bind running on a Solaris box that is our main public DNS. Given my very limited knowledge on DNS, I changed a few of the zones in the DNS to be 'dual-stack'. I did it through Webmin, but I know that I can also do it by adding an AAAA-record to the zone file. My question is how can I make... (2 Replies)
Discussion started by: Dardeer
2 Replies

6. IP Networking

[ipv6_test] Kernel is not compiled with IPv6 support

Hello, i tried to enable IPv6 networking and after service network restart i seen these messages: FATAL: Error inserting ipv6 (/lib/modules/2.6.18-348.16.1.el5.028stab108.1/kernel/net/ipv6/ipv6.ko): Device or resource busy CRITICAL : Kernel is not compiled with IPv6 support Bringing up... (6 Replies)
Discussion started by: postcd
6 Replies

7. UNIX for Dummies Questions & Answers

Assigning ipv6 to bonding interface - getting old as well as changed ipv6 in ifconfig output

Hi, I have created a bonding bond1 interface with 6 Eth , mode=4. Recently i have changed my old ipv6 to new one and tried to restart as well as reload network service. Post which i can see old as well as changed ipv6 in ifconfig command output. Below are few files and command output for your... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies

8. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies

9. UNIX for Beginners Questions & Answers

What determines DNS will query IPV6 address?

When I do simple nslookup it does not generate any query for IPV6 (AAAA). But sometimes I see DNS query for both A and AAAA are generated. What decides this? The reason I do not want AAAA query is in most of the cases AAAA records are absent. Hence, if one DNS server fails, the clients keeps... (1 Reply)
Discussion started by: broy32000
1 Replies
YPBIND(8)							     ypbind-mt								 YPBIND(8)

NAME
ypbind - NIS binding process SYNOPSIS
ypbind [-c] [-d | -debug] [-verbose] [-broadcast] [-broken-server] [-ypset] [-ypsetme] [-no-ping] [-f configfile] [-local-only] [-ping-interval ping-interval] [-no-dbus] ypbind --version DESCRIPTION
ypbind finds the server for NIS domains and maintains the NIS binding information. The client (normally the NIS routines in the standard C library) could get the information over RPC from ypbind or read the binding files. The binding files resides in the directory /var/yp/binding and are conventionally named [domainname].[version]. The supported versions are 1 and 2. There could be several such files since it is possible for an NIS client to be bound to more than one domain. After a binding has been established, ypbind will send YPPROC_DOMAIN requests to the current NIS server at 20 seconds intervals. If it doesn't get an response or the NIS server reports that he doesn't have this domain any longer, ypbind will search for a new NIS server. All 15 minutes ypbind will check to see if the current NIS server is the fastest. If it find a server which answers faster, it will switch to this server. You could tell ypbind to use network broadcasts to find a new server, what is insecure, or you could give it a list of known secure servers. In this case ypbind will send a ping to all servers and binds to first one which answers. Unless the option -debug is used, ypbind detaches itself from the controlling terminal and puts itself into background. ypbind uses syslog(3) for logging errors and warnings. At startup or when receiving signal SIGHUP, ypbind parses the file /etc/yp.conf and tries to use the entries for its initial binding. A broadcast entry in the configuration file will overwrite a ypserver/server entry and a ypserver/server entry broadcast. If all given server are down, ypbind will not switch to use broadcast. ypbind will try at first /etc/hosts and then DNS for resolving the hosts names from /etc/yp.conf. If ypbind couldn't reconfigure the search order, it will use only DNS. If DNS isn't available, you could only use IP-addresses in /etc/hosts. ypbind could only reconfigure the search order with glibc 2.x. If the -broadcast option is specified, ypbind will ignore the configuration file. If the file does not exist or if there are no valid entries, ypbind exit. This ypbind version listens for DBUS messages from NetworkManager. If no NetworkManager is running at startup, ypbind will behave as usual and assumes there is a working network connection. If NetworkManager is running on the system, ypbind will only search and provide NIS informations, if NetworkManager tells that a network connection is available. If NetworkManager establishes a connection, ypbind will reread all configuration files, registers at the local portmapper and try to search NIS servers. If NetworkManager drops a connection, ypbind will unregister from portmapper. OPTIONS
-broadcast Send a broadcast to request the information needed to bind to a specific NIS server. With this option, /etc/yp.conf will be ignored. -ypset Allow root from any remote machine to change the binding for a domain via the ypset(8) command. By default, no one can change the binding. This option is really insecure. If you change a binding for a domain, all the current known servers for this domain will be forgotten. If the new server goes down, ypbind will use the old searchlist. -ypsetme The same as -ypset, but only root on the local machine is allowed to change the binding. Such requests are only allowed from loopback. -c ypbind only checks if the config file has syntax errors and exits. -debug starts ypbind in debug mode. ypbind will not put itself into background, and error messages and debug output are written to standard error. -verbose Causes ypbind to syslog(2) any and all changes in the server its bound to. -broken-server lets ypbind accept answers from servers running on an illegal port number. This should usually be avoided, but is required by some ypserv(8) versions. -no-ping ypbind will not check if the binding is alive. This option is for use with dialup connections to prevent ypbind from keeping the connection unnecessarily open or causing autodials. -f configfile ypbind will use configfile and not /etc/yp.conf -local-only ypbind will only bind to the loopback device and is not reachable from a remote network. -ping-interval ping-interval The default value for ypbind to check, if a NIS server is still reacheable, is 20 seconds. With this options another frequency in seconds can be specified. -no-dbus Disables DBUS support if compiled in. --version Prints the version number FILES
/etc/yp.conf configuration file. /var/yp/binding/[domainname].[version] binding file containing information about each NIS domain. /var/run/ypbind.pid contains the process id of the currently running ypbind master process. SEE ALSO
syslog(3), domainname(1), yp.conf(5), ypdomainname(8), ypwhich(1), ypserv(8), ypset(8) AUTHOR
ypbind-mt was written by Thorsten Kukuk <kukuk@thkukuk.de>. ypbind-mt 06/19/2009 YPBIND(8)
All times are GMT -4. The time now is 03:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy