tag:blogger.com,1999:blog-7176045.post-86381047567962856082008-05-28T01:30:00.000+04:002008-05-28T01:30:00.000+04:002008-05-28T01:30:00.000+04:00As a network infrastructure person, I can tell you that it is not good practice to have an external DNS in Local clients TCP/IP configuration.<BR/><BR/>The reason for this is that, if for what ever reason the internal DNS Server is not available, or alternatively, just busy, then Windows will fall to the next DNS Server.<BR/><BR/>What this means is that when you look up COMPANYSERVER it will no longer append a .local (or what ever your internal FQDN is) to the lookup, instead, it will append a .com.au or a .com to the lookup request, and suddenly you are trying to connect to external machines<BR/><BR/>Windows doesn't then fall back to the initial DNS Server until the first one fails a request. <BR/><BR/>DNS Should be configured with forwarders, (if required in your network) and the client machines should only have internal DNS Servers to manage requests.<BR/><BR/>If you want a redundant DNS server, then create a new Internal DNS Server.<BR/><BR/>Hope this explains why this was happening.<BR/><BR/>Regards,<BR/>Anthony MooreAnthony Moore (IT Excellence)noreply@blogger.com