Dennis Carr | 10 Jun 04:37 2003
Picon

slave servers?

I'm curious, is it common practice to delegate "slave" server setups in
bind to other tier 1 servers?

-Dennis Carr

######################################################################
This is the discussion list for the Open Network Information
Center.  You can unsubscribe by sending an email containing the words
"unsubscribe discuss" in the body of the message to
"majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net".
######################################################################

gARetH baBB | 26 Jun 12:32 2003

Root

How often is this maintained with regard to "ICANN" (inc ccTLDs) zones ?

I've just come across the NS records for .tk are out of date, and it's
made me wonder what other out-of-date inaccurate records are in there.

This is not a good state of affairs, the easiest thing to do would be to
just dump opennic and use the proper accurate not-out-of-date ICANN root -
the extreme measure, but certainly hassle free.

As per the "post" to the "forum" which has just gone up, I don't trust
opennic root for ICANN zones now either.

The root zone has to be useful, ie. accurate, for people to use it - if
they suddenly find they can't rely on it, they're not going to prat about
with mechanisms as in that forum post, they're just going to give up.

As it is I'm going to ignore the full opennic root and just slave
various/certain opennic root zones (like .geek).
######################################################################
This is the discussion list for the Open Network Information
Center.  You can unsubscribe by sending an email containing the words
"unsubscribe discuss" in the body of the message to
"majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net".
######################################################################

Rhonda Hyslop | 26 Jun 21:55 2003
Picon

Re: Root

* gARetH baBB <hick <at> gink.geek> [26 Jun 2003 04:00]:
> I've just come across the NS records for .tk are out of date, and it's
> made me wonder what other out-of-date inaccurate records are in there.

I thought all requests for ICANN names were just sent on to ICANN
servers?  Am I mistaken then, and do we actually serve ICANN data?

-Rhonda
--

-- 
www.write-on.indy || write-on.homeip.net \/  http://history.ubcengineers.ca/
  Discuss the art and craft of writing   /\   UBC Engineers History Project
   That's the problem with world domination. Nobody is willing to wait for 
   it anymore, work slowly towards it, drink more and enjoy the ride more.
######################################################################
This is the discussion list for the Open Network Information
Center.  You can unsubscribe by sending an email containing the words
"unsubscribe discuss" in the body of the message to
"majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net".
######################################################################

Adam | 26 Jun 22:12 2003
Picon

Re: Root

The tier 1 servers give the tier 2 servers the addresses to use to look up
domains for each TLD. A typical OpenNIC server will use the OpenNIC tier 1
to get this info. The ICANN root servers are not used in this case.
Though, our addresses should be the same with the exception of .biz and
the TLDs that OpenNIC supports.

Adam Licata

On Thu, 26 Jun 2003, Rhonda Hyslop wrote:

> * gARetH baBB <hick <at> gink.geek> [26 Jun 2003 04:00]:
> > I've just come across the NS records for .tk are out of date, and it's
> > made me wonder what other out-of-date inaccurate records are in there.
>
> I thought all requests for ICANN names were just sent on to ICANN
> servers?  Am I mistaken then, and do we actually serve ICANN data?
>
> -Rhonda
> --
> www.write-on.indy || write-on.homeip.net \/  http://history.ubcengineers.ca/
>   Discuss the art and craft of writing   /\   UBC Engineers History Project
>    That's the problem with world domination. Nobody is willing to wait for
>    it anymore, work slowly towards it, drink more and enjoy the ride more.
> ######################################################################
> This is the discussion list for the Open Network Information
> Center.  You can unsubscribe by sending an email containing the words
> "unsubscribe discuss" in the body of the message to
> "majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net".
> ######################################################################
>
(Continue reading)

Chris Knight | 26 Jun 22:51 2003

Re: Root

Unless Robin has made significant changes to the system it works thus:

Pull down root zone/hints file from ftp site that is SUPPOSED to have THE 
up-to-date file available.

Remove any zones that we have chosen not to support, such a .biz

Insert info for OpenNIC TLDs.

Load on T1-prime server.

If we have bad data for an ICANN tld it is most likely caused by the file 
Robin's automated process pulls from the FTP server being out of date.  Second 
most likely cause would be something having broken with that cron job causing 
it not to update.  My money is on the root zone/hints file not being updated 
by ICANN, just to stop the kind of thing that OpenNIC does.

-Chris

Rhonda Hyslop wrote:
> * gARetH baBB <hick <at> gink.geek> [26 Jun 2003 04:00]:
> 
>>I've just come across the NS records for .tk are out of date, and it's
>>made me wonder what other out-of-date inaccurate records are in there.
> 
> 
> I thought all requests for ICANN names were just sent on to ICANN
> servers?  Am I mistaken then, and do we actually serve ICANN data?
> 
> -Rhonda
(Continue reading)

Ed Sawicki | 27 Jun 00:11 2003

Re: Root

On Thu, 2003-06-26 at 13:51, Chris Knight wrote:
> Unless Robin has made significant changes to the system it works thus:
> 
> Pull down root zone/hints file from ftp site that is SUPPOSED to have THE 
> up-to-date file available.
> 
> Remove any zones that we have chosen not to support, such a .biz
> 
> Insert info for OpenNIC TLDs.
> 
> Load on T1-prime server.
> 
> If we have bad data for an ICANN tld it is most likely caused by the file 
> Robin's automated process pulls from the FTP server being out of date.  Second 
> most likely cause would be something having broken with that cron job causing 
> it not to update.  My money is on the root zone/hints file not being updated 
> by ICANN, just to stop the kind of thing that OpenNIC does.

