Re: Fwd: The Root has got an A record

2005-10-12 Thread Bill Stewart

Back in the mid-80s, when some people at Bell Labs were trying to get
the rest of us there onto the DNS bandwagon, there were some people
who didn't like it.  Pike and Weinberger put out deep theoretical
papers  like The Hideous Name on relative vs. absolute names and the
effects of syntax (available at
http://cm.bell-labs.com/cm/cs/doc/85/1-05.ps.gz ), and the Plan 9
naming structure, and Honeyman and Bellovin wrote pathalias to
optimize communication paths across bang-space and other namespaces. 
I mainly grumbled about the unlikelihood of everybody being willing to
let some central authority decide whose machines could be named
gandalf and mozart given the current anarchic structure of uucp
naming, a prediction which proved resoundingly wrong over the next few
years as DNS took off like wildfire because it was obviously much more
convenient. :-)

The main feature of a global hierarchical namespace root is that
There Can Be Only One (Highlander, 1986).  That doesn't mean that
other people can't use the same syntax and software to describe a
different namespace that may overlap the Internet's namespace and may
resolve to the same addresses in many cases, and over the years there
have been occasional alternate-root namespaces grabbing a fraction of
a percent of the market, and sometimes they've even been administered
well enough that their few users don't all give up immediately.   But
when they do something wrong with their root, that doesn't mean that
there's anything wrong with the root - it just means that their
users may get unpredictable results, which is something they're mostly
used to anyway.

The DNS namespace is designed that lots of things can be grafted under
it, and much of the DNS name resolution software is designed to
resolve local as well as global names.  So company example.com with
globally-named servers like engineering.example.com or
london.example.com can have users who refer to those servers as
example or london as long as they administer their DNS correctly. 
And Joe-Bob's Alternate Root Services can have locally-usable names
like www.example.fun which are also globally accessible as
www.example.fun.joe-bob-alt-root-example.net by people who don't use
their name resolvers (again, if they configure everything correctly) -
but many of the alternate roots over the years haven't wanted to do
that, because it makes it obvious that they're not the real root,
just a wannabe.

There have been other global namespaces - ICQ was very popular for a
while, and it didn't get bothered by the WIPO-and-ICANN crowd because
nobody worried too much about trademark violations in a flat numerical
namespace that didn't correlate with anything else.  On the other
hand, the ENUM proposals do have serious issues of namespace policy
and centralization-vs-decentralization - should their hierarchical
number space be forced to buy E.164 numbers from the Telco Gods? 
Should anyone who has a PBX be able to manage ENUMs for extensions
under it, and should anybody with a phone number be able to define
ENUM numbers under it (e.g. 5.4.3.2.1.0.0.0.1.5.5.5.3.2.1.1 to get
extension 12345 at +1-123-555-1000, or fax.0.0.0.1.5.5.5.3.2.1.1 to
get the fax machine?)


Re: Fwd: The Root has got an A record

2005-10-11 Thread Peter Dambier


The A record for '.' is gone.

I am told it was a typo. I guess nameservers for at least one domain
where involved too. That is the reason why I had problems.

Kind regards,
Peter and Karin


Peter Dambier wrote:


See with your own eyes:

;  DiG 9.1.3  -t any . @a.public-root.net
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 18588
;; flags: qr aa rd; QUERY: 1, ANSWER: 15, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;.  IN  ANY

;; ANSWER SECTION:
.   172800  IN  SOA a.public-root.net. 
hostmaster.public-root.net.\
2005101006 43200 3600 
1209600 14400

.   172800  IN  A   57.67.193.188
.   172800  IN  NS  k.public-root.net.
.   ...
.   172800  IN  NS  j.public-root.net.

;; Query time: 81 msec
;; SERVER: 205.189.71.2#53(a.public-root.net)
;; WHEN: Mon Oct 10 16:01:11 2005


 Original Message 
Return-Path: [EMAIL PROTECTED]
X-Flags: 
Delivered-To: GMX delivery to [EMAIL PROTECTED]
Received: (qmail invoked by alias); 10 Oct 2005 13:07:54 -
Received: from LAIR.LIONPOST.NET (EHLO LAIR.LIONPOST.NET) [199.5.157.32]
  by mx0.gmx.net (mx072) with SMTP; 10 Oct 2005 15:07:54 +0200
