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

Walter Smith whatisee1 at
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:

irish A
brit  A

$ORIGIN bar2
irish2 A

brit2  A

irish3 A

brit3  A

$ORIGIN bar2

irish22 A

brit22  A


irish39 A

brit39  A

$ORIGIN bar2

irish29 A

brit29  A

...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,

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

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

In article <mailman.43.1297269285.10842.bind-users at>,
 Walter Smith <whatisee1 at> 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: IN A

it will write:


foo IN A

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
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bind-users mailing list