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

EcoAxis 376 Reputation points
2023-08-23T07:37:52.29+00:00

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

A3

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,744 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,524 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,039 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Karlie Weng 18,276 Reputation points Microsoft Vendor
    2023-09-20T06:20:09.58+00:00

    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

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.