----- Original Message -----
From: "Len Conrad" <[EMAIL PROTECTED]>
> btw, apparently the registrars/registry operators for other .TLDs have
been
> raping their DNS for months, so you can nullify their TLD shenanigans also
> by the declaring all of them as "zone type delegation-only". In fact, I
> can't see why you should not set up ALL .TLDs as delegation-only.
>
> apropos:
>
> Reserach lifted from another mailing list:
>
> dnsqr a *.nu
> answer: \052.nu 86375 A 64.55.105.9
> answer: \052.nu 86375 A 212.181.91.6
>
> dnsqr a *.com
> answer: \052.com 167 A 64.94.110.11
>
> dnsqr a *.net
> answer: \052.net 211 A 64.94.110.11
>
> dnsqr a *.ac
> answer: \052.ac 86376 A 194.205.62.122
>
> dnsqr a *.museum
> answer: \052.museum 156 A 195.7.77.20
>
> dnsqr a *.cc
> answer: \052.cc 3577 A 206.253.214.102
>
> dnsqr a *.cx
> answer: \052.cx 86378 A 219.88.106.80
>
> dnsqr a *.tm
> answer: \052.tm 86378 A 194.205.62.42
This is from the Bind mailing list:
> Furthermore, it seems not only .com and .net include wildcards. It seems
> also .cc and so on have these. So is there a way to set up this
> delegation-only GLOBALY without having to specify each and every tld?
Nope, to quote Paul Vixie:
{
no. not just because that's not how our internal hashing works, but
because "hosted" tld's like .museum have had wildcards from day 1 and
the registrants there are perfectly comfortable with them. there's
no one-policy-fits-all when it comes to tld's, so we would not want
to offer a knob that tried to follow a single policy for all tld's.
}
Bill
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
