LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Red Hat
User Name
Password
Red Hat This forum is for the discussion of Red Hat Linux.

Notices

Reply
 
Search this Thread
Old 07-18-2012, 10:58 AM   #1
dafydd2277
Member
 
Registered: Mar 2010
Posts: 58

Rep: Reputation: 5
Known RHEL5 IPv6 resolver bug.


Good Morning!

I can demonstrate this behavior in RHEL5, and demonstrate that it doesn't exist in RHEL6. Ergo, this is a known bug that's been fixed. Now, I need to document that fact!

Of course, for the life of me, I can't find the bug.

Basically, under certain circumstances, the RHEL5 resolver will ignore the ndots value when making AAAA queries. This leads to seeing queries with multiple q.d.n's attached. (And, of course, this won't show up with host, dig, nslookup, etc. I had to get one of the Java guys to whip up a little .jar that calls InetAddress.getByName).

For context, my /etc/resolv.conf contains a search line of "mid.top bot1.mid.top bot2.mid.top bot3.mid.top."

Search "host.bot1.mid.top" and bind receives these requests

query: host.bot1.mid.top IN AAAA +
query: host.bot1.mid.top.mid.top IN AAAA +
query: host.bot1.mid.top.mid.top IN AAAA -E
query: host.bot1.mid.top.mid.top IN AAAA -E
query: host.bot1.mid.top.mid.top IN AAAA +
query: host.bot1.mid.top.mid.top IN AAAA -E
query: host.bot1.mid.top.mid.top IN AAAA -E
query: host.bot1.mid.top.bot2.mid.top IN AAAA +
query: host.bot1.mid.top.bot1.mid.top IN AAAA +
query: host.bot1.mid.top.bot3.mid.top IN AAAA +
query: host.bot1.mid.top IN A +


Search "host:"

host.mid.top IN AAAA +
host.bot1.mid.top IN AAAA +
host.bot2.mid.top IN AAAA +
host.bot3.mid.top IN AAAA +
host.mid.top IN A +


Search "host.bot1.mid.top." with the dot on the end:

host.bot1.mid.top IN A +
host.bot1.mid.top IN AAAA +
host.bot1.mid.top IN A +


This only appears to apply to IPv6 requests handled directly by the resolver in RHEL5.

Does this look familiar to anyone? I need to track down any existing bug number for this behavior.

Thanks!
dafydd
 
Old 07-18-2012, 06:32 PM   #2
unSpawn
Moderator
 
Registered: May 2001
Posts: 26,944
Blog Entries: 54

Rep: Reputation: 2731Reputation: 2731Reputation: 2731Reputation: 2731Reputation: 2731Reputation: 2731Reputation: 2731Reputation: 2731Reputation: 2731Reputation: 2731Reputation: 2731
When you're saying "handled directly by the resolver" do you mean that as in 'man 5 resolver'? If that's the case then look at Glibc first?
 
  


Reply

Tags
dns


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Another IPv6 Crash Course For Linux: Real IPv6 Addresses, Routing, Name Services LXer Syndicated Linux News 0 04-21-2011 07:40 AM
slackware64-current glibc resolver bug? fancylad Slackware 8 01-31-2010 04:47 PM
BIND9 as forwarder, IPv6 queries from IPv6 forwarders Nonoo Linux - Server 1 11-23-2009 01:57 PM
How to configure DHCP server in ipv6 on RHEL5 mailme.prio Linux - Newbie 4 12-05-2008 04:49 PM
Bind 9 resolver? oddo Linux - Networking 3 08-30-2004 06:31 PM


All times are GMT -5. The time now is 03:46 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration