DNS through router

[jfc1003]

We have two networks that are interconnected via a router. One network is the 192.168.20.0/255.255.255.0 and the other is 172.22.0.0/255.255

We are in the process of migrating everything over to the 172 network due to our network growth. However, certain vendors have to be involved so we can't just move everything all at once.....

So our domain controllers and internal DNS are still sitting on the 192 network. We bought a new Windows 2003 server, placed it on the 172 network, but it refuses to join the domain on the 192 network. (I can ping the IP but not the server name) Windows 2000 Server, however worked just fine.

Now, we just ran the Windows 2000 security rollup, and suddenly our DNS servers (running Windows 2000) on the 192 network will no longer resolve DNS requests coming from the 172 network. So there is obviously some kind of security setting built in to 2003 and now added to 2000 that refuses to resolve DNS requests from other networks or something.....help!!!

 

[SimonDavies]

OK, first of all are you running two seperate DNS servers? If so have you put lookup zones in? ie if it can't resolve to your local DNS domain to look at other DNS servers?

Have you tried to do an NSLOOKUP to see which DNS servers it's trying to query?

 

[jfc1003]

I tried adding reverse lookup zones, AD integrated last night. If I did a repair on the machines on the other network, they began showing up in DNS and they were able to contact servers in the primary network.

I admit DNS is a big weakness for me. Do I understand this to mean that my DNS servers were not responding because the computers on the 172 network were not securely registered in DNS? I don't understand why this fixed it. Or why it worked fine until we ran the security rollup for SP4 on the DNS servers.