1996-06-26 - Re: domain name zapping threat by Internic

Header Data

From: Herr Wendigo <wendigo@gti.net>
To: shifter@portal.stwing.upenn.edu (Shifter)
Message Hash: 8821d2018ce3e848063224e47b955c001ee8c329624c5789fec1b5bac90c3feb
Message ID: <199606251727.NAA14059@apollo.gti.net>
Reply To: <199606251353.JAA07632@portal.stwing.upenn.edu>
UTC Datetime: 1996-06-26 00:56:47 UTC
Raw Date: Wed, 26 Jun 1996 08:56:47 +0800

Raw message

From: Herr Wendigo <wendigo@gti.net>
Date: Wed, 26 Jun 1996 08:56:47 +0800
To: shifter@portal.stwing.upenn.edu (Shifter)
Subject: Re: domain name zapping threat by Internic
In-Reply-To: <199606251353.JAA07632@portal.stwing.upenn.edu>
Message-ID: <199606251727.NAA14059@apollo.gti.net>
MIME-Version: 1.0
Content-Type: text


An entity claiming to be Shifter wrote:
: Nothing stops anyone from running their own name server.  However, the root
: servers are what 99% of the nameservers out there point at.  No one is going
: to use dns.joe.schmoe.org as their primary nameserver.

Except of course schmoe.org.  Primary name service is usually provided
by the organization's own nameserver.  The secondary name server should
(as per the rfc whose number I forget at the moment) be on a separate
network segment.  Anyone who lists a machine from root-servers.net as their
primary needs to learn a bit more about DNS.  Root servers exist to provide
an authoritative starting point for recursive lookups, they do not provide
name service for anything other than top level domains (com. edu. net. etc.).

The NIC has the power to remove domains based upon it's authority among 
the root servers.

- -- 
    Mark Rogaski   | Why read when you can just sit and |      Member
  GTI System Admin |         stare at things?           | Programmers Local
  wendigo@gti.net  | Any expressed opinions are my own  |     # 0xfffe
 wendigo@pobox.com | unless they can get me in trouble. |     APL-CPIO

Version: 2.6.2