Re: Migrating to new ISP


"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message news:%23fSfRkgmIHA.5260@xxxxxxxxxxxxxxxxxxxxxxx

"Barry" <bazagee@xxxxxxxxxxx> wrote in message news:OTK9$1bmIHA.6064@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I'm looking for advice on moving to a new ISP in a smooth manner with little or no down time to our public websites, MX etc.

Change the TTL to something small at LEAST one full TTL period ahead of the
change.

E.g., if you TTL is 1 day, then at least a day ahead, change it to 5 minutes or
some such.

My concern is how to do this with Win2k DNS services. I will have new IP's mapped to the Nics of our servers in advance and have contacted our Domain registrant to see if we can add multiple ip's to our nameserver records. I was hoping to be able to propagate downstream routers before the phyisical changeover. We have two public facing DNS server, Primary and Secondary zones.

Can this be done or what is the better way of approaching this?
TIA

TTL settings are the key and it doesn't matter if it is Windows DNS or some
(unknown) ISP/Registrar DNS server (e.g., BIND).

BTW, most companies should NOT be running their own public DNS but
should be using the REGSTRAR provided DNS Servers so you might wish
to consider this before performing this move and just use that instead.


Why you advice so strongly for most of the companies to do not run their own dns services?

.

Relevant Pages

  • Re: Deathrow Cluster down again
    ... problem with Verizon (or even Verizon in Boston) ... Configuring a DNS server is not terribly difficult these days. ... Once you are satisfied that everything is working correctly, you should increase the TTL to at least twenty-four hours. ...
    (comp.os.vms)
  • Re: Migrating to new ISP
    ... I'm looking for advice on moving to a new ISP in a smooth manner with ... little or no down time to our public websites, ... Change the TTL to something small at LEAST one full TTL period ahead of the ... We have two public facing DNS server, ...
    (microsoft.public.win2000.dns)
  • Re: PTR? what the heck is it?
    ... > zero, why should mail be blocked because of that? ... > to live) merely tells the DNS server how long to refresh ... how would that be associated to potential spam? ... > that i set my TTL to 30... ...
    (comp.security.misc)
  • Re: Caching nameserver
    ... > google.com means a fresh TLD lookup, ... come as a tradeoff to DNS server load. ... Another common scenario for changing TTL value to a smaller value is ... Using dig, we can see what the TTL for google.com is ...
    (comp.os.linux.networking)
  • Re: Windows 2003 R2 SP2 DNS Event ID 3000
    ... The DNS server sometime got Event ID 3000 error on event log ... recursion avail. ... refresh = 900 (15 mins) ... default TTL = 3600 ...
    (microsoft.public.win2000.dns)
Quantcast