Question Locked

How To Resolve a Domain to External Server using DNS & Windows 2003 Serve

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a new server running Windows 2003 Server (R2) and have installed Active Directory for a small network of 10 PCs. The problem is that the our website is hosted on a server elsewhere and any time we try to get to the site using our domain name, it resolves to our internal server instead of resolving to the actual external server running the website.

For more details, we have a server (10.1.80.200)(Server1) that is running DNS and the internal domain is defined as (pinet.com) and the fully qualified name is server1.pinet.com. If I go to any of the PCs on our network and type in the browser, www.pinet.com, I get a page not found because it is resolving this name to 10.1.80.200 instead of the actual external server.

Any ideas on how do I fix this as I'm new to active directory and DNS.

Thanks

M

4 replies

by scott_heath

This is why MS says to never name your internal domain the same as your external domain. But, alas, it is too late. Put a static DNS entry in the pinet.com zone that points to the IP of you external web server.

Or put in a proxy server that uses an external server for DNS.

Or rebuild you AD as pinet.local or pinetad.com or anything but pinet.com.

Good luck,
Scott

http://scottisageek.spaces.live.com

by churdoo

First, for precisely this reason, it is considered a best practice to name your AD Domain differently than your public domain, i.e. yourdomain.local versus yourdomain.com.

You can rename your AD to .local, if interested see:
https://www.techrepublic.com.com/5208-6230-0.html?forumID=102&threadID=229757&start=0
https://www.techrepublic.com.com/5208-6230-0.html?forumID=102&threadID=229757&start=0
http://www.msexchange.org/tutorials/Domain-Rename.html

Short of renaming your AD Domain, do you really have a host www on your internal network that's resolving to 10.1.80.200, or is www non-existent? You would have to modify or create the www A record in your AD DNS so that www resolves to the pub IP of your website.

by p.j.hutchison

You need to change the www entry in your internal DNS to point to the correct IP address of your external web site.

Any internal web servers will need a different dns entry e.g. intranet.pinet.com or something.

This discussion is closed to new replies.