[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: briansp@walid.com (Brian W. Spolarich)
Cc: patrick@gandi.net (Patrick), ietf-provreg@cafax.se
From: Bill Manning <bmanning@isi.edu>
Date: Tue, 6 Feb 2001 07:57:30 -0800 (PST)
In-Reply-To: <IPEMICCPDPPICMIONJIOEEACCCAA.briansp@walid.com> from "Brian W. Spolarich" at Feb 06, 2001 10:02:47 AM
Sender: owner-ietf-provreg@cafax.se
Subject: Re: Nameserver as object/entity or not ?

% 
% | >From experience, I can tell you that it is used. I was working before
% | in an ISP. One day we had to change our Internet connexion, which
% | changed the IP of our nameservers, thus the need to change the
% | properties of all domains using these nameservers.
% | I'm working in a Registrar now, and it happens that customer ask us
% | to change 50 or 100 domains at the same time because they change
% | nameservers or they change IP of one nameserver.

A case in point.  A server was recently renumbered and the host record
at the registrar was modified.  This server was/is hosting a number
of distinct zone entries.  Apparently the internal protocol tracked
the new number at a number of levels but did not work across the board.
This server also serves as a server for a number of ccTLDs and the "glue"
records for this server at those ccTLDs was -NOT- automatically updated...
leading to "lame" server indications.   So the protocol ought to ensure 
that when a "host" record is modified, that it can be tracked throughout
the system.

-- 
--bill

Home | Date list | Subject list