Registrar and Host are different companies. Obviously A, MX, CNAME, TXT, SRV should be changed. However, should I move Domain Name Servers to the Host or keep them with the Registrar?
You could really go with either. If you like the registrar’s DNS management tools, then you can continue to use them. If you feel the hosting company’s offerings are better or that their DNS service is more reliable, you can switch to them.
One thing to consider is that if you ever switch hosting companies, having your DNS managed by your registrar might make things easier. If you’re quite happy with your hosting then this is not as big an issue.
Compare things like online tools, reliability and uptime, APIs for scripting and making automated updates, stuff like that. If you ever decide to run your own nameserver, you might want to see if either company offers slave DNS service, too.
There’s not really a “right” answer, so you just want to compare the options which are important to you.
- Server cannot reached in different locations. Who I should blame, domain registrar or hosting company?
- Setting MX records with Registrar vs. Nameserver Host
- Shouldn’t the domain registrar run the nameservers?
- In a 2 DC environment, should both DCs host AD integrated primary zones to ensure DNS redundancy?
- Is using a name server on a different host a good practice?
Leave a comment
- What is the easiest way to upgrade my existing Perl 5.14 to Perl 5.16 on FreeBSD 9 using the ports system?
- Know if mysql has done its job
- Redirect https .com to https .co.uk without a valid SSL cert on .com without DNS change
- Why is it a bad idea to use customer email as from address
- 100% packets dropped on first RX queue on 3/5 raid6 iSCSI NAS devices using intel igb (resolved)