DNS resolves www address when pinging internal systems on Windows 2003 Domain
We have a handful of computers that, when pinging another system (server) on the local network, resolves to the external 'www' address seen in our DNS Server (Windows 2003 server). A reboot of the client seems to fix. What could be causing this?
ASKER
yes, we are
ASKER
are you saying this is due to not having split DNS in Windows 2003m domain?
Where do you have your ISP dns server forwarders placed. They should be on the forwarders tab rather than on the Interface tab, which occasionally is configured that way? Run dnsmgmt.msc on (all off) your dns server(s) -> open properties off the dns server and see if this is configured correctly.
add an Alias CNAME in DNS called www. company.com and point it to your web IP
I think Meultje is on the right track, although the fact that your internal and external domain names are the same is the ultimate root of the problem. Are your clients configured to use only your internal DNS server(s) for resolution?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
DrDave - clients are now joined to 'CompanyB.com' but look to 'companyA' domain for resolution. In other words, Clients are still using the resources of CompanyA.com but have been migrated to join CompanyB.com. The client DNS configuration of the client has 'CompanyB.com as the Primary DNS suffix. CompanyB.com is also top of the list for the suffix search list. Although, the IP address of CompanyA.com's DNS server is first on the adapter. So, under IPCONFIG /ALL, windows IP config and enternet DNS settings defined differently.
I am currently checking Meultje recommendations from above...
I am currently checking Meultje recommendations from above...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok, to clarify - our clients are now members of the companyB.com domain. We change them to use companyB.com DNS servers. Our clients will, for a short time, still need to access resources on CompanyA.com domain. will we need to transfer the entire CompanyA.com zone 'across' to comanyB.com DNS server, to be able to resolve correctly? Also, will there be a performance hit, if traversing WAN connection, for this type of query? thanks for any insight
No, just configure conditional forwarders on the companyb.com DNS servers to forward queries for the companya.com domain to the companya.com DNS servers. Then do the opposite on the companya.com DNS servers so that they'll forward queries for the companyb.com domain to the companyb.com servers.
Here's info on how to configure conditional forwarders in Server 2008:
http://technet.microsoft.com/en-us/library/cc754941.aspx
The process in 2003 is very similar.
Here's info on how to configure conditional forwarders in Server 2008:
http://technet.microsoft.com/en-us/library/cc754941.aspx
The process in 2003 is very similar.
ASKER
will be attempting the DNS re-configure soon and will update with results
ASKER
the zone transfer appears to be successful cor clients to resolve all 'local' resources by querying the 'remote' networks' DNS servers. This, it seems, is obviously the most effient and reliable way query DNS - through the DNS server of the domain which you are a member of. thanks - -
ASKER
Most helpful recommendation to DNS server of 'own' domain but also valid recommendation to check DHCP scope options
I.e. your company.com is used inside the LAN, and on the internet?