[Pdns-users] Odd Recursor/Authoritative problem with a private domain

Jeremy Utley pdns at gammanetworking.com
Thu Jul 21 18:33:15 UTC 2011


On 7/21/2011 1:14 PM, Stefan Schmidt wrote:
> On Thu, Jul 21, 2011 at 8:00 PM, Jeremy Utley<pdns at gammanetworking.com>  wrote:
>> gnint.prv=66.152.94.11, 66.152.94.12, 66.152.94.13
>> 10.in-addr.arpa=66.152.94.11, 66.152.94.12, 66.152.94.13
> ...
>> $ host gn-ldap01.gnint.prv
>> gn-ldap01.gnint.prv has address 10.1.20.1
>> Host gn-ldap01.gnint.prv not found: 3(NXDOMAIN)
>> Host gn-ldap01.gnint.prv not found: 3(NXDOMAIN)
> Are those machines maybe using some kind of asynchronous dns library?
Not to my knowledge.  The machines are bog standard CentOS 5.6 machines, 
using the stock "host" command that comes with CentOS 
(bind-utils-9.3.6-16.P1.el5  package).
> If you do a
> dig @<IP>  gn-ldap01.gnint.prv
> for each of your loadbalancer IPs does it show NXDOMAIN somewhere?
No it does not, running dig against both the recursors and the 
authoritative, whether going thru the load balancer, or directly to the 
machines, no NXDOMAIN responses are given.
> Also worth trying: Does ping gn-ldap01.gnint.prv work every time?
It's erratic.  I have seen pings fail due to failure to resolve the 
hostname, other times it works just fine.

Jeremy



More information about the Pdns-users mailing list