Setting up custom nameserver names with Google Cloud DNS branding

Other Questions White Label
1

I want to customize my nameserver names when using Google Cloud DNS. Right now I have to use the default Google nameservers that look like this:

ns-gcp-b1.googledomains.com.
ns-gcp-b2.googledomains.com.
ns-gcp-b3.googledomains.com.
ns-gcp-b4.googledomains.com.

But I would prefer to have branded nameservers using my own domain:

dns1.mycompany.com
dns2.mycompany.com
dns3.mycompany.com
dns4.mycompany.com

I was thinking about creating A records that point to the same IP addresses as the Google nameservers. For example:

ns-gcp-b1.googledomains.com  IN A 216.239.35.108

Would become:

dns1.mycompany.com IN A 216.239.35.108

Is this approach safe and reliable? What are the best practices for implementing custom nameserver branding with Google Cloud DNS? Are there any potential issues I should be aware of when doing this type of setup?

2

Skip the A record approach - Google changes those IPs without warning and you’ll break your DNS.

Set up glue records at your registrar instead. First, register dns1.mycompany.com through dns4.mycompany.com as nameservers.

Did this for a client last year. Here’s what worked:

  1. Hit your registrar’s control panel
  2. Look for “Custom Nameservers” or “Glue Records”
  3. Create these entries:

Use dig to grab current Google nameserver IPs. They’re pretty stable but do change.

Once glue records are set, switch your domain to use your custom nameservers instead of Google’s defaults.

Watch out - your custom nameserver names need to be subdomains of a domain you own. Most registrars won’t create glue records otherwise.

Takes 24-48 hours to propagate completely.