I set up a domain with ABC.Local for my company a long time ago. When we added an Exchange server, I created a second zone for FullName.com in our GoDaddy account, which only had a host entry for WWW pointing to a third-party web host. Over time, I added more records for various services like autodiscover and internal equipment, but now we're doing more SSO and need host records that point to SSO login pages. For these to work, I have to create an entry on GoDaddy first, and then replicate it in our internal DNS, which feels redundant. I'm considering removing the FullName.com zone from our local DNS and only using ABC.Local for internal purposes. However, are there any potential issues I should be aware of before proceeding?
3 Answers
It’s pretty straightforward! From your internal DNS, set the NS records to point to GoDaddy. Just use the format for each subdomain you want them to handle. After that, set the records on GoDaddy and you’ll have a single source of truth.
You don’t really need both zones; one should suffice. Your DNS settings might need a review since external entries can confuse things. Plus, using .LOCAL as a TLD is considered bad practice these days—just something to keep in mind.
As long as FullName.com isn't tied to any internal services or Active Directory, you should be fine to remove it. Just make sure to back up the internal zone first in case anything goes wrong.
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