Is this all from the server with the .0 ip address or is the other one the same? From the other server remove the .0 one as a dns server and try?
On the .0 server remove all other dns servers apart from the the other dc and try again?
so changing the DNS entry on the server to 188.8.131.52 allowed you to ping 184.108.40.206 ? when you could not before?
That's very odd.
Just so I'm clear, because I'm at a point that I'm questioning everything.
on the nic of the server, the dns should be the ips of the internet dns servers.. correct? And we use the DNS forwarders as the only location to ass the isp DNS server (or external dns server ips)
No in a fully functioning ad domain your domain controllers and all pc's should have their dns servers set to be the domain controllers and nothing else.
Working DNS is the cornerstone of Active Directory.
The DNS servers can then use root hints or a dns forwarder to resolve ip addresses for names in the outside world.
Getting you to change them was only as a test of trying to pin down where the issue is.
BTW, I did try dropping the .0 and nothing has changed for the good. I'm currently shutting down one of the servers and will play around with everything I can find. It's also the one time that the event logs aren't yelling at me about a glaring issue. Go figure.
If DNS is on the DC's then the Primary DNS server listed on the network Adapter should be one of your other DNS/DC server and its own IP its Secondary DNS server
You also have to update your list of root hint servers manually, an up to date list can be found here ftp://ftp.rs.internic.net/domain/db.cache.
There are currently 1 users browsing this thread. (0 members and 1 guests)