In case you are running a different DNS server this should be similar just that the configurations will look different based on the particular DNS server you are using. ; Nameservers ns1 A 192.168.0.1 ns2 A 192.168.0.2 ; Mail mail A 192.168.0.10 ; Web www CNAME domain_to_Let’s say that we have a very simple zone file defined that looks like this (the IPs are private ones just for the exemplification): ; zone 'domain_to_move.com' $TTL 86400 @ IN SOA ns1.domain_to_ ( 2006052101 ; Serial 10800 ; Refresh 3 hours 3600 ; Retry 1 hour 604800 ; Expire 1 week 86400 ); Minimum 24 hours @ NS ns1.domain_to_ As you can see in the first line of the zone file ($TTL 86400) this defines the default TTL for all existing records to 86400 seconds (that means 24 hours).This same story is also true for the Internet and domain names.
Once the move is over : in case you have the nameserver hosted on some remote service and don’t have full control of your DNS zone you might not be able to do this and you will be limited to the control panel you will have there.
In this case talk with your hosting support to have them lower the TTL for you.
I wanted to point this out explicitly to avoid any confusion as you'll see it displayed both ways across the Internet.
A name server is a specialized server on the Internet that handles queries or questions from your local computer, about the location of a domain name's various services.
But just how exactly did your computer know what webpage to display for you, and what server to pull it from?
Your web-browser knows you typed In Motion into the address bar.Once that time has passed we can safely proceed with the move and change the actual IPs to point to the new server.I have assumed in this example that the nameservers will remain unchanged, but if you are going to move them also to the new server all you need to do is to be sure that you will configure them the same way.Then wait the previous minimum value, make your changes, verify their correctness, and turn this value back up. Remember this value can be overridden on individual resource records.” So as you can see this is not at all a big secret and the RFC even explains what you need to do in such situations…Now I will exemplify this on a small example where I will consider having an authoritive nameserver running BIND9 and the zone .Set this as large as is comfortable given how often you update your nameserver.