Received: from list.public-root.com ([199.5.157.32])
by LAIR.LIONPOST.NET with esmtp (Exim 4.24)id 1EOx3o-ny-HQ
for [EMAIL PROTECTED]; Mon, 10 Oct 2005 08:47:20 -0400
Received: from [206.254.45.93] (helo=ruby.cynikal.net ident=qmremote)
by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1EOx3n-nt-5J
for [EMAIL PROTECTED]; Mon, 10 Oct 2005 08:47:19 -0400
Received: (qmail 9881 invoked by uid 1018); 10 Oct 2005 13:10:36 -
Received: from localhost ([EMAIL PROTECTED])
by localhost with SMTP; 10 Oct 2005 13:10:36 -
Date: Mon, 10 Oct 2005 09:10:36 -0400 (EDT)
From: Joe Baptista [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Pr-plan] BAD NEWS Re: IASON Root Domain Observatory (fwd)
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: pr-plan.LAIR.LIONPOST.NET
List-Unsubscribe: http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan,
mailto:[EMAIL PROTECTED]
List-Archive: http://LAIR.LIONPOST.NET/pipermail/pr-plan
List-Post: mailto:[EMAIL PROTECTED]
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan,
mailto:[EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-GMX-Antivirus: 0 (no virus found)
X-GMX-Antispam: 0 (Mail was not recognized as spam)
X-GMX-UID: /QI4Y8R1eSEkOtTJ43QhaXN1IGRvb4Di


Folks - got some bad news.  The Public-Root has aquired an A record - yup
thats right - an A record.  Which see below.  Have tried to contact Paul
Scheepers - our absent minded root operator - who now hovers very close to
criminal conspiracy - to get him to fix this mistake.  Noone is at home at
the inn.  Not good.  See appened message to Peter Dambier and our
public-root associates.

I have no idea how a root will respond with an A record in it.  Should be
interesting - but have no doubt a few things out in the wild have been
broken.

regards
joe

-- Forwarded message --
Date: Mon, 10 Oct 2005 09:03:04 -0400 (EDT)
From: Joe Baptista [EMAIL PROTECTED]
To: Peter Dambier [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED]
Subject: Re: IASON Root Domain Observatory


Report this to NANOG and the IETF.  Make sure you send them a copy of my
response and the headers of this message.  I am holding UNIDT personally
responsible for this technical nightmare.

regards
joe

On Mon, 10 Oct 2005, Peter Dambier wrote:


Kewl, '.' has got an A record :)

;  DiG 9.1.3  @a.public-root.net . axfr
;; global options:  printcmd
.   172800  IN  SOA a.public-root.net. 
hostmaster.public-root.net. 2005100906 43200 3600 1209600 14400

.   172800  IN  A   57.67.193.188
.   172800  IN  NS  a.public-root.net.



Joe Baptista, Official Public-Root Representative and Lobbyist to the
United States Congress and Senate / Tel: +1 (202) 517-1593

Public-Root Disclosure Documents: http://www.cynikal.net/~baptista/P-R/
Public-Root Discussion Forum: 
http://lair.lionpost.net/mailman/listinfo/pr-plan




___
Pr-plan mailing list
[EMAIL PROTECTED]
http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan





--
Peter and Karin Dambier
Public-Root
Graeffstrasse 14
D-64646 Heppenheim
+49-6252-671788 (Telekom)
+49-179-108-3978 (O2 Genion)
+49-6252-750308 (VoIP: sipgate.de)
+1-360-448-1275 (VoIP: freeworldialup.com)
mail: [EMAIL PROTECTED]
http://iason.site.voila.fr
http://www.kokoom.com/iason



Re: Fwd: The Root has got an A record

2005-10-11 Thread Andre Oppermann


Peter,

nobody here cares even the slightest bit for your public-root problems.

Please stop spamming NANOG lists NOW!

--
Andre


Peter Dambier wrote:


The A record for '.' is gone.

I am told it was a typo. I guess nameservers for at least one domain
where involved too. That is the reason why I had problems.

Kind regards,
Peter and Karin


Peter Dambier wrote:



See with your own eyes:

