Re: How is a $ORIGIN directive used inside a DNS Zone File

[Mukund Sivaraman]

On Mon, Dec 14, 2015 at 11:18:08AM +, Tony Finch wrote:
> Mukund Sivaraman  wrote:
> >
> > Zone files do not require use of $ORIGIN. It is in fact an extension to
> > the master format in RFC 1035.
> 
> No, it is specified in RFC 1035 section 5.1:

I'm getting old.

Mukund


signature.asc
Description: PGP signature
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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

Re: How is a $ORIGIN directive used inside a DNS Zone File

[Tony Finch]

Mukund Sivaraman  wrote:
>
> Zone files do not require use of $ORIGIN. It is in fact an extension to
> the master format in RFC 1035.

No, it is specified in RFC 1035 section 5.1:

: Two control entries are defined: $ORIGIN and $INCLUDE.  $ORIGIN is
: followed by a domain name, and resets the current origin for relative
: domain names to the stated name.

:  Domain names that end in a dot are called
: absolute, and are taken as complete.  Domain names which do not end in a
: dot are called relative; the actual domain name is the concatenation of
: the relative part with an origin specified in a $ORIGIN, $INCLUDE, or as
: an argument to the master file loading routine.  A relative name is an
: error when no origin is available.

: @   A free standing @ is used to denote the current origin.

For BIND when you specify a zone you have to provide a zone file name and
zone apex name, and the origin defaults to the zone apex.

Tony.
-- 
f.anthony.n.finch    http://dotat.at/
Cromarty, Forth: Cyclonic becoming easterly 4 or 5, occasionally 6 later.
Slight or moderate. Occasional rain. Good, occasionally poor.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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

Re: How is a $ORIGIN directive used inside a DNS Zone File

[Mukund Sivaraman]

Hi Harshith

On Mon, Dec 14, 2015 at 07:36:15AM +, Harshith Mulky wrote:
> Why is a $ORIGIN directive used in DNS Zone Files?

$ORIGIN directive sets a name to be appended to relative names in the
zone file so that they can be made into absolute names. The current
origin is appended to such relatives names.

See the BIND ARM for syntax and an explanation.

It is also explained here: http://www.zytrax.com/books/dns/ch8/origin.html

> Would my Zone Files not work if I do not have $ORIGIN directive?

Zone files do not require use of $ORIGIN. It is in fact an extension to
the master format in RFC 1035.

See the pointers above for more details.

Mukund


signature.asc
Description: PGP signature
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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

How is a $ORIGIN directive used inside a DNS Zone File

[Harshith Mulky]

Why is a $ORIGIN directive used in DNS Zone Files?
Would my Zone Files not work if I do not have $ORIGIN directive?

I would need some examples on how this works, lets say

$ORIGIN .
[ What does $ORIGIN . mean?]
or


What is the difference here having 1.e164.arpa. in $ORIGIN [ as in example 1] 
or having it in NAPTR Records section [as in Example 2]
1.$ORIGIN 1.e164.arpa.

or

2.   $ORIGIN 2.7.5.2.0.2.5.0.2.1.e164.arpa.
  0NAPTR10 10 "u" "sip+E2U" 
"!^.*$!sip:2052025720@112.24.45.44!" .
  1NAPTR10 10 "u" "sip+E2U" 
"!^.*$!sip:2052025721@112.24.44.44!" .
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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