Issue with DNS Server

[dan]

I setup a AD server and the domain i used was mydomin.com
but when i want to go to the website www.mydomain.com that
is hosted by my isp, i get a dns error. I was told that i
should of used mydomain.local when i setup my AD server.
Is there any way to fix this with out redoing the server.

 

[Simon Geary]

You must create a host record of www in your local DNS server that points to
the external IP address of your web server.

It is not necessarily true that you should use .local when installing AD.
You can use the same namespace as your external domain but this split brain
setup requires you to manually create any publicly accessible records
internally. www, ftp, smtp etc.

 

[Dan]

What is the best practice in setting this up. Is it better
to use .local or use the same namespace as your external
domain? Also on another AD server i set it up to be .local
can i change it back to .com with out messing up my
exchange server settings.

 

[Michael Johnston [MSFT]]

The recommended approach is to use a different name internally than externally. This can be acheived in a number of ways. You could use mydomain.local
or corp.mydomain.com to acheive this. Either would be an acceptible sollution. As for your current setup, most of the problems surrounding this can be
addressed. The primary issue is what you currently are experiencing. This is what we commonly refer to as split horizon dns where the name exists internally
and externally. All you have to do is make sure that any resources that clients on either side need to access, exist in the other DNS name space. For instance,
in your internal zone you needed to create the www record for the external website. If there are any other external resources for this domain that internal clients
need, those records will also need to be created.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.