[AusNOG] AusRegistry

[Chris Wright]

Thanks James, this is useful information, I will see if I can get someone from google to look into it.

Thanks

Chris

From: Ender [mailto:ender at hostaway.net.au]
Sent: Friday, 3 May 2013 12:39 PM
To: Chris Wright
Cc: James Troy; ausnog at lists.ausnog.net
Subject: Re: [AusNOG] AusRegistry

Hi all,

FWIW, we've encountered this same problem before, and the only actual resolver I've seen affected is Google DNS.
The Google resolver seems awfully sensitive to the actual NS records returned by the target DNS server.

You'll notice that with this configuration, a dig at 8.8.8.8 for sunatraffic.com.au fails.

Kind regards,
 James 'Ender' Brown
 Systems Administrator,
 HostAway Pty Ltd


Now in normal circumstance, since the com.au zone has your domain delegated to ns[0-3].summitdns.com.au this wouldn't be a problem and the summithosting.com.au left over records wouldn't be a problem, however since summitdns.com.au is delegated to summithosting.com.au it appears some resolves are getting confused (perhaps they are buggy, I'm not sure why they are being confused and we haven't been able to replicate the problem and find any broken resolvers).



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20130503/69816573/attachment.html>