Recent problems with Reverse DNS.

[Barry Margolin]

In article <bhdtdp$251r$1 at sf1.isc.org>,
Brett Simpson  <simpsonb at hillsboroughcounty.org> wrote:
>Three weeks ago our internal clients were able to connect to hosts by ip 
>address quickly. Then we started noticing slow connection to various internal 
>host by IP address. If I add a host entry of my workstation to the server I'm 
>connecting to then things are fast again. Sounds like a Reverse DNS problem.
>So I updated our db.cache file (which contains the root servers) on both DNS 
>server and things seemed to be fast again after restarting Bind. But then 10 
>minutes later things slowed down again.
>Our hosts that have public IPs with FQDN are fine. Just the internal hosts 
>have problems.

If the internal hosts are using private addresses, then you need to have
local zone files for the reverse domains.  The nameservers that the RFC
1918 reverse domains are delegated to don't always respond in a timely
fashion.

-- 
Barry Margolin, barry.margolin at level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.