THe DC already is configured with a non routable IP and has that IP setup in it's own DNS.
Main Topics
Browse All TopicsServer 2003
AD domain name same as existing internet domain name.
1 DC that is the Internal DNS server.
DNS Server is setup to forward unkown lookups requests to external dns.
It is also caching internet lookup's.
Problem: When you ping DC internally it is responding with internet domain name IP. It has also created DNS entries for most of the internal computers that point to the external IP address.
There are valid DNS entries for DC/other PC's in DNS. I need to know how to re-configure Internal DNS so that when users are looking up local computers they are not getting returned the external IP address of the internet domain.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
first check where are the client machines pointing for dns. They should only point to the internal dns server and no to the isp even for alternate dns. Next on the client machine run the command nslookup and try to resolve the name of dc and it should resolve to the internal ip address.
On the dns server itself when you ping to self by name, do you get a internal ip address or the public ip address?
Cheers!
Aj
>AD domain name same as existing internet domain name
Why? Can you change one or the other so they do not match?
I'm no windows guru, but I've seen some advice right here at EE (in other questions) that suggest that having your external DNS domain match your AD domain is a bad idea, and can cause all sort of problems...
Cheers,
-Jon
1. Did not clear cache (yet) because even if I did it would probably come back anyway.
2. Yes the AD domain name should not be the same as a internet domain name, I didn't set it up, but I have to deal with it and changing the domain name is not an option right now.
3. Clients are have 3 dns entries.
1. Domain controller
2. External DNS 1
3. External DNS 2
During my testing I have configured a client with ONLY the Domain controller IP, but it still resolves to an external address. That is because the Domain controller is the internal DNS server and it has the external ip in it's cache.
On the AD server when I ping it's name I believe it resolves to the right ip. I can't test it right now.
Business Accounts
Answer for Membership
by: busbarPosted on 2007-03-16 at 12:44:27ID: 18737472
Configure the IP address of the DC with internal IP for example 192.168.1.1
in the DNS tab of the DC point to its ip address (192.168.1.1)
run netdiag /fix
dc diag/fix
restart the netlogon service and have fun