This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/

[dns-wg] Analysis of Increased Query Load on Root Name Servers

Previous message (by thread): [dns-wg] Analysis of Increased Query Load on Root Name Servers
Next message (by thread): [dns-wg] Response size of JP's DNSKEY was changed

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Doug Barton dougb at dougbarton.us
Wed Jul 13 19:38:43 CEST 2011

On 07/13/2011 02:32, Emile Aben wrote:
> Yes, it was a different domain, not in COM.
> We asked folks that operate COM and they didn't see the same query-storm
> for this domain though. If these were all 'normal' resolvers dealing
> with a misconfigured zone, I'd expect them to follow the delegation
> chain. Also when spot-checking some 20 source IPs for these queries we
> didn't find these did any other queries to K-root then for things in
> <domain>.com.

Interesting stuff! Thanks for once again indulging my curiosity. I
always find it interesting when more data makes a problem muddier
instead of clearer. :)


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/

Previous message (by thread): [dns-wg] Analysis of Increased Query Load on Root Name Servers
Next message (by thread): [dns-wg] Response size of JP's DNSKEY was changed

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]