;  DiG 9.1.3  -t any . @a.public-root.net
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 18588
;; flags: qr aa rd; QUERY: 1, ANSWER: 15, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;.  IN  ANY

;; ANSWER SECTION:
.   172800  IN  SOA a.public-root.net. 
hostmaster.public-root.net.\
2005101006 43200 3600 
1209600 14400

.   172800  IN  A   57.67.193.188
.   172800  IN  NS  k.public-root.net.
.   ...
.   172800  IN  NS  j.public-root.net.

;; Query time: 81 msec
;; SERVER: 205.189.71.2#53(a.public-root.net)
;; WHEN: Mon Oct 10 16:01:11 2005


 Original Message 
Return-Path: [EMAIL PROTECTED]
X-Flags: 
Delivered-To: GMX delivery to [EMAIL PROTECTED]
Received: (qmail invoked by alias); 10 Oct 2005 13:07:54 -
Received: from LAIR.LIONPOST.NET (EHLO LAIR.LIONPOST.NET) [199.5.157.32]
  by mx0.gmx.net (mx072) with SMTP; 10 Oct 2005 15:07:54 +0200
Received: from list.public-root.com ([199.5.157.32])
by LAIR.LIONPOST.NET with esmtp (Exim 4.24)id 1EOx3o-ny-HQ
for [EMAIL PROTECTED]; Mon, 10 Oct 2005 08:47:20 -0400
Received: from [206.254.45.93] (helo=ruby.cynikal.net ident=qmremote)
by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1EOx3n-nt-5J
for [EMAIL PROTECTED]; Mon, 10 Oct 2005 08:47:19 -0400
Received: (qmail 9881 invoked by uid 1018); 10 Oct 2005 13:10:36 -
Received: from localhost ([EMAIL PROTECTED])
by localhost with SMTP; 10 Oct 2005 13:10:36 -
Date: Mon, 10 Oct 2005 09:10:36 -0400 (EDT)
From: Joe Baptista [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Pr-plan] BAD NEWS Re: IASON Root Domain Observatory (fwd)
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: pr-plan.LAIR.LIONPOST.NET
List-Unsubscribe: http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan,
mailto:[EMAIL PROTECTED]
List-Archive: http://LAIR.LIONPOST.NET/pipermail/pr-plan
List-Post: mailto:[EMAIL PROTECTED]
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan,
mailto:[EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-GMX-Antivirus: 0 (no virus found)
X-GMX-Antispam: 0 (Mail was not recognized as spam)
X-GMX-UID: /QI4Y8R1eSEkOtTJ43QhaXN1IGRvb4Di


Folks - got some bad news.  The Public-Root has aquired an A record - yup
thats right - an A record.  Which see below.  Have tried to contact Paul
Scheepers - our absent minded root operator - who now hovers very 
close to
criminal conspiracy - to get him to fix this mistake.  Noone is at 
home at

the inn.  Not good.  See appened message to Peter Dambier and our
public-root associates.

I have no idea how a root will respond with an A record in it.  Should be
interesting - but have no doubt a few things out in the wild have been
broken.

regards
joe

-- Forwarded message --
Date: Mon, 10 Oct 2005 09:03:04 -0400 (EDT)
From: Joe Baptista [EMAIL PROTECTED]
To: Peter Dambier [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED]
Subject: Re: IASON Root Domain Observatory


Report this to NANOG and the IETF.  Make sure you send them a copy of my
response and the headers of this message.  I am holding UNIDT personally
responsible for this technical nightmare.

regards
joe

On Mon, 10 Oct 2005, Peter Dambier wrote:


Kewl, '.' has got an A record :)

;  DiG 9.1.3  @a.public-root.net . axfr
;; global options:  printcmd
.   172800  IN  SOA a.public-root.net. 
hostmaster.public-root.net. 2005100906 43200 3600 1209600 14400

.   172800  IN  A   57.67.193.188
.   172800  IN  NS  a.public-root.net.




Joe Baptista, Official Public-Root Representative and Lobbyist to the
United States Congress and Senate / Tel: +1 (202) 517-1593

Public-Root Disclosure Documents: http://www.cynikal.net/~baptista/P-R/
Public-Root Discussion Forum: 
http://lair.lionpost.net/mailman/listinfo/pr-plan




___
Pr-plan mailing list
[EMAIL PROTECTED]
http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan









