[Dibbler] RHEL domain search paths

Wiegand, Steven Steven.Wiegand at NGC.com
Tue Jun 6 22:03:21 CEST 2006


When the dibbler client is run on my Linux system with the /usr/sbin/dibbler-client run command, I receive the desired DNS server information and the domain information configured in the server.conf file.  I'm good up until here.   The three domains are put into the file on separate lines with the search option before each line:

 

/etc/resolv.conf

nameserver   8000:0:0:802:20f:20ff:fe98:8663

nameserver   8000:0:0:802:20f:20ff:fe98:46d3

search hawk.bird.root.com

search dog.root.com

search root.com

 

This causes some of my applications to behave in a strange way.  If I use ping6 <hostname>, the hostname will only be queried with the root.com domain appended, the last domain in the list.  When I put all the domains on the same line with one search, it works fine.  Some applications work different.  nslookup -type=AAAA <hostname> works fine.  The man page for resolv.conf states "List each domain following the search keyword with spaces or tabs between them" (more detail below).  I noticed that the code individually configures each domain to a separate line (output of the dibbler-client run below)

 

I also noticed that the GUI does not get updated.  The Primary DNS, Secondary DNS, Tertiary DNS, and DNS search path text fields remain blank. (I don't think this will cause any problems, but it would be nice if it showed the true configuration.

 

VERSIONS:

Version of RHEL:           2.6.9-5.EL

Version of Dibbler:          0.4.1

 

PLATFORMS

Dibbler Server is running on a Windows 2003 Server

Dibbler Client is running on a RHEL system

 

Dibbler Server config:

option dns-server 8000:0:0:802:20f:20ff:fe98:8663, 8000:0:0:802:20f:20ff:fe98:46d3

option domain hawk.bird.root.com, dog.root.com, root.com

 

 

Output of the dibbler-client run command:

2006.06.06 15:40:29 Client Debug     Received 212 bytes on interface eth0/2 (socket=6, addr=fe80::213:c4ff:fec1:8db8.).

2006.06.06 15:40:29 Client Notice    Received REPLY on eth0/2,TransID=0x8aea35, 6 opts: 2 14 1 3 23 24

2006.06.06 15:40:29 Client Notice    Address 8000:0:0:803::10 added to eth0/2 interface.

2006.06.06 15:40:29 Client Notice    Setting up DNS server 8000::802:20f:20ff:fe98:8663 on interface eth0/2.

2006.06.06 15:40:29 Client Notice    Setting up DNS server 8000::802:20f:20ff:fe98:46d3 on interface eth0/2.

2006.06.06 15:40:29 Client Notice    Setting up Domain hawk.bird.root.com on interface eth0/2.

2006.06.06 15:40:29 Client Notice    Setting up Domain dog.root.com on interface eth0/2.

2006.06.06 15:40:29 Client Notice    Setting up Domain root.com on interface eth0/2.

2006.06.06 15:40:29 Client Notice    Sleeping for 1 second(s).

2006.06.06 15:40:30 Client Notice    Sleeping for 1 second(s).

2006.06.06 15:40:31 Client Debug     DAD finished successfully. Address 8000:0:0:803::10 is not tentative.

2006.06.06 15:40:31 Client Notice    Sleeping for 1798 second(s).

 

 

man resolv.conf:

search      Domain(s) to use for DNS lookups when no domain is speci-

                 fied. List each domain following the search keyword with

                 spaces or tabs between them. Each possible domain will be

                 checked in order until a match is found. Note that this pro-

                 cess may be slow (queries will time out if no server is

                 available for a domain) and will generate a lot of network

                 traffic if the servers for the listed domains arenâEUR(tm)t local.

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: /lists/dibbler/attachments/20060606/be849c70/attachment.html 


More information about the Dibbler mailing list