DNS Synchronization

  • Thread starter Thread starter Roland Hall
  • Start date Start date
R

Roland Hall

I know that if I move my domain from one web host to another that since I'm
using different name servers that it takes roughly 4 days to synchronize
around the planet. Is the same true if I change the IP address of a public
DNS server? How would any hosted domains be affected and would the
synchronization process take longer?
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
 
If you know you that you are going to change your IP, it is a good practice
to reduce the TTL of the records mapped to that IP, long before the day you
are changing the IP. You can then set the TTL back to normal after you are
done with the switch.

No, 4 days is not normal. Your host may just be lazy.

--

Sincerely,
Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
Roland Hall said:
I know that if I move my domain from one web host to another that since I'm
using different name servers that it takes roughly 4 days to synchronize
around the planet.
Click to expand...

This is not fixed nor even normal -- it is YOUR TLL
for you zone (or individual records.)

The best practice is to CHANGE you TTL at least one
full "TTL period" ahead (e.g., if you use 4 days, change
it at least 4 days ahead) -- and allow for any technician
delay or delay in updating your servers.


Take it down to something small, [ optional: perhaps even
1 hour until the day of the change the go down to 5 minutes until
after the change.]

Is the same true if I change the IP address of a public
DNS server? How would any hosted domains be affected and would the
synchronization process take longer?
Click to expand...

The issue with public DNS servers is complicated by
the fact that updates have an administrative overhead
which you cannot control.

In general, this is covered by leaving the old DNS up
during the change -- each has the correct values and
the delay is merely a nuisance.
 
in message
: : > I know that if I move my domain from one web host to another that since
: I'm
: > using different name servers that it takes roughly 4 days to synchronize
: > around the planet.
:
: This is not fixed nor even normal -- it is YOUR TLL
: for you zone (or individual records.)
:
: The best practice is to CHANGE you TTL at least one
: full "TTL period" ahead (e.g., if you use 4 days, change
: it at least 4 days ahead) -- and allow for any technician
: delay or delay in updating your servers.
:
:
: Take it down to something small, [ optional: perhaps even
: 1 hour until the day of the change the go down to 5 minutes until
: after the change.]
:
:
: > Is the same true if I change the IP address of a public
: > DNS server? How would any hosted domains be affected and would the
: > synchronization process take longer?
:
: The issue with public DNS servers is complicated by
: the fact that updates have an administrative overhead
: which you cannot control.
:
: In general, this is covered by leaving the old DNS up
: during the change -- each has the correct values and
: the delay is merely a nuisance.

I have never had to deal with this on the public side where I had access.
Moving a domain between hosts results in you being at their mercy. This
time, it is a web host asking, since they will be eliminating a 1.5mbps
connection and going with a carrier with a 3mbps connection, thus losing all
IP addressing.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
 
I have never had to deal with this on the public side where I had access.
Moving a domain between hosts results in you being at their mercy. This
time, it is a web host asking, since they will be eliminating a 1.5mbps
connection and going with a carrier with a 3mbps connection, thus losing all
IP addressing.
Click to expand...

One of the reasons, that I strongly recommend
leaving (or moving) your DNS servers at the
registrar, and neither maintaining them (directly)
yourself nor at an ISP.

I want to manage my records directly; I do not
want to maintain those DNS servers 24/7 nor
necessarily to even have two DNS servers
(personally) as required in most top level zones.

--
Herb Martin


Roland Hall said:
in message
: : > I know that if I move my domain from one web host to another that since
: I'm
: > using different name servers that it takes roughly 4 days to synchronize
: > around the planet.
:
: This is not fixed nor even normal -- it is YOUR TLL
: for you zone (or individual records.)
:
: The best practice is to CHANGE you TTL at least one
: full "TTL period" ahead (e.g., if you use 4 days, change
: it at least 4 days ahead) -- and allow for any technician
: delay or delay in updating your servers.
:
:
: Take it down to something small, [ optional: perhaps even
: 1 hour until the day of the change the go down to 5 minutes until
: after the change.]
:
:
: > Is the same true if I change the IP address of a public
: > DNS server? How would any hosted domains be affected and would the
: > synchronization process take longer?
:
: The issue with public DNS servers is complicated by
: the fact that updates have an administrative overhead
: which you cannot control.
:
: In general, this is covered by leaving the old DNS up
: during the change -- each has the correct values and
: the delay is merely a nuisance.

I have never had to deal with this on the public side where I had access.
Moving a domain between hosts results in you being at their mercy. This
time, it is a web host asking, since they will be eliminating a 1.5mbps
connection and going with a carrier with a 3mbps connection, thus losing all
IP addressing.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
Click to expand...
 
Roland,
If you need a quick fix to keep you going while you are doing the move
consider using www.zoneedit.com. They allow up to 5 free domains on an
account. Simply set them up as a secondary in your domain registration
after you build out a zone on your new account. Just make the zoneedit zone
a slave to your current zone. If, for some reason your current master (and
public primary) for the zone goes down things will flip over to zoneedit
because they are entered as a secondary. When you get your new stuff up
then you can simply add that into your domain registration and then repoint
your zoneedit account to the new name server. Make sure your firewall and
your server allow zone transfers from whatever name server zoneedit assigns
your zone to. That way it can pull the zones properly.
Hope that helps.

Regards,
Ed Horley
Microsoft MVP Server-Networking

Herb Martin said:
I have never had to deal with this on the public side where I had access.
Moving a domain between hosts results in you being at their mercy. This
time, it is a web host asking, since they will be eliminating a 1.5mbps
connection and going with a carrier with a 3mbps connection, thus losing all
IP addressing.
Click to expand...

One of the reasons, that I strongly recommend
leaving (or moving) your DNS servers at the
registrar, and neither maintaining them (directly)
yourself nor at an ISP.

I want to manage my records directly; I do not
want to maintain those DNS servers 24/7 nor
necessarily to even have two DNS servers
(personally) as required in most top level zones.

--
Herb Martin


Roland Hall said:
in message
: : > I know that if I move my domain from one web host to another that since
: I'm
: > using different name servers that it takes roughly 4 days to synchronize
: > around the planet.
:
: This is not fixed nor even normal -- it is YOUR TLL
: for you zone (or individual records.)
:
: The best practice is to CHANGE you TTL at least one
: full "TTL period" ahead (e.g., if you use 4 days, change
: it at least 4 days ahead) -- and allow for any technician
: delay or delay in updating your servers.
:
:
: Take it down to something small, [ optional: perhaps even
: 1 hour until the day of the change the go down to 5 minutes until
: after the change.]
:
:
: > Is the same true if I change the IP address of a public
: > DNS server? How would any hosted domains be affected and would the
: > synchronization process take longer?
:
: The issue with public DNS servers is complicated by
: the fact that updates have an administrative overhead
: which you cannot control.
:
: In general, this is covered by leaving the old DNS up
: during the change -- each has the correct values and
: the delay is merely a nuisance.

I have never had to deal with this on the public side where I had access.
Moving a domain between hosts results in you being at their mercy. This
time, it is a web host asking, since they will be eliminating a 1.5mbps
connection and going with a carrier with a 3mbps connection, thus losing all
IP addressing.

--
Roland Hall
/* This information is distributed in the hope that it will be useful,
but
without any warranty; without even the implied warranty of
merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
Click to expand...
Click to expand...
 
Back
Top