Added new subnet but records are not updated to DNS’s reverse lookup zone

Question

Our old existing network

192.168.3.x (for workstations and servers)

DHCP was on Windows Server. Both DNS Forward lookup zone and reverse lookup zone had 192.168.3.x records.

  

New location network

Vlan 3, 192.168.3.x (for servers)

Vlan 100, 192.168.100.x (for workstations)

DHCP role was moved to Firewall.

Two subnets are routed each other by switches.

 

After moved to new location, on Windows DNS

Forward Lookup Zone, workstations 192.168.100.x can be updated to the zone

Reverse lookup zone

3.168.192.in-addr.arpa still shows workstation’s old records. Should I remove them manually?

I added 100.168.192.in-addr.arpa zone manually. But only 8 workstations are recored.

Please advise how to fix this. Thanks

Answer 1

Hello   EcoAxis 

Should I remove them manually?

You may need to manually remove the old reverse records associated with workstations that have moved to the new subnet. These records are no longer valid in the new subnet and can cause DNS resolution issues if they are not removed.

DNS records typically don't update automatically when devices move between subnets because DNS servers may not be aware of the new network topology. So, manually managing and cleaning up old records is often necessary when you make significant network changes like this.

Best regards,

Karlie Weng