DNS does not escalate for its own domain name
Posted on 2004-10-16
an inhouse net with AD domain "mydomain.com".
outside ISP with web server: www.mydomain.com and some more subdomains as: x.mydomain.com, y.mydomain.com,...
The ISP provides 2 DNS server: NS1 and NS2
My inhouse DNS server has all inhouse ip mapped to names.
I could access by IE6 all inhouse of mydomain and all other (not my domain) targets outside (usual web access)
>>> I could not access my (outside) www and subdomains!
Obviously my DNS does not resolve the outside domains when it has to look for inhouse domain names outside (escalating to the ISP provided 2 DNS server).
The outside domains has 2 DNS server (provided by the ISP) which are listed as 2nd and 3rd when listing with ipconfig /all
First DNS server is my inhouse DNS server.
I made a test by moving one of the outside DNS server to position 1 in my list.
Now I have access to all outside and "www.mydomain.com" too. but i.e. Outlook doesn't resolve to my (local /inhouse) Exchange2003 server. It says the server maybe down. But the problem the local server is not found as its name is not resolved. (MY! inhouse DNS server doesn't obviously resolve it as it is not asked or not asked early enough when it is a timing problem.)
Internet access is by DSL and an dynamic IP for the DSL-Router
Could it be that timing plays a role. How should I over came that?
How could I make my DNS server escalating an unresolved name to DNS 2 and DNS3? As it obviously does for all foreign domains but not for the AD (inhouse) domain?
Any help would be really appreciated.