Move the site to a new IP address
We have released new version of DNS hosting (actual) and are discontinuing support and development of legacy version (legacy). Domains and resource records in DNS hosting (legacy) continue to work, we will warn you in advance if they are discontinued.
We recommend move domains and resource records to DNS hosting (actual) now to avoid disruption of sites when DNS hosting (legacy) goes down.
If you registered after January 30, only DNS hosting (actual) is available to you.
You can accelerate the propagation of changes to a resource record to caching servers. To do this, a few days before the planned change, reduce the TTL of the recording to the lowest possible value. Then, at the designated time, change the resource record, and when the change propagates to the caching servers, return the TTL to its previous value.
- DNS-хостинг (actual)
- DNS-хостинг (legacy)
- In Control Panel, go to DNS.
- Open the zone page.
- From the menu of the A-record group, select Edit.
- Change the IP address to a new one.
- Click Save.
- Wait for the resource record to be updated on the DNS servers. Updates can take from a group's TTL up to 72 hours to complete. The TTL of the resource record group can be viewed in control panel under DNS on the zone page.
- Optional: check resource record. If the resource record has not updated on the DNS servers 72 hours after creation, create a ticket.
- Check that requests are only coming to the new IP address and that the old one has no requests from users. After that, release the old IP address.
- In Control Panel, go to Network Services → DNS Hosting.
- Open the domain page → DNS records tab.
- From the A-record menu, select Edit.
- Change the IP address to a new one.
- Click Save.
- Wait for the resource record to be updated on the DNS servers. The update can take from TTL recordings up to 72 hours to complete. The TTL of the resource record can be viewed in control panel: section Network Services → DNS hosting → domain page → expand record string.
- Optional: check resource record. If the resource record has not updated on the DNS servers 72 hours after creation, create a ticket.
- Check that requests are only coming to the new IP address and that the old one has no requests from users. After that, release the old IP address.