If this is actually the problem, the solution is to write a
program/script that queries the ICANN root servers for the
NS entries of all the TLDs. Use this build an accurate and
up to date root zone file.

--

-- 
Ed Sawicki <ed <at> alcpress.com>
ALC

######################################################################
This is the discussion list for the Open Network Information
Center.  You can unsubscribe by sending an email containing the words
(Continue reading)

Marcus Dennis | 27 Jun 00:33 2003
Picon

Re: Root

On Thu, 26 Jun 2003, Rhonda Hyslop wrote:

> * gARetH baBB <hick <at> gink.geek> [26 Jun 2003 04:00]:
> > I've just come across the NS records for .tk are out of date, and it's
> > made me wonder what other out-of-date inaccurate records are in there.
> 
> I thought all requests for ICANN names were just sent on to ICANN
> servers?  Am I mistaken then, and do we actually serve ICANN data?
> 
Ack... can someone forward me the rest of the messages sent since this
one? /home2 got full again and I lost recent messages.

--
http://www.gnu.org/philosophy/
Support the freedom to share with your neighbor and your community.

######################################################################
This is the discussion list for the Open Network Information
Center.  You can unsubscribe by sending an email containing the words
"unsubscribe discuss" in the body of the message to
"majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net".
######################################################################

Bruno Wolff III | 28 Jun 20:55 2003
Picon

Re: Root

On Thu, Jun 26, 2003 at 15:11:07 -0700,
  Ed Sawicki <ed <at> alcpress.com> wrote:
> If this is actually the problem, the solution is to write a
> program/script that queries the ICANN root servers for the
> NS entries of all the TLDs. Use this build an accurate and
> up to date root zone file.

A discussion related to this came up on the djbdns list recently and
there was the following quote which I have not verified:
"B, C, and F allow unrestricted AXFR of . F's operators have said that
they have no plans to ever turn that off."

Also mentioned in this thread was that OSRC's root differed from ICANN's
in part was because ICANN was refusing to make some changes desired by
ccld's until they signed contracts saying they would do what ICANN says
or else and OSRC was already incorporating the changes desired by the
cclds.
######################################################################
This is the discussion list for the Open Network Information
Center.  You can unsubscribe by sending an email containing the words
"unsubscribe discuss" in the body of the message to
"majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net".
######################################################################

Ed Sawicki | 28 Jun 21:20 2003

Re: Root

On Sat, 2003-06-28 at 11:55, Bruno Wolff III wrote:
> On Thu, Jun 26, 2003 at 15:11:07 -0700,
>   Ed Sawicki <ed <at> alcpress.com> wrote:
> > If this is actually the problem, the solution is to write a
> > program/script that queries the ICANN root servers for the
> > NS entries of all the TLDs. Use this build an accurate and
> > up to date root zone file.
> 
> A discussion related to this came up on the djbdns list recently and
> there was the following quote which I have not verified:
> "B, C, and F allow unrestricted AXFR of . F's operators have said that
> they have no plans to ever turn that off."

I saw that and I tried to axfr the root zone from f.root-servers.net
but it didn't do it. I think I tried b and c as well. No joy.

> Also mentioned in this thread was that OSRC's root differed from ICANN's
> in part was because ICANN was refusing to make some changes desired by
> ccld's until they signed contracts saying they would do what ICANN says
> or else and OSRC was already incorporating the changes desired by the
> cclds.

All the more reason to ignore the ICANN roots and do what I
suggested in my original message.

--

-- 
Ed Sawicki <ed <at> alcpress.com>
ALC

######################################################################
(Continue reading)

Quentin Smith | 28 Jun 21:43 2003

Re: Root

On 28 Jun 2003, Ed Sawicki wrote:

> Date: 28 Jun 2003 12:20:11 -0700
> From: Ed Sawicki <ed <at> alcpress.com>
> Reply-To: discuss <at> opennic.unrated.net
> To: discuss <at> opennic.unrated.net
> Subject: Re: OpenNIC Discuss: Root
> 
> On Sat, 2003-06-28 at 11:55, Bruno Wolff III wrote:
> > On Thu, Jun 26, 2003 at 15:11:07 -0700,
> >   Ed Sawicki <ed <at> alcpress.com> wrote:
> > > If this is actually the problem, the solution is to write a
> > > program/script that queries the ICANN root servers for the
> > > NS entries of all the TLDs. Use this build an accurate and
> > > up to date root zone file.
> > 
> > A discussion related to this came up on the djbdns list recently and
> > there was the following quote which I have not verified:
> > "B, C, and F allow unrestricted AXFR of . F's operators have said that
> > they have no plans to ever turn that off."
> 
> I saw that and I tried to axfr the root zone from f.root-servers.net
> but it didn't do it. I think I tried b and c as well. No joy.
Hi-
That worked fine for me.
$dig  <at> f.root-servers.net . axfr
I put the results on my website, 
http://linux.comclub.org/~quentins/tld-servers.txt .
Perhaps you didn't configure your dns client properly?

(Continue reading)


Gmane