I've set up a new Active Directory (AD) domain for a client, but I made the mistake of using the same name as their existing public website. This is causing issues because internal access is conflicting with their web services. I've implemented Split-brain DNS to manage access, but I'd prefer to have a different domain name altogether for clarity and reliability. I realize I can't just rename the AD domain. Is there a way to back up my current setup, remove the existing AD environment, and restore everything after changing the domain name?
2 Answers
You could introduce some simple DNS records, like A and CNAME records, to manage the internal traffic. However, keep in mind this could misroute traffic that relies on internal AD name resolution, potentially causing DFS and other services to break. It might be easier to stick with the split-brain DNS setup you already have.
It sounds like you might be in a bit of a tight spot using the same domain name. Typically, most people opt for something like corp.yourdomain.com to avoid this confusion. If you haven’t got much live traffic running yet, renaming the domain is possible. I did it once in my career without any major issues. If you determine that the AD forest isn’t active with many dependencies, consider giving it a shot. Worst case, you might end up needing to rebuild everything anyway.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures