Question : DNS impact In Network Migration.

DNS impact In Network Migration.

We have our current Site site1 with all servers.
we built a new  site site2 in a different geographical location, and installed new servers with similar applications as the old ones.

my concern about DNS is while we have some customers accessing our old servers then all of sudden they will have to access the new servers do they need to flush their DNS cache or would this work seamlessly?

Note the names of the new servers are similar to the old ones but the IPs are different.
I have been told about changing the TTL on DNS, but can not understand it well and why should I do that.

Thanks

Answer : DNS impact In Network Migration.

Yes, you should change the TTL on the records in the old servers.  TTL = Time To Live.  It is a setting that tells the requesting DNS server how long it can cache that record before it should be considered stale.

By shortening the TTL prior to changing the records, it will force any querying DNS server to auto-flush the records quicker, which will ensure that there are no stale records pointing to the old IPs.  After you change the TTL to something very short, and after sufficient time has passed that the old DNS records can no longer be cached, you should be able to change the IP addresses to the new addresses, and the maximum amount of time that the servers will be unreachable will be whatever the TTL you configured on the old records.

For example:

DNS server A says "Where is host B?"  You respond with an IP that has a TTL of 24 hours.
Then, you change the TTL to be 30 minutes.
WAIT 24 HOURS (the length of your previous TTL).
After 24 hours, the old caches record goes stale, and DNS server A must request a new one.  This new one has a TTL of 30 minutes.
You change your IP addresses immediately after DNS server A gets the record for Host B (worst case scenario).
The net result is that any hosts using DNS A for resolution will not be able to find Host B for..  29 and a half minutes (the length of time it will take the incorrect record to go stale in DNS A's cache).


HTH,
exx
Random Solutions  
 
programming4us programming4us