NS File format.

[Barry Margolin]

In article <4.3.2.7.2.20000615131216.00b63598 at pop3.valuelinx.net>,
Stephen D. Malenshek <stephen at valuelinx.net> wrote:
>
>I have a very strange question regarding the new P5 version of Bind.  I 
>recently upgraded to it and on my slave NS servers, it goes through and 
>rewrites all the records with this $ORIGIN in it and changes the format 
>completely.  Is this the proper format for it to be in, or is there some 
>way to make it stop rewriting the slave records on my secondary servers to 
>this hard to deal with form.  I have looked around and there is not 
>actually a sample file format to look at to see actually what they are 
>supposed to look like....  I know this sounds stupid, but after seeing what 
>this new version does...  I am just questioning if I am doing it the 
>correct way.  I was tempted to post a small section to show the layout, but 
>I did not know if that would upset anyone...  I am new to this list, so 
>please forgive me.

named-xfer has been using that format for years.  It uses $ORIGIN
directives so that all records have a single-component name in the left
column.  E.g. instead of

foo.com.  IN SOA ...
bar.foo.com.  IN A ...

it does:

$ORIGIN com.
foo       IN SOA ...
$ORIGIN foo.com.
bar       IN A ...

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.