2 replies
by bfilmfan
Your internal and external name spaces are the same on that Windows 2000 domain. You said it was a domain, but is it actually the root of the AD forest domain's DNS name?
In any event, you will need to redo this AD domain and if it is the root domain for the forest, you will need to redo the DNS for the entire forest.
Ideally, the internal DNS names space shoudl not be published to the world. By using www.name.LOCAL on the AD, you will prevent confusion on which DNS namespace is internal or external.
For your client (and other interested parties) this is one of the better explanations of how DNS works:
http://www.stamey.nu/DNS/DNSHowItWorks.asp
Best of luck telling your client this bad news...
by haileyan
The problem is that your internal DNS server thinks it is responsible for anything with name.com in the URL. If you have not made any entry internally in DNS for www.name.com your clients will never find it as yoru internal DNS will not forward a DNS request containing *.name.com.
Make a host entry on your DNS server that points the host www.name.com to the public IP address of your web page.
If you host your public web page yourself just make a DNS entry for www.name.com to the internal IP address of the web server.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending