Help with DNS issue in Active Directory

[sdotsen]

1 - Let's say our domain is abc.com.
2 - Our websites are hosted on dedicated servers outside our company.
3 - We're running Active Directory and the domain we setup is called abc.com

Ok, so I added

http://www as

a CNAME and pointed it to the IP address to the server that houses
our website. If I ping

http://www.abc.com

it resolves to the external IP to the dedicated server.
If I ping abc.com it points back to the internal IP of the PDC 192.168.100.10. How the heck do I resolve abc.com to the external IP?

 

[LWComputingMVP]

This is why you shouldn't use abc.com for an Active Directory domain name - you should have used .local or something similar (I usually use .lcl). I don't think you can get abc.com to point to an external host without screwing up DNS for your domain.

 

[rickrude11]

why does it matter if you ping abc.com that it resolves to your pdc? same happens to me, but users just have to type

http://www.fgh.com

to visit the website.

 

[lhuegele]

If you have users that don't want to type www, those users don't have enough to do in their daily jobs.

Best practice is to use something unique for your internal domains as lwcomputing already stated.

 

[djtech2k]

You could change DNS so that abc.com resolves to your external, BUT it will break your domain. If your internal domain is abc.com then you always have to resolve it to your DC's otherwise domain authentication will not work.

One workaround could be something with a proxy server or web content filtering. You could then possibly take any request going to abc.com and redirect it to

http://www.abc.com.

As the gusy before me have said, this is why you NEVER name your internal domain the same as an external.