Discuss mailing list

[Jeff Taylor <shdwdrgn AT sourpuss.net>]

BIND may rearrange the order of a zone when it is transferred, but you still 
need to break down the hostnames to create proper origin groups.  I finally 
settled on breaking down the names, throwing out the first part (usually 
something like NS1), and sorting out what was left.  There may be excessive 
switching between origins for some zone, but for the most part it looks like it 
is working correctly, and everything I've verified myself is listed in a proper 
method that BIND will understand.

Here's an icann-available path to reach the same file:  
http://sourpuss.net/opennic.oss/files/root-hints

Hope that helps.


On 01/23/2011 01:50 PM, Amrit Panesar wrote:
> On 1/23/2011 11:34 AM, Jeff Taylor wrote:
> > Some folks have pointed out that the root-hints file is out of date.
> > Today I have been working on a script to generate a brand new hints
> > file, pulling all data directly from ICANN's root servers.  The
> > hardest part of this project has been sorting out the A records to be
> > grouped under their proper $ORIGIN headings.
> I believe BIND does this on its own, when `slaving` normal zones, i'm
> not sure if it can do the same for a hits zone, I believe you are
> looking for the same idea, correct?
> > I have a sample file available here:  http://opennic.oss/files/root-hints
> Hmm..  I am unable to resolve the domain, though opennic.glue is
> resolving, but only wiki.opennic.glue, for whatever reason.. I think I'm
> having some issues with my DNS settings..
>
> I like the idea, I wish you luck with it.. I just thought it was worth
> noting that BIND does group things via $ORIGIN, perhaps you can
> incorporate something from BIND in what you are doing right now...
>
> Thanks
>
> --Amrit
> _______________________________________________
> discuss mailing list
> discuss AT lists.opennicproject.org
> http://lists.darkdna.net/mailman/listinfo/discuss