Re: DNS Synchronization
From: Herb Martin (news_at_LearnQuick.com)
Date: 02/06/05
- Next message: DavidM: "Primary/Secondary DNS Issue"
- Previous message: William Stacey [MVP]: "Re: Problems when we added a sub domain"
- In reply to: Roland Hall: "Re: DNS Synchronization"
- Next in thread: Ed Horley: "Re: DNS Synchronization"
- Reply: Ed Horley: "Re: DNS Synchronization"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 6 Feb 2005 10:28:57 -0600
> 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.
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" <nobody@nowhere> wrote in message news:#hz1ABDDFHA.2232@TK2MSFTNGP14.phx.gbl... > "Herb Martin" wrote in message > news:OMavdd%23CFHA.208@TK2MSFTNGP12.phx.gbl... > : "Roland Hall" <nobody@nowhere> wrote in message > : news:u3VFUJyCFHA.392@TK2MSFTNGP14.phx.gbl... > : > 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 > >
- Next message: DavidM: "Primary/Secondary DNS Issue"
- Previous message: William Stacey [MVP]: "Re: Problems when we added a sub domain"
- In reply to: Roland Hall: "Re: DNS Synchronization"
- Next in thread: Ed Horley: "Re: DNS Synchronization"
- Reply: Ed Horley: "Re: DNS Synchronization"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
