1. Home
2. /
3. Domains
4. /
5. Updating nameserver IP addresses (renumbering)

Updating nameserver IP addresses (renumbering)

3 min read · 4 screenshots

Background and deadlines

As part of the modernization of our DNS infrastructure, the IP addresses of your virtual nameservers will change.

This QuickGuide explains what adjustments are required and how to make them in AutoDNS.

Important deadlines

All changes can be made effective immediately.

DNS queries will be answered in parallel via both the old and new infrastructures until the old DNS infrastructure is completely shut down in April 2027 (dual provisioning).

• November 30, 2026
  Shutdown of dual provisioning for the old DNS infrastructure. 
  New zones and changes to existing zones will be processed exclusively on the new infrastructure.
  Existing zones will continue to function technically, but can no longer be modified without the IP update.
• April 30, 2027
  Complete shutdown of the old DNS infrastructure
  From this point on, domains that use non-migrated virtual nameservers will no longer be accessible.

Take Action!

If the necessary adjustments are not made by November 30, 2026, existing zones on the virtual name servers can no longer be modified, and new zones can no longer be created as usual. In this case, as of April 30, 2027, all domains connected to the virtual name servers will become inactive and will no longer resolve in the DNS.

Overview: Old and new nameserver IP addresses

Step-by-step: Changing host names to new IP addresses

Step 1: Identifying the affected hostnames

Using the zone inventory list, you can identify all currently used nameserver hostnames that are affected and then migrate them all to the new IP addresses at once.

A list of the zones and their associated hostnames will also be emailed to all affected customers.

Step 2: Updating the IP addresses of the virtual name servers

• In the PORTFOLIO, open the Nameserver tab for the DNS zones.

• Search for the resource records that contain one of the old IP addresses.

• Replace the old IP address with the new one (see overview above).

• Click Save to apply the change.
• Repeat this process for all affected zones if the virtual nameserver set is distributed across multiple domains and TLDs.

Step 3: Updating glue records (domain update)

This step is only necessary if you use your own domains as nameserver hostnames.

Without updating the glue records, name resolution for the affected domains via the nameserver would only be partially guaranteed after November 30, 2026.

Here’s how to update the domains:

• Open the domain portfolio in AutoDNS.
• Open the domain form for the nameserver domain (e.g., yourdomain.de).
• Switch to the Name servers tab.
• Replace the old IP addresses with the new addresses from the table.
• Click Save to apply the changes.

Notes for customers with a primary setup

Primary Setup = The customer uses our primary nameserver and their own secondary nameservers

During the transition phase, our existing primary IPs will continue to send notifications to the external secondary nameservers.

The new IP addresses for the primary nameservers must also be configured in the DNS software so that the external secondary nameservers can respond to notifications from the new infrastructure.

New primary IP for notifications: 217.160.80.161

Notes for customers with a secondary setup

Secondary Setup = The customer uses their own primary nameserver and our secondary nameservers.

The IP addresses for zone transfer and zone import do not change.

Zone transfer continues to take place via the AXFR gateway 62.116.132.5, and zone import via 62.116.129.216.

To ensure a seamless transition, the primary nameserver must be configured to send notifications (notifies) to both the previous AND the new IP addresses of our nameservers.

Support and Contact

If you have any questions about the process or need assistance with DNS configuration, our Domain Services Team is happy to help.

Email: domains@internetx.com