Nameserver not resolving working domain

Gilles Massen gm at
Wed Nov 15 10:22:17 UTC 2006


I have a weird issue with a bind9 resolver: it fails to resolve a domainname 
that appears to be absolutely correctly configured (and which works correctly 
from another bind9 server). I even expect it to work after restarting Bind, 
but I don't want to do it yet in sake of finding what is wrong.

The host I cannot resolve is, returning no answer.
The domain is delegated to ns19 +  Both are reachable. From 
the nameserver:

ns:/usr/local/named-ns/var/log # dig @localhost

; <<>> DiG 9.3.2-P1 <<>> @localhost
; (2 servers found)
;; global options:  printcmd
;; connection timed out; no servers could be reached
ns:/usr/local/named-ns/var/log # dig

; <<>> DiG 9.3.2-P1 <<>>
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23910
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;         IN      A

;; ANSWER SECTION:  7200    IN      A

;; AUTHORITY SECTION:      7200    IN      NS      7200    IN      NS

;; Query time: 111 msec
;; WHEN: Wed Nov 15 11:18:38 2006
;; MSG SIZE  rcvd: 102

Where could this go wrong? Our firewall isn't logging anything. Everyone is 
reachable, even through IPv6 (the only IPv6 addresses involved being those 
for a +

Any hint to what to try, before I have to restart bind, would be much 

Best regards,
Gilles Massen

More information about the bind-users mailing list