none
DNS: best practices when changing from /24 to /16 RRS feed

  • General discussion

  • We have changed our DHCP scope from /24 to /16.

    DNS reverse DNS zone, still /24 (0.168.192.in-addr.arpa), populates accordingly. The /16 (168.192.in-addr.arpa) has no entries.

    On a lab that we've setup as /16 from the beginning, the /16 reverse DNS zone populates as expected.

    It's a best practice to remove the default DNS forward lookup zone and create a new one when changing subnet masks?

    What you would suggest in our scenario? OS is Windows Server 2016.

    Any help will be greatly appreciated!



    Thursday, May 2, 2019 8:58 PM