[AusNOG] AusRegistry

[Wolfgang Nagele]

Hi,

This might be a complete issue with Google. See the thread on NANOG:
http://mailman.nanog.org/pipermail/nanog/2013-May/058132.html

Regards,

-- 
Wolfgang Nagele
IT Services Manager
AusRegistry Pty Ltd
Level 8, 10 Queens Road
Melbourne, Victoria, Australia, 3004
Phone +61 3 9090 1756
Email: wolfgang.nagele at ausregistry.com.au
Web: www.ausregistry.com.au


The information contained in this communication is intended for the named
recipients only. It is subject to copyright and may contain legally
privileged and confidential information and if you are not an intended
recipient you must not use, copy, distribute or take any action in
reliance on it. If you have received this communication in error, please
delete all copies from your system and notify us immediately.


On 5/3/13 1:02 PM, "Chris Wright" <chris at ausregistry.com.au> wrote:

>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).
> 
> 
>
> 
>