delegation only, uz. tld
Florian Weimer
fw at deneb.enyo.de
Wed Nov 8 21:08:23 UTC 2006
* Paul Vixie:
>> > that's just delegation data. can you show us some non-delegation content
>> > in that zone?
> ...
>> ;; ANSWER SECTION:
>> NS4.uz. 14400 IN A 87.139.124.237
>>
>> ;; AUTHORITY SECTION:
>> uz. 14400 IN NS ns5.uz.
>> uz. 14400 IN NS ns.uz.
>> uz. 14400 IN NS ns2.uz.
>> uz. 14400 IN NS ns3.uz.
>> uz. 14400 IN NS NS4.uz.
>>
>> ;; ADDITIONAL SECTION:
>> ns.uz. 14400 IN A 195.158.1.25
>> ns2.uz. 14400 IN A 81.95.224.158
>> ns3.uz. 14400 IN A 195.158.1.22
>> ns5.uz. 14400 IN A 217.12.81.129
>
> let's not exclude tld's from delegation-only just because they have in-zone
> nameservers.
These aren't just in-zone name servers (I think you mean "glue
records"), these are in-zone A records for which the SLD servers are
themselves authoritative.
> the additional data isn't what triggers the syslog, it's the
> direct-query-for-the-glue, which is usually avoidable.
Look at the answer section (and the AA flag you didn't quote). This
zone is definetely *not* delegation-only.
More information about the bind-users
mailing list