Re: Fwd: The Root has got an A record

2005-10-11 Thread Michael . Dillon

 nobody here cares even the slightest bit for your public-root 
problems.
 Please stop spamming NANOG lists NOW!

Seems to me that such appeals might be a bit more
effective if you sent it privately to the list
administrators via the address published here:
http://www.nanog.org/listadmins.html

--Michael Dillon



Fwd: The Root has got an A record

2005-10-10 Thread Peter Dambier


See with your own eyes:

;  DiG 9.1.3  -t any . @a.public-root.net
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 18588
;; flags: qr aa rd; QUERY: 1, ANSWER: 15, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;.  IN  ANY

;; ANSWER SECTION:
.   172800  IN  SOA a.public-root.net. 
hostmaster.public-root.net.\
2005101006 43200 3600 1209600 
14400
.   172800  IN  A   57.67.193.188
.   172800  IN  NS  k.public-root.net.
.   ...
.   172800  IN  NS  j.public-root.net.

;; Query time: 81 msec
;; SERVER: 205.189.71.2#53(a.public-root.net)
;; WHEN: Mon Oct 10 16:01:11 2005


 Original Message 
Return-Path: [EMAIL PROTECTED]
X-Flags: 
Delivered-To: GMX delivery to [EMAIL PROTECTED]
Received: (qmail invoked by alias); 10 Oct 2005 13:07:54 -
Received: from LAIR.LIONPOST.NET (EHLO LAIR.LIONPOST.NET) [199.5.157.32]
  by mx0.gmx.net (mx072) with SMTP; 10 Oct 2005 15:07:54 +0200
Received: from list.public-root.com ([199.5.157.32])
by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1EOx3o-ny-HQ
for [EMAIL PROTECTED]; Mon, 10 Oct 2005 08:47:20 -0400
Received: from [206.254.45.93] (helo=ruby.cynikal.net ident=qmremote)
by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1EOx3n-nt-5J
for [EMAIL PROTECTED]; Mon, 10 Oct 2005 08:47:19 -0400
Received: (qmail 9881 invoked by uid 1018); 10 Oct 2005 13:10:36 -
Received: from localhost ([EMAIL PROTECTED])
by localhost with SMTP; 10 Oct 2005 13:10:36 -
Date: Mon, 10 Oct 2005 09:10:36 -0400 (EDT)
From: Joe Baptista [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Pr-plan] BAD NEWS Re: IASON Root Domain Observatory (fwd)
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: pr-plan.LAIR.LIONPOST.NET
List-Unsubscribe: http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan,
mailto:[EMAIL PROTECTED]
List-Archive: http://LAIR.LIONPOST.NET/pipermail/pr-plan
List-Post: mailto:[EMAIL PROTECTED]
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan,
mailto:[EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-GMX-Antivirus: 0 (no virus found)
X-GMX-Antispam: 0 (Mail was not recognized as spam)
X-GMX-UID: /QI4Y8R1eSEkOtTJ43QhaXN1IGRvb4Di


Folks - got some bad news.  The Public-Root has aquired an A record - yup
thats right - an A record.  Which see below.  Have tried to contact Paul
Scheepers - our absent minded root operator - who now hovers very close to
criminal conspiracy - to get him to fix this mistake.  Noone is at home at
the inn.  Not good.  See appened message to Peter Dambier and our
public-root associates.

I have no idea how a root will respond with an A record in it.  Should be
interesting - but have no doubt a few things out in the wild have been
broken.

regards
joe

-- Forwarded message --
Date: Mon, 10 Oct 2005 09:03:04 -0400 (EDT)
From: Joe Baptista [EMAIL PROTECTED]
To: Peter Dambier [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED]
Subject: Re: IASON Root Domain Observatory


Report this to NANOG and the IETF.  Make sure you send them a copy of my
response and the headers of this message.  I am holding UNIDT personally
responsible for this technical nightmare.

regards
joe

On Mon, 10 Oct 2005, Peter Dambier wrote:


Kewl, '.' has got an A record :)

;  DiG 9.1.3  @a.public-root.net . axfr
;; global options:  printcmd
.   172800  IN  SOA a.public-root.net. 
hostmaster.public-root.net. 2005100906 43200 3600 1209600 14400
.   172800  IN  A   57.67.193.188
.   172800  IN  NS  a.public-root.net.


