We often advise customers to (if possible) replicate the records that our system auto-populate when it created the account (which you can see when you log in to cPanel and visit Zone Editor) on their domain registrar dashboard or where they are hosting their DNS.
Now, this is not a feature you will see on all Registrars but most modern ones do.
There are several benefits to this including maintaining consistency across the board which kind add a certain amount of redundancy to your DNS structure.
If you have bought your domain from Google Domain, please visit https://domains.google.com/m/registrar/?hl=en.
- Select the domain for the list and click “Manage”.
- Select “DNS” from the options on the left-hand side.
- Scroll down till you come to the “Custom resource records”.
- Then log back into your cPanel, copy the records you see on your cPanel Zone Editor and replicate each one of these there.
Default DNS for that service is 1 hour but you can adjust it to 5 minutes for a speedier resolution.
If you are using Premium Cloud DNS, you will have to this from the Console.
Another faster approach would be to export and then import the zone file but it is kind fraught with risk.
If you are willing to give it a try (useful if you have a very large zone record), then this is what might consider doing:
Please note that there is no way to export DNS zone as file via the Zone Editor, but here is a workaround:
- create a backup in cPanel
- download and untar it
- rename dnszones/domain.com.db to domain.com.txt, domain.com.zone, domain.com.bind or whatever your new service wants (txt for CF)
- import to your file to the new service
You can also ask us for a copy of your DNS zone file which we can give and then you can rename it to .txt file and use it.
You can then import record-sets using the dns record-sets import command.
The –zone-file-format flag tells import to expect a BIND zone formatted file.
If you omit this flag, import expects a YAML formatted records file:
gcloud dns record-sets import -z=examplezonename \
Once done, visit https://developers.google.com/speed/public-dns/cache and flush the records from Google cache.
But as a precaution, always have the same set of DNS records on both Cloud DNS console and Google Domain UI so that if you decide to leave Cloud DNS, you simply switch your name-servers and be back online in seconds.