[dns-operations] Hearing first complains about failing internal resolving due to .prod TLD

Paul Ferguson fergdawgster at mykolab.com
Fri Sep 12 02:17:38 UTC 2014

Hash: SHA256



- - ferg

On 9/11/2014 6:58 PM, Joshua Smith wrote:

> Probably something I should know. But what's the best way to get
> notified of new TLDs coming online to help arm the NOC?
> -- Josh Smith KD8HRX
> Email/jabber: juicewvu at gmail.com Phone: 304.237.9369(c)
> Sent from my iPhone.
>> On Sep 11, 2014, at 9:32 PM, Paul Vixie <paul at redbarn.org>
>> wrote:
>>> On 9/11/2014 6:30 PM, Paul Vixie wrote:
>>> ... i have a lot of data but no obvious way to distill this 
>>> determination out of it.
>> as to this part, let me quote what i said on another mailing
>> list earlier today, on a similar thread (.PROD collisions):
>> On 9/11/2014 2:57 PM, Paul Vixie wrote:
>>>> ...
>>> so, we (farsight security; home of SIE and DNSDB) do not
>>> currently store or measure NXDOMAIN traffic, but it has seemed
>>> to me that with ~350 name servers sending us ~150K cache miss
>>> transactions per second, we ought to be able to see contrails
>>> from gTLD collisions.
>>> if anybody has a proposal for a (not-for-fee) experiment, or 
>>> (not-for-fee) continuous monitoring, i'm all ears.
>>> vixie
>> that offer is generally open to unfunded nonprofit DNS
>> researchers who want to help study collisions. contact me
>> directly if you're interested.
>> vixie _______________________________________________

- -- 
Paul Ferguson
VP Threat Intelligence, IID
PGP Public Key ID: 0x54DC85B2
Key fingerprint: 19EC 2945 FEE8 D6C8 58A1 CE53 2896 AC75 54DC 85B2
Version: GnuPG v2


More information about the dns-operations mailing list