Joe Baptista, Official Public-Root Representative and Lobbyist to the
United States Congress and Senate / Tel: +1 (202) 517-1593

Public-Root Disclosure Documents: http://www.cynikal.net/~baptista/P-R/
Public-Root Discussion Forum: http://lair.lionpost.net/mailman/listinfo/pr-plan



___
Pr-plan mailing list
[EMAIL PROTECTED]
http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan


--
Peter and Karin Dambier
Public-Root
Graeffstrasse 14
D-64646 Heppenheim
+49-6252-671788 (Telekom)
+49-179-108-3978 (O2 Genion)
+49-6252-750308 (VoIP: sipgate.de)
+1-360-448-1275 (VoIP: freeworldialup.com)
mail: [EMAIL PROTECTED]
http://iason.site.voila.fr
http://www.kokoom.com/iason



Re: Fwd: The Root has got an A record

2005-10-10 Thread Stephen J. Wilcox

i'm reading looking for your explanation but there isnt one.

and the A record is for what?

anyway its on a private dns server, the internet roots are fine so why worry? :)

Steve

On Mon, 10 Oct 2005, Peter Dambier wrote:

 
 See with your own eyes:
 
 ;  DiG 9.1.3  -t any . @a.public-root.net
 ;; Got answer:
 ;; -HEADER- opcode: QUERY, status: NOERROR, id: 18588
 ;; flags: qr aa rd; QUERY: 1, ANSWER: 15, AUTHORITY: 0, ADDITIONAL: 0
 
 ;; QUESTION SECTION:
 ;.  IN  ANY
 
 ;; ANSWER SECTION:
 .   172800  IN  SOA a.public-root.net. 
 hostmaster.public-root.net.\
  2005101006 43200 3600 
 1209600 14400
 .   172800  IN  A   57.67.193.188
 .   172800  IN  NS  k.public-root.net.
 .   ...
 .   172800  IN  NS  j.public-root.net.
 
 ;; Query time: 81 msec
 ;; SERVER: 205.189.71.2#53(a.public-root.net)
 ;; WHEN: Mon Oct 10 16:01:11 2005
 
 
  Original Message 
 Return-Path: [EMAIL PROTECTED]
 X-Flags: 
 Delivered-To: GMX delivery to [EMAIL PROTECTED]
 Received: (qmail invoked by alias); 10 Oct 2005 13:07:54 -
 Received: from LAIR.LIONPOST.NET (EHLO LAIR.LIONPOST.NET) [199.5.157.32]
