We have some exciting upgrades planned for 2019 and to help prepare for these we’re replacing our secondary DNS server. This change requires your attention if you use private or custom name servers (ex: ns1.yourdomain.com).

If you use any of our gzo.com (ns*.gzo.com or dns*.gzo.com) name servers or a 3rd party DNS service, you can safely ignore this. If you have questions as to whether or not this applies to you, please submit a ticket and we can help guide you.

The IP address for our secondary DNS server has changed from 162.254.145.209 to 107.155.97.210. If you’re using private or custom name servers, this change has to be made in two places:

1. The A record for ns2.yourdomain.com, or whatever address you’ve chosen, needs to be updated to the new IP address. This will need to be done at the domain’s current DNS host. If we host the domain's DNS and it had the old A record configured, it has been automatically updated and no change is required on your part for this step. If yourdomain.com is using 3rd party DNS, then you'll have to update the A record with that provider.

2. The entry for ns2.yourdomain.com, or whatever address you’ve chosen, needs to be updated at the registrar for yourdomain.com. Registrars vary in how they reference these, but they commonly call them child name servers, custom name servers, personal name servers, or DNS hosts. Your registrar should have documentation available explaining this process if needed. If you have any trouble with this, please let us know and we’ll be happy to help in any way possible.

These changes should be made by December 28th if at all possible. At that point, we will be taking the old server offline. If for some reason you’re unable to meet this deadline, your domains will remain online so long as your primary name server (ns1) is configured correctly and that server does not experience any downtime. This required change simply ensures the redundant nature of our DNS so that the downtime of any single DNS server will have no impact.

If you have any questions at all concerning this process, please feel free to submit a ticket. We’ll gladly assist as best we can. We’re currently examining all domains that we host and will be reaching out with ticket notifications to clients that we see using custom name servers.

As a bonus, our secondary name server now supports IPv6 connectivity. Please know that setting this up is not required nor is it possible with all registrars. If it’s something that you’re interested in, though, the address can be found in your account info in our portal.