On 13-Dec-2005, at 16:28, Steven M. Bellovin wrote:
In message
[EMAIL PROTECTED], Sam Cr
ooks writes:
I would think you would want to drop your DNS record TTLs for all
domains being moved to something very low several days before the
switch-over period.
More precisely, you want to
Joe Abley wrote:
You also want to check all the registries which are superordinate to
zones your server is authoritative for, and check that any IP addresses
stored in those registries for your nameserver are updated, otherwise
you will experience either immediate or future glue
On 14-Dec-05, at 10:02 AM, Joe Abley wrote:
You also want to check all the registries which are superordinate
to zones your server is authoritative for, and check that any IP
addresses stored in those registries for your nameserver are
updated, otherwise you will experience either
On 14-Dec-2005, at 10:17, Joe Maimon wrote:
Joe Abley wrote:
You also want to check all the registries which are superordinate
to zones your server is authoritative for, and check that any IP
addresses stored in those registries for your nameserver are
updated, otherwise you will
On Wed, Dec 14, 2005 at 10:02:56AM -0500, Joe Abley wrote:
On 13-Dec-2005, at 16:28, Steven M. Bellovin wrote:
In message
[EMAIL PROTECTED], Sam Cr
ooks writes:
I would think you would want to drop your DNS record TTLs for all
domains being moved to something very low several days
On 14-Dec-2005, at 11:52, [EMAIL PROTECTED] wrote:
currently in the middle of such a safe, conservative
transition leads me to believe that there will -NEVER-
be a point w/ there are no queries to the old address.
(he says, 24 months into a transition...)
On 14-Dec-05, at 10:02 AM, Joe Abley wrote:
You also want to check all the registries which are superordinate
to zones your server is authoritative for, and check that any IP
addresses stored in those registries for your nameserver are
updated, otherwise you will experience
On Wed, Dec 14, 2005 at 10:29:52AM -0500, Joe Abley wrote:
There are registries that store A records for nameservers that aren't
subordinate to the zones they publish. While it'd be probably
And for those that don't...some administrators (your predecessor
hostmaster? the admin of zones you
assuming you've got the old box and the new one running
concurrently, you could run tcpdump on the old box with a
filter to only catch dns requests to the old ip. Let it run
for 24-48 hours and you could see who/what was still
querying the old ip.
-e
-Original Message-
From: [EMAIL
From: Ejay Hire [EMAIL PROTECTED]
To: 'Eric Kagan' [EMAIL PROTECTED], nanog@merit.edu
Subject: RE: Gothcas of changing the IP Address of an Authoritative DNS Server
Date: Wed, 14 Dec 2005 13:15:42 -0600
assuming you've got the old box and the new one running
concurrently, you could run
Title: Message
We need to move our
Primary DNS server from legacy IP space provided by our upstreams toour
ARIN Assigned IP space. I am looking for advice and any gotchas. I
couldn't find any white papers to this affect or archived articles or
postings. If someone does have a resource for
I would think you would want to drop your DNS record TTLs for all
domains being moved to something very low several days before the
switch-over period.
On 12/13/05, Eric Kagan [EMAIL PROTECTED] wrote:
We need to move our Primary DNS server from legacy IP space provided by our
upstreams to
In message [EMAIL PROTECTED], Sam Cr
ooks writes:
I would think you would want to drop your DNS record TTLs for all
domains being moved to something very low several days before the
switch-over period.
More precisely, you want to change the TTL on the NS records, which are
in the parent zone.
13 matches
Mail list logo