by mx0.gmx.net (mx072) with SMTP; 10 Oct 2005 15:07:54 +0200
 Received: from list.public-root.com ([199.5.157.32])
   by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1EOx3o-ny-HQ
   for [EMAIL PROTECTED]; Mon, 10 Oct 2005 08:47:20 -0400
 Received: from [206.254.45.93] (helo=ruby.cynikal.net ident=qmremote)
   by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1EOx3n-nt-5J
   for [EMAIL PROTECTED]; Mon, 10 Oct 2005 08:47:19 -0400
 Received: (qmail 9881 invoked by uid 1018); 10 Oct 2005 13:10:36 -
 Received: from localhost ([EMAIL PROTECTED])
   by localhost with SMTP; 10 Oct 2005 13:10:36 -
 Date: Mon, 10 Oct 2005 09:10:36 -0400 (EDT)
 From: Joe Baptista [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Message-ID: [EMAIL PROTECTED]
 MIME-Version: 1.0
 Content-Type: TEXT/PLAIN; charset=US-ASCII
 Subject: [Pr-plan] BAD NEWS Re: IASON Root Domain Observatory (fwd)
 X-BeenThere: [EMAIL PROTECTED]
 X-Mailman-Version: 2.1.2
 Precedence: list
 List-Id: pr-plan.LAIR.LIONPOST.NET
 List-Unsubscribe: http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan,
   mailto:[EMAIL PROTECTED]
 List-Archive: http://LAIR.LIONPOST.NET/pipermail/pr-plan
 List-Post: mailto:[EMAIL PROTECTED]
 List-Help: mailto:[EMAIL PROTECTED]
 List-Subscribe: http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan,
   mailto:[EMAIL PROTECTED]
 Sender: [EMAIL PROTECTED]
 Errors-To: [EMAIL PROTECTED]
 X-GMX-Antivirus: 0 (no virus found)
 X-GMX-Antispam: 0 (Mail was not recognized as spam)
 X-GMX-UID: /QI4Y8R1eSEkOtTJ43QhaXN1IGRvb4Di
 
 
 Folks - got some bad news.  The Public-Root has aquired an A record - yup
 thats right - an A record.  Which see below.  Have tried to contact Paul
 Scheepers - our absent minded root operator - who now hovers very close to
 criminal conspiracy - to get him to fix this mistake.  Noone is at home at
 the inn.  Not good.  See appened message to Peter Dambier and our
 public-root associates.
 
 I have no idea how a root will respond with an A record in it.  Should be
 interesting - but have no doubt a few things out in the wild have been
 broken.
 
 regards
 joe
 
 -- Forwarded message --
 Date: Mon, 10 Oct 2005 09:03:04 -0400 (EDT)
 From: Joe Baptista [EMAIL PROTECTED]
 To: Peter Dambier [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
   [EMAIL PROTECTED]
 Subject: Re: IASON Root Domain Observatory
 
 
 Report this to NANOG and the IETF.  Make sure you send them a copy of my
 response and the headers of this message.  I am holding UNIDT personally
 responsible for this technical nightmare.
 
 regards
 joe
 
 On Mon, 10 Oct 2005, Peter Dambier wrote:
 
  Kewl, '.' has got an A record :)
 
  ;  DiG 9.1.3  @a.public-root.net . axfr
  ;; global options:  printcmd
  .   172800  IN  SOA a.public-root.net. 
  hostmaster.public-root.net. 2005100906 43200 3600 1209600 14400
  .   172800  IN  A   57.67.193.188
  .   172800  IN  NS  a.public-root.net.
 
 Joe Baptista, Official Public-Root Representative and Lobbyist to the
 United States Congress and Senate / Tel: +1 (202) 517-1593
 
 Public-Root Disclosure Documents: http://www.cynikal.net/~baptista/P-R/
 Public-Root Discussion Forum: 
 http://lair.lionpost.net/mailman/listinfo/pr-plan
 
 
 
 ___
 Pr-plan mailing list
 [EMAIL PROTECTED]
 http://LAIR.LIONPOST.NET/mailman/listinfo/pr-plan
 
 
 



Re: Fwd: The Root has got an A record

2005-10-10 Thread Janet Sullivan


Stephen J. Wilcox wrote:

i'm reading looking for your explanation but there isnt one.

and the A record is for what?


The A record is for . (the DNS root).  Or at least . as public-root 
sees it.



anyway its on a private dns server, the internet roots are fine so why worry? :)


It might impact people who have drunk enough of the public-root kool-aid 
to be using it instead of the ICANN root.  For everyone else, its just 
more evidence that alternative roots are usually a bad idea. ;-)


Re: Fwd: The Root has got an A record

2005-10-10 Thread Joe Blanchard



Hmm, B has the same one, and C has all the other Roots listed
as A records. Would/could this really cause any sort of an issue
though? 

Regards,
-Joe Blanchard

On Mon, 10 Oct 2005, Peter Dambier wrote:

 
 See with your own eyes:
 
 ;  DiG 9.1.3  -t any . @a.public-root.net
 ;; Got answer:
 ;; -HEADER- opcode: QUERY, status: NOERROR, id: 18588
 ;; flags: qr aa rd; QUERY: 1, ANSWER: 15, AUTHORITY: 0, ADDITIONAL: 0
 
 ;; QUESTION SECTION:
 ;.  IN  ANY
 
 ;; ANSWER SECTION:
 .   172800  IN  SOA a.public-root.net. 
 hostmaster.public-root.net.\
  2005101006 43200 3600 
 1209600 14400
 .   172800  IN  A   57.67.193.188
 .   172800  IN  NS  k.public-root.net.
 .   ...
 .   172800  IN  NS  j.public-root.net.
 
 ;; Query time: 81 msec
 ;; SERVER: 205.189.71.2#53(a.public-root.net)
 ;; WHEN: Mon Oct 10 16:01:11 2005
 
 




