Changing ip addresses for NS records

[Mark Andrews]

> Sorry but what do you mean by this:
> > If
> > however the OP has allowed his clients to use names within the
> > client zones for the nameservers then he (or maybe his clients)
> > will need to contact the registars for each of the client zones.
> Thanks a lot!

	The way the DNS was designed to be run.  You only need to update
	one set of address and glue records (via whois).  The client zones
	don't change only the ISP's zone changes.

	isp.com. SOA ns1.isp.com. ...
	isp.com. NS  ns1.isp.com.	
	isp.com. NS  ns2.isp.com.	
	isp.com. NS  ns3.isp.com.	
	ns1.isp.com. A X.X.X.1	; nameserver on network X.X.X/24
	ns2.isp.com. A Y.Y.Y.1	; nameserver on network Y.Y.Y/24
	ns3.isp.com. A Z.Z.Z.1 	; nameserver on network Z.Z.Z/24

	client1.com. SOA ns1.isp.com. ...
	client1.com. NS  ns1.isp.com.	
	client1.com. NS  ns2.isp.com.	
	client1.com. NS  ns3.isp.com.	

	client2.com. SOA ns1.isp.com. ...
	client2.com. NS  ns1.isp.com.	
	client2.com. NS  ns2.isp.com.	
	client2.com. NS  ns3.isp.com.	

	The way ISPs sometime do it that ends up with a lot more
	administrative work when addresses change as every set of
	address and glue records needs to be updated.  This requires
	talking to every registrar (registry).  This defeats the
	level of indirection NS records provide.  Every client zone
	changes as well and the ISP's zone.  It also requires the
	parent zones to hold more glue.

	isp.com. SOA ns1.isp.com. ...
	isp.com. NS  ns1.isp.com.	
	isp.com. NS  ns2.isp.com.	
	isp.com. NS  ns3.isp.com.	
	ns1.isp.com. A X.X.X.1	; nameserver on network X.X.X/24
	ns2.isp.com. A Y.Y.Y.1	; nameserver on network Y.Y.Y/24
	ns3.isp.com. A Z.Z.Z.1 	; nameserver on network Z.Z.Z/24

	client1.com. SOA ns1.client1.com. ...
	client1.com. NS  ns1.client1.com.	
	client1.com. NS  ns2.client1.com.	
	client1.com. NS  ns3.client1.com.	
	ns1.client1.com. A X.X.X.1	; nameserver on network X.X.X/24
	ns2.client1.com. A Y.Y.Y.1	; nameserver on network Y.Y.Y/24
	ns3.client1.com. A Z.Z.Z.1 	; nameserver on network Z.Z.Z/24

	client2.com. SOA ns1.client2.com. ...
	client2.com. NS  ns1.client2.com.	
	client2.com. NS  ns2.client2.com.	
	client2.com. NS  ns3.client2.com.	
	ns1.client2.com. A X.X.X.1	; nameserver on network X.X.X/24
	ns2.client2.com. A Y.Y.Y.1	; nameserver on network Y.Y.Y/24
	ns3.client2.com. A Z.Z.Z.1 	; nameserver on network Z.Z.Z/24

 
> > > I did the same thing a few months ago. All you have to do is to notify
> > > the registrar of the domain that the nameservers belong to, and of
> > > course modify the nameserver addresses in BIND. If your nameservers
> > > are
> > >
> > > ns1.foobar.com
> > > ns2.foobar.com
> > > ns3.foobar.com=20
> > >
> > > all you would need to do is go to your registrars website, modify the
> > > IP addresses of the nameservers for foobar.com (name stays the same),
> > > and modify the entries in the foobar.com zone on your master.
> > >
> > > The SOA shouldn't be effected at all. The name of the box is staying
> > > the same, ns1.foobar.com is still ns1.foobar.com, so the SOA will be
> > > fine.
> >
> > When you change the zone content you change the SOA record.
> >
> > In theory this should just be changing the three host entries
> > in the whois which will then propogate down as changes to the
> > glue address records in the parent zone.
> >
> > None of the client domains should need to be touched assuming
> > that the client domains all use the same nameserver names.  If
> > however the OP has allowed his clients to use names within the
> > client zones for the nameservers then he (or maybe his clients)
> > will need to contact the registars for each of the client zones.
> >
> > Mark
> >
> > > The only thing you should do (if possible) is to have the servers
> > > answer queries at both the new and old IP addresses for some time,
> > > that way if the registrar checks, you answer from the new address.
> > >
> > > Peace,
> > > Jim
> > > =20
> > >
> > > On 5/31/05, Bind Mailing List <bind_ml40 at telusquebec.net> wrote:
> > > > We are an internet provider and we have 3 DNS that have authority for
> mor=
> > > e than 2500 domains. We would like to change the 3 ip addresses of these
> DN=
> > > S but we want to keep their names. We know that the registrars have
> records=
> > >  of their names.
> > > >=20
> > > >=20
> > > > Do they have records of their ip addresses too (for these NS records)?
> > > >=20
> > > >=20
> > > >=20
> > > > What do we have to do before changing theirs addresses?
> > > >=20
> > > >=20
> > > >=20
> > > > Which steps do we have to follow to avoid any problems?
> > > >=20
> > > >=20
> > > >=20
> > > > Do you know if the registrars can change these adresses for all of our
> do=
> > > mains (soa) automatically?
> > > >=20
> > > >=20
> > > >=20
> > > > What could arrive with the root servers?
> > > >=20
> > > >=20
> > > >=20
> > > > The registrars are icann.org, cira.ca ...
> > > >=20
> > > >=20
> > > >=20
> > > > Thanks a lot for your help!
> > > >=20
> > > >=20
> > > >=20
> > > >
> > >
> > >
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org
> >
> >
> >
> 
> 
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org