Legacy DNS: Finish of Life

Earlier this summer season, GreenGeeks started rolling out our Anycast-based DNS for all shared and reseller internet hosting accounts.

Utilizing Anycast permits greater efficiency, decreased latency, and scaling throughout a number of places, higher assembly our clients’ wants.

Table of Contents

Anycast Nameservers

Our new nameservers, that are Anycast-enabled are as follows:

Legacy DNS Shutdown

On September thirtieth, GreenGeeks will shut down our legacy DNS infrastructure and can make default the Anycast-enabled nameservers.

The legacy nameservers, with the IP addresses listed beneath, will not reply after September thirtieth:

chi-ns1 [99.198.112.83]
chi-ns2 [69.175.59.162]
ams-ns1 [107.6.141.186]
sgp-ns1 [103.3.62.28]

GreenGeeks has already re-directed the legacy nameserver aliases to the Anycast DNS cluster and robotically adjusted domains registered via the GreenGeeks registrar to the Anycast NS.

Domains registered via third-party area registrars should be up to date manually.

Though the legacy nameserver aliases will proceed to work after the nameserver shutdown, GreenGeeks strongly recommends updating all nameservers to the Anycast DNS to keep away from mismatches between the backend nameservers & the area registrar.

Personal Vainness Nameservers

For customers with non-public vainness nameservers underneath non-GreenGeeks domains, you’ll want to regulate the IP handle assigned to every nameserver to match these offered beneath:

ns1.area.com [75.2.69.7]
ns2.area.com [99.83.188.187]

Personal vainness nameserver adjustment is a two-step course of involving registering the IP handle for every nameserver with the area registrar and updating the corresponding A report throughout the GreenGeeks DNS zone. For more information about non-public nameservers, confer with our help article on Organising Personal Nameservers