Re: Fwd: The Root has got an A record

2005-10-10 Thread Jon Lewis


On Mon, 10 Oct 2005, Peter Dambier wrote:


See with your own eyes:

;  DiG 9.1.3  -t any . @a.public-root.net

 ^^


;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 18588
;; flags: qr aa rd; QUERY: 1, ANSWER: 15, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;.  IN  ANY

;; ANSWER SECTION:
.   172800  IN  SOA a.public-root.net.

  ^

hostmaster.public-root.net.\
   2005101006 43200 3600 1209600 
14400

.   172800  IN  A   57.67.193.188


Who cares?  Please stop wasting NANOG bandwidth that could be better used 
debating peering/depeering with gibberish about fringe DNS systems.



Report this to NANOG and the IETF.  Make sure you send them a copy of my
response and the headers of this message.  I am holding UNIDT personally
responsible for this technical nightmare.


Make sure to also report when pigs fly and the aliens decide to publicly 
make contact.


Apologies to anyone already .procmailrc'ing Peter to /dev/null for 
sneaking this into your inbox.


--
 Jon Lewis   |  I route
 Senior Network Engineer |  therefore you are
 Atlantic Net| 
_ http://www.lewis.org/~jlewis/pgp for PGP public key_


Re: Fwd: The Root has got an A record

2005-10-10 Thread Janet Sullivan


Joe Blanchard wrote:

Hmm, B has the same one, and C has all the other Roots listed
as A records. Would/could this really cause any sort of an issue
though? 


Its not records like

a.public-root.net.  369 IN  A   205.189.71.2

that are the issue.  That's as it should be.  (Well... if you accept 
that public-root should be. ;-) )


This record, however, is not correct:

.   172800  IN  A   57.67.193.188


That is the root.

For those of you who need reminding on how DNS works...

.   the root
  / | \
 /  |  \
/   |   \
  .com .net .orgtop level domains
   | |
   | |
 yahoo  bgp4domain names
   |  |
   |  |
  wwwsea host (or subdomain)


The trailing dot is left out in day to day use when we use URLS like 
www.yahoo.com - however, its really www.yahoo.com. - note the dot on the 
end.  That's the root.


Having an A record for the root is one better than having an A record 
for, say, .edu.  In other words, this shouldn't work:


[aura.sea.bgp4.net] (ciscogeek)  nslookup . a.public-root.net
Server: a.public-root.net
Address:205.189.71.2#53

Name:   .
Address: 57.67.193.188


As for what issues it could cause, I'm not sure.  I can't think of any 
off hand, but who knows what poorly written application may not be 
expecting an A record for the root.


For most people though, it doesn't matter, because they aren't using 
public-root in the first place.


I now return you to the Cogent/Level3 thread.


Re: Fwd: The Root has got an A record

2005-10-10 Thread Peter

Janet Sullivan [EMAIL PROTECTED] wrote:
[...]
 Having an A record for the root is one better than having an A
 record for, say, .edu. In other words, this shouldn't work:

The content at http://57.67.193.188/ made me wonder if they'd not in
fact put in a *wildcard* record in the root zone. It turns out that
they haven't, so there's still some more lack of DNS Clue that hasn't
yet been demonstrated.

-- 
My swerver room, my patch panels. By the time they figure out why none of the
ports on their floor box work anymore I'll be done, dusted and down the pub
with a pint of something brewed with yeast that was smarter than they are.
- a fed up BOFH in the Monastery


Re: Fwd: The Root has got an A record

2005-10-10 Thread Valdis . Kletnieks
On Mon, 10 Oct 2005 11:51:54 EDT, Jon Lewis said:

 Make sure to also report when pigs fly and the aliens decide to publicly 
 make contact.

RFC1925 sayeth:

   (3)  With sufficient thrust, pigs fly just fine. However, this is
not necessarily a good idea. It is hard to be sure where they
are going to land, and it could be dangerous sitting under them
as they fly overhead.

Obviously, what Peter was reporting is the result of a DNS administrator
sitting under the flight path of Porcine Airlines flight 109


pgpIfeSFD2t5H.pgp
Description: PGP signature


Re: Fwd: The Root has got an A record

2005-10-10 Thread Peter Dambier


I am sorry if you feel annoyed by this, but

