General discussion


DNS wont resolve internal names.

By williamoshea ·
Dear folks,
i have just added a 2003 server to my domain, made it a domain controller, etc., etc. My problem is that when i try to visit a page on the intranet using it's netbios name, the page fails because it is looking for the page outside the intranet. If i use the IP address, it works fine. Any idea why my DNS server cannot resolve internal names or why it is forwarding internal names to the forwarders. Ping returns the FQDN of this servers but http://netbiosname or FQDN returns "could not be resolved".
Please help. The DNS is AD integrated and there are 2 secondary DNS servers that loads off the

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to DNS wont resolve internal ...

could be a couple of problems. your DNS server isn't pointing to itself. Your DNS server isn't pointing to other DNS servers and they aren't point to the W2003 DNS server. You probably have a root hint (.) in your foward lookup zone.

here is a KB;en-us;2**382

Collapse -

by jacobgin1 In reply to DNS wont resolve internal ...

Is this a problem from only ur pc or is a common problem. If its only urs, check if ur DNS is correct in the pc. Also add a new DNS entry in the server to point to itsself. A temporary solution is editing the host file in ur pc and adding an entry of the server.

Collapse -

by BFilmFan In reply to DNS wont resolve internal ...

Is the FQDN registered in DNS? You may have to make a manual entry for this to function properly.

You may also find this article to be of interest:

Related Discussions

Related Forums