bind 9.7.2-P3 does not resolve

Lazy lazy404 at
Thu Dec 30 16:43:18 UTC 2010

2010/12/28 Dennis Clarke <dclarke at>:
>>> trying to resolve or results in a
>>> "connection timed out; no servers could be reached"
>> Well, for what it's worth - it's not just you having that issue. When
>> testing from home and from work I get the same.
> works fine for me on linux and Solaris.

how does dig ANY looks on your site ?

when I query ie google's public dns resolver I get

$ dig ANY @

; <<>> DiG 9.6-ESV-R3 <<>> ANY @
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52638
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 0

;                 IN      ANY

;; ANSWER SECTION:          3185    IN      A          3185    IN      A          85985   IN      NS          85985   IN      NS          85985   IN      NS          85985   IN      NS          85985   IN      NS          3185    IN      SOA 2010122201 300 600 2419200 3600          3185    IN      MX      10          3185    IN      TXT

;; Query time: 36 msec
;; WHEN: Thu Dec 30 17:07:20 2010
;; MSG SIZE  rcvd: 336

this is missing second TXT spf record

bind and powerdns-recursor seems to reply with all records for they have, so if You earlier request for A and TXT you
get A and TXT from your local resolver despite that m$ servers sent
truncated answers for ANY queries that got ignored by bind, and didn't
provide TCP so I guess all you see is Your local cache made form
previous non ANY queries

Response for dig ANY varies significantly across dns
servers, sometimes we get TXT records, sometime we don't, some don't
have SOA ect.


More information about the bind-users mailing list