and bind8/9

Dirk Janssen dirk at
Mon Dec 6 13:56:56 UTC 2004


> is delegated to 4 nameservers
> ({uk,de,fr,se}, but each of them only publishes a
> single {uk,de,fr,se} NS record for the zone. In
> other words, if you happen to query, say, for
> the NS record of the zone, it would respond with
> only an NS record pointing to 

they have (semi-)fixed the problem already at the time you wrote your
post, now they point at least to _one_ existing host.

At the time I wrote my posting the situation was this:

# dig ns

; <<>> DiG 8.3 <<>> ns 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60330
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;;, type = NS, class = IN


The unresolvable host (no A-Record)
was the reason for the timeout of bind8.
Now after the correction, there is no timeout issue anymore. 

But your absolutly right with this one:

> Ultimately, needs to fix either their delegations or
> their in-zone NS records for The in-zone NS records
> should match the delegation NS records. At a bare minimum, they need to
> follow Internet standards and publish at least 2 NS'es for the zone.



More information about the bind-users mailing list