In message <[EMAIL PROTECTED]> "Nicholas Accad" <[EMAIL PROTECTED]> was claimed to have wrote:
>Hello Dave, > >In an offlist discussion with other people on this list, we found out >that it is a problem with Microsoft's DNS and cache poisoning. >Actually if you look at the output you provided from dig, you will >notice that your resolver is trying to lookup google.com using >ns1.mdnsservice.com, which is wrong. >The fix is available here though: > >http://support.microsoft.com/kb/241352 The interesting thing is that I've had that particular switch enabled since the NT4.0 days, so this shouldn't have been possible. I'm trying to track down the specific issue, but it looks like the problem is caused by using RSAT to manage a 2003 DNS server. Opening the DNS management configuration dialog on the 2003 server reveals a forwarder of "1.0.0.0", which is odd since I'm not using forwarders right now. Despite this invalid forwarder, the server was still managing to perform lookups too. Tweaking the configuration using the tools installed on the 2003 server or from an XP box using adminpak.msi rather then a Vista/RSAT seems to have fixed the problem. -- Dave Warren, [EMAIL PROTECTED] Office: (403) 775-1700 / (888) 300-3480 _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen
