Nameservers & Glue Records separate
I have a domain with sub domains for each server. So vps1.domain.com (main WHM/cPanel with many accounts), vps2.domain.com (DNSOnly cPanel). These are the FQDNs for the servers. They don't have accounts in WHM, just a DNS zone on vps1.domain.com using the "Add a DNS Zone" function.
domain.com has glue records for ns1.domain.com (vps1.domain.com IP) and ns2.domain.com (vps2.domain.com IP).
domain.com has nameservers pointing to ns1.domain.com and ns2.domain.com.
The issue is that all these sub domain records live on vps1.domain.com. I want to add additional servers and not rely on one of them for the domain.com DNS records.
I want to have the DNS records for domain.com live on the DNS in the VPS provider or something like DNSMadeEasy.
Can I have the DNS for the main domain for all my servers (domain.com) off of the servers but still have all the DNS for the hosted websites live on the server they're on?
To do this I would change the nameservers for domain.com to the VPS provider's or DNSMadeEasy, migrate the sub domain dns A records (vps1 and vps2).
I'm not sure what to do with a few of the records though.
The DNS zones for vps1 and vps2 have NS records in addition to the A record. Do I need those or are they created by default in WHM? There are also zones for ns1.domain.com and ns2.domain.com each with more NS records and their A records.
-
I should be able to remove the vps1.domain.com and vps2.domain.com zones from the server but do I need to keep the zones for ns1.domain.com and ns2.domain.com on the server? On the external DNS I've created the following: - NS, domain.com, ns1.domain.com
- NS, domain.com, ns2.domain.com
- AAAA, ns1.domain.com, 2001:0db8:85a3:0000:0000:8a2e:0370:7334
- AAAA, ns2.domain.com, 2001:0db8:85a3:0000:0000:8a2e:0370:3322
- A, ns1.domain.com, 111.111.111.111
- A, ns2.domain.com, 222.222.222.222
- A, vps1.domain.com, 111.111.111.111
- A, vps2.domain.com, 222.222.222.222
0 -
This seems to work fine, you can delete this thread. 0 -
Hi @jonh I'm happy to see that you were able to find a solution to your issue! Thanks for updating us how you resolved the issue as well. 0
Please sign in to leave a comment.
Comments
3 comments