nameserver
Click on the red underlined text to get to the source
...
A problem I've found in quite some nameservers is that the various
timers have been set (far) too low. Especially for top level ...
... top level domain
nameservers this causes unnecessary traffic over international and
intercontinental links ...
... I've seen it happen on various occasions that hosts got bombarded by
nameserver requests without knowing why. On investigation it turned
out then that such a host was supposed to (i.e., the information was
...
... addr.arpa)) domain, without that host's nameserver manager having
been asked or even been told so!
...
... domain registrars accept registrations
of nameservers without checking if primary (!) and secondary servers
have been set up, informed, or even asked. It should also be noted
that a combination of long-lasting unreachability of primary
...
... have been set up, informed, or even asked. It should also be noted
that a combination of long-lasting unreachability of primary
nameservers, (therefore) expiration of zone information, plus static
IP routing, can lead to massive network traffic ...
...
In a sense similar to point 3. Sometimes nameserver managers enter MX
records in their zone files that point to external hosts, without
...
... first asking or even informing the systems managers of those external
hosts. This has to be fought out between the nameserver manager and
the systems managers involved. Only as a last resort, if really
nothing helps to get the offending records removed ...
...
It is required that there be a least 2 nameservers for a domain. For
obvious reasons the nameservers ...
... nameservers for a domain. For
obvious reasons the nameservers for top level domains need to be very
...
... Europe and 2 in the USA, but there
may of course be more on either side. An excessive number of
nameservers is not a good idea though; a recommended maximum is 7
nameservers. In Europe ...
... nameservers is not a good idea though; a recommended maximum is 7
nameservers. In Europe, EUnet has offered to run secondary server
for each European top level ...
... Wildcard MX records should be avoided where possible. They often
cause confusion and errors: especially beginning nameserver managers
tend to overlook the fact that a host/domain ...
... There appears to be a common misunderstanding that one of the data
fields (usually the second field) in HINFO records is optional. A
recent scan of all reachable nameservers in only one country revealed
some 300 incomplete HINFO records. Specifying two data fields in a
...
...
Nameservers and resolvers aren't flawless. Bogus queries should be
kept from being forwarded to the root servers ...
... addresses. To catch such queries, every nameserver should run
primary for the 0.in-addr.arpa and 255.in-addr.arpa zones; the zone
files need only contain a SOA and an NS ...
... NS record.
Also each nameserver should run primary for 0.0.127.in-addr.arpa;
that zone file should contain a SOA and NS record and an entry:
...
... problems.
Running secondary nameserver off another secondary nameserver is
possible, but not recommended unless really necessary: there are
...
...
Running secondary nameserver off another secondary nameserver is
possible, but not recommended unless really necessary: there are
known cases where it has led to problems like bogus TTL values ...
... TTL values. This
can be caused by older or flawed implementations, but secondary
nameservers in principle should always transfer their zones from the
official primary nameserver.
...
... nameservers in principle should always transfer their zones from the
official primary nameserver.
...
...
The Domain Name System and nameserver are purely technical tools, not
meant in any way to exert control or impose politics. The function of
...
... removing a domain's
entry from the nameserver zone files; this of course should be done
only with extreme care and only as a last resort.
...
... NS records for subdomains, top level domain nameserver
managers should realize that the people setting up the nameserver ...
... nameserver
managers should realize that the people setting up the nameserver for
a subdomain often are rather inexperienced and can make mistakes that
can easily lead to the subdomain becoming completely unreachable or
...
... NS record, the
(top level) nameserver manager does a couple of sanity checks on the
new nameserver ...
... nameserver manager does a couple of sanity checks on the
new nameserver (SOA record and timers OK?, MX records present where
needed? No obvious errors made? Listed secondary servers
...
... nameservers
- nameservers set up to use external hosts as forwarders
without permission from those hosts ...