BIND Lameness

Keith Burgoyne keith at
Tue Apr 3 02:37:23 UTC 2012

Hi all,

I have what, I hope, will be a rather quick question regarding 'lame 
server resolving' errors.

I've recently replaced the master server at, and am now 
running bind 9.7.3.

My question is: I keep seeing log entries like

Apr  2 23:24:17 clementine named[5870]: lame server resolving 
'' (in ''?):
Apr  2 23:24:01 clementine named[5870]: lame server resolving 
'' (in ''?):

and the list goes on. I don't get a lot, probably a few a minute. But 
where do they come from? It's my understanding that they originate from 
a name server that's not configured to be authoritative for a domain, 
yet listed as such. Both of the domains above have as the 
authoritative name server and, as far as I know, the bind install is 
configured as such.

Each time I dig, say,, I get an authoritative answer from 
that server:


; <<>> DiG 9.3.3 <<>>
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61939
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3

;                    IN      A

;; ANSWER SECTION:             600     IN      A

;; AUTHORITY SECTION:             600     IN      NS             600     IN      NS             600     IN      NS

;; ADDITIONAL SECTION:   1800    IN      A   1800    IN      A   1800    IN      A

;; Query time: 15 msec
;; WHEN: Mon Apr  2 23:30:27 2012
;; MSG SIZE  rcvd: 159

So it's clearly showing up as the authoritative server. Hence, I can't 
figure out why those log entries are showing up. I've disabled ipv6 for 
now, using the "-4" option. I heard that can help.

Any pointers would be massively appreciated!



More information about the bind-users mailing list