c.public-root.com,  Cleveland, Ohio, USA,  IP 68.255.182.111
e.public-root.com,  Montreal, Quebec, Canada,  IP 216.138.219.83
f.public-root.com,  Terre Haute, Indiana, USA,  IP 66.15.237.185
g.public-root.com,  Chicago, Illinois, USA,  IP 199.5.157.131
h.public-root.com,  Des Moines, Iowa, USA,  64.198.89.245

operate in north america, in your network. So do their customers.
It is you who will be annoyed if anything goes wrong because of
this misbehaviour.

I do not recommend using the public-root right now. I do warn
because of obvious technical problems.

I dont know what happens if '.' suddenly has a valid ip address.
I have not written windows. I dont know what Bill Gates does.
My linux did complain. That is how I did find it in the first
place.

And I know for shure '.' was not meant to have an ip address.

What can go wrong will go wrong. I have seen enough queries
for '.local' and for 'localhost' on the root-servers.

Jon Lewis wrote:

On Mon, 10 Oct 2005, Peter Dambier wrote:


See with your own eyes:

;  DiG 9.1.3  -t any . @a.public-root.net


 ^^


;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 18588
;; flags: qr aa rd; QUERY: 1, ANSWER: 15, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;.  IN  ANY

;; ANSWER SECTION:
.   172800  IN  SOA a.public-root.net.


  ^


hostmaster.public-root.net.\
   2005101006 43200 3600 
1209600 14400

.   172800  IN  A   57.67.193.188



Who cares?  Please stop wasting NANOG bandwidth that could be better 
used debating peering/depeering with gibberish about fringe DNS systems.



Report this to NANOG and the IETF.  Make sure you send them a copy of my
response and the headers of this message.  I am holding UNIDT personally
responsible for this technical nightmare.



Make sure to also report when pigs fly and the aliens decide to publicly 
make contact.


Apologies to anyone already .procmailrc'ing Peter to /dev/null for 
sneaking this into your inbox.


Better /dev/null the rest of nanog too because I am afraid there will
raise issues because of this.

So, if you really dont care ...



--
 Jon Lewis   |  I route
 Senior Network Engineer |  therefore you are
 Atlantic Net| _ 
http://www.lewis.org/~jlewis/pgp for PGP public key_





--
Peter and Karin Dambier
Public-Root
Graeffstrasse 14
D-64646 Heppenheim
+49-6252-671788 (Telekom)
+49-179-108-3978 (O2 Genion)
+49-6252-750308 (VoIP: sipgate.de)
+1-360-448-1275 (VoIP: freeworldialup.com)
mail: [EMAIL PROTECTED]
http://iason.site.voila.fr
http://www.kokoom.com/iason



Re: Fwd: The Root has got an A record

2005-10-10 Thread Jon Lewis


On Mon, 10 Oct 2005, Peter Dambier wrote:



I am sorry if you feel annoyed by this, but

c.public-root.com,  Cleveland, Ohio, USA,  IP 68.255.182.111
e.public-root.com,  Montreal, Quebec, Canada,  IP 216.138.219.83
f.public-root.com,  Terre Haute, Indiana, USA,  IP 66.15.237.185
g.public-root.com,  Chicago, Illinois, USA,  IP 199.5.157.131
h.public-root.com,  Des Moines, Iowa, USA,  64.198.89.245


Where they operate or how many alternative root's there are really 
doesn't matter.  Anyone nutty enough to rely on them gets what they have 
coming.


--
 Jon Lewis   |  I route
 Senior Network Engineer |  therefore you are
 Atlantic Net| 
_ http://www.lewis.org/~jlewis/pgp for PGP public key_


Re: Fwd: The Root has got an A record

2005-10-10 Thread Todd Vierling

On Mon, 10 Oct 2005, Peter Dambier wrote:

 I do not recommend using the public-root right now. I do warn
 because of obvious technical problems.

All you're doing is making the rest of us laugh uncontrollably as the
problems with the non-Internet Public-Root DNS servers keep stacking up.
The rest of us use actual *Internet* root DNS servers and will never see
these problems.

(I need to find my glasses, because that sign on the road ahead is hard to
read -- something about feeling droll?  Wait, that's not right)

-- 
-- Todd Vierling [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]