Greetings, I hope someone here might be able to shed some light on an issue I am having with DNS.
This weekend we finally upgraded our domain from NT4 to 2003. That went smooth as can be. We have however run into some outbound mail issues from our SMTP gateway that are DNS related (can't resolve some MX records from aol.com and others.) Pre-upgrade we ran split brain DNS on Windows 2000. Two servers on our internal LAN for our private ip space, and two externally for our public records. This has worked fine. No issues resolving external hosts from the internal servers. Post upgrade, our internal DNS servers are now running Windows 2003 DNS and internal clients and servers cannot resolve some, but not all external dns records (ie: a nslookup -q=mx aol.com returns nothing but the same for say earthlink.net does. The same lookup using the unchanged public Windows 2000 DNS server returns all the correct results.) Under Windows 2000 we did not use forwarders, the root hints handled everything. Under Windows 2003, this appears to be hit or miss and to guarantee resolution, we have had to direct our internal DNS to forward to our external DNS to do the actual root lookup. Any ideas on why the Windows 2003 DNS refuses to use the root hints to lookup records and must be set to forward to an external server to use it's root hints lookup? I have it working, but I am not sure why I had to make the changes in the first place. Thanks Miles ------ You are subscribed as [EMAIL PROTECTED] Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=nt2000&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED]
