Question : Incorrect DNS Settings Prohibit Dynamic Updates for Some IP Ranges

I believe I'm having an issue with a DNS configuration, but I'm not entirely sure.  Here's my scenario.

I have three locations.  The locations are tied together via an MPLS network.  Each location has it's on /22 network.  Each location also has a Domain Controller, DNS Server, and DHCP server.

Location 1
192.168.0.0/22

Location 2
192.168.8.0/22

Location 3
192.168.16.0/22

The issue I'm having is isolated to Location 1, but only because that site has more workstations than the rest.  That will make sense in a second.

We used to have one location with a 192.168.0.0/24 network.  We altered the subnets when we added the facilities.  However, until recently I was unaware that our DNS settings were incorrect.  Our Reverse Lookup Zones (for each of the three sites) are as follows:

192.168.0.x Subnet
192.168.8.x Subnet
192.168.16.x Subnet

I'm sure you all can see where this is going.

For Location 1 (192.168.0.x), any workstation with an IP address of 192.168.1.x, 2.x, or 3.x are not dynamically added to our Reverse Lookup Zone of 102.168.0.x within our DNS.

My initial reaction was to create a 192.168.x.x Subnet, but my fear was if or how that would negatively impact the 192.168.8.0/22 and 192.168.16.0/22 sites.

So...this is where I ask for your assistance.  How should I fix this mess?

Great thanks in advance.

Answer : Incorrect DNS Settings Prohibit Dynamic Updates for Some IP Ranges

As your network is on a /22

11111111.11111111.11111100.00000000 which means that 192.168. (1-3) . x should be visible locally.

Therefore creating reverse lookup zones for 192.168.1.x, 192.168.2,x, & 192.168.3.x would mean that IP range would be accessible locally without getting routed which is exactly what you want I think.

Access to address range 192.168.8.x and 192.168.16.x would still get routed through your default gateway as it is outside your subnet mask range

So I'd just go ahead, create a reverse lookup zone for 192.168.2.x and 192.168.3.x you should be able to 'ping' them locally.