<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
FWIW, we've encountered this same problem before, and the only
actual resolver I've seen affected is Google DNS.<br>
The Google resolver seems awfully sensitive to the actual NS records
returned by the target DNS server.<br>
<br>
You'll notice that with this configuration, a dig at 8.8.8.8 for
sunatraffic.com.au fails.<br>
<br>
Kind regards,<br>
James 'Ender' Brown<br>
Systems Administrator,<br>
HostAway Pty Ltd<br>
<br>
<span style="color:#44546A"><o:p> </o:p></span>
<blockquote
cite="mid:8CEF048B9EC83748B1517DC64EA130FB76F44EB9FC@off-win2003-01.ausregistrygroup.local"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#44546A">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).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#44546A"><o:p> </o:p></span></p>
<br>
</div>
</blockquote>
<br>
</body>
</html>