0

I've been tasked with implementing reverse DNS internally in our Windows environment. What are some risks I should watch out for, and what is the best way to setup a test environment for changes like these?

Should I just spin up a new domain controller and add a few DNS entries and then go from there? I'm a new sysadmin and just really want to avoid breaking something.

PermanentBeginner
  • 1

1 Answers1

1

Windows and Active Directory don't use reverse DNS for any internal communication. There's absolutely no risk in setting up a reverse lookup zone.

You don't need a new Domain Controller. Just create the zone(s) on your existing DNS server(s).

joeqwerty
  • 109,901
  • 6
  • 81
  • 172
  • Thanks! The new domain controller would just be for testing purposes. Just trying to be extra cautious. – PermanentBeginner Jan 15 '21 at 21:10
  • There's no such thing as testing in a production environment. If you need to spin up a Domain Controller to tinker with, do it in a test environment. Deploy a new server, install the AD DS roles and services, and create a test domain. – joeqwerty Jan 16 '21 at 00:27