syntax/format of zone on slave $ORIGIN/paragraph - sorted?

Walter Smith whatisee1 at yahoo.com
Thu Feb 10 16:40:42 UTC 2011


Oh Thanks - I understand that - I can't comprehend the logic behind composing _same_ $ORIGIN paragraphs over-and-over again - this is an example:


$ORIGIN bar
irish A 1.2.3.4
brit  A 1.2.3.5

$ORIGIN bar2
irish2 A 1.2.3.42

brit2  A 1.2.3.52

$ORIGIN bar
irish3 A 1.2.3.43

brit3  A 1.2.3.53

$ORIGIN bar2

irish22 A 1.2.3.422


brit22  A 1.2.3.522

$ORIGIN bar

irish39 A 1.2.3.439


brit39  A 1.2.3.539

$ORIGIN bar2

irish29 A 1.2.3.429


brit29  A 1.2.3.529


...see - What i meant!

It keep splitting on some un-even way --- that "$ORIGIN bar" and "$ORIGIN bar2" keep switching back-and-forth...
Is there any way to have ONLY ONE paragraph per $ORIGIN?

Thanks folks,
-WS

--- On Wed, 2/9/11, Barry Margolin <barmar at alum.mit.edu> wrote:

From: Barry Margolin <barmar at alum.mit.edu>
Subject: Re: syntax/format of zone on slave $ORIGIN/paragraph - sorted?
To: comp-protocols-dns-bind at isc.org
Date: Wednesday, February 9, 2011, 7:27 PM

In article <mailman.43.1297269285.10842.bind-users at lists.isc.org>,
 Walter Smith <whatisee1 at yahoo.com> wrote:

> Hello,
> 
> I have bind/named running on Linux master and slaves. All is good, but now 
> when I’m trying to clean up some old records – I realized that sorted zone on 
> slaves are quite uneven. What I meant is, the $ORIGIN splits the zone into 
> some unknown to me syntax/format. Is there anywhere I can find the 
> description/documentation on it – How exactly slave parse the zone from 
> master and puts all these arbitrary paragraphs with $ORIGIN.

When writing the zone file on a slave, BIND uses $ORIGIN so that all 
records just have a single label.  So instead of writing:

foo.bar IN A 1.2.3.4

it will write:

$ORIGIN bar

foo IN A 1.2.3.4

If you have a zone with lots of levels of subdomain, the file will have 
lots of $ORIGIN statements as a result.

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***

-----Inline Attachment Follows-----

_______________________________________________
bind-users mailing list
bind-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20110210/ba374693/attachment.html>


More information about the bind-users mailing list