Autor: Lukasz Ploszajski (lukasz_at_nask.org.pl)
Data: Wed 06 Sep 1995 - 09:06:03 MET DST
Mysle, ze to moze zainteresowac troche osob...
-Lukasz
---------- Forwarded message ----------
Date: Tue, 05 Sep 1995 18:28:06 +0200
From: Geert Jan de Groot <GeertJan.deGroot_at_ripe.net>
Subject: Changes at ns.uu.net
Hi,
UUnet is in the process of changing its nameserver setup,
but the plans are not very well published at this moment.
Since this machine provides nameserver services for parts
of the European Internet, I thought it would be wise
to tell what I found so far.
ns.uu.net had performance problems, as it was running
primary/secondary for many thousand zones, and also
was used as resolver (caching nameserver).
The plan is to split off resolver functionality from
the authority functionality, and spread the load for
both to a number of machines.
The resolvers will be called cache00.ns.uu.net (and 01, ...)
and the authority machines auth00.ns.uu.net (and onwards...).
ns.uu.net as physical machine should die over time.
As first step, a new cache machine has been brought online
(cache00.ns.uu.net), and customers that used to resolve
off ns.uu.net have been asked to change their setup.
Recursion has been switched off at ns.uu.net.
Later, zones will be moved from ns.uu.net to auth00.ns.uu.net
(and onwards). No need to contact UUnet, they will contact the
SOA contacts of the zones involved when they are ready to do so.
Unfortunately, some people misunderstood and have
changed glue records, which is not intended.
As should be obvious, cache00.ns.uu.net [198.6.1.1]
should only be listed in /etc/resolv.conf (and equivalent),
and NEVER in your zone files.
At this moment, I found that some popular nameservers
have polluted data:
ns.uu.net. 565706 A 137.39.1.3 (OK)
ns.uu.net. 299907 A 198.6.1.1 (ERROR!!!)
ns.uu.net. 311083 A 137.191.2.149 (ERROR!!!)
Of these, only the first line is correct; the second IP adress
is the IP address of cache00, which obviously is not authoritive.
I don't know where the 3rd line comes from.
Because of the possibility of configuration errors, by less
experienced people, UUnet has been cautiously only providing
instructions targeted for each audience.
However, this has caused some confusion while debugging
which is why I asked about this.
Please use caution if you must spread this info.
To proceed, please remove all glue records of ns.uu.net in your
zone files (nobody but UUnet needs glue records, so REMOVE them),
and check & restart your nameserver as appropiate.
If UUnet is running secondary for a zone you maintain,
they will contact you in time.
Hope this helps,
Geert Jan
PS: I assume everybody have seen the contents of the changed named.root
file at rs.internic.net?
To archiwum zostało wygenerowane przez hypermail 2.1.7 : Wed 19 May 2004 - 15:52:38 MET DST