Name resolution on domain is not working correctly
Posted on 2009-04-02
My company has one main office and several branch offices.
In the main office we have the DC, a Windows 2003 server, which is also the primary DNS server for the PC's in that area. In one of the branch offices we have a Windows 2003 Server which acts as a DNS slave. This is the primary DNS server for the PC's in that area. The DNS slave used to be a Linux machine with BIND DNS daemon, but was replaced a few months back with the Windows machine.
What happened after the replacement was that PC's both at the main office and at the branch office have problems resolving internal addresses. It looks as if WINS is still working because we can ping COMPUTERNAME, but not COMPUTERNAME.some.domain. The only solution is to run the command 'net stop dnscache' on the clients. Then it works. Afterwards we can turn the dnscache on again and it will still work, but we always have to turn it off after booting the PC's.
Does anyone have an idea on what is going on?