Need of 2 $ORIGIN Directives

[Harshith Mulky]

Hello,


We have bind running bind-9.9.4-29.el7.x86_64


We have a domain file with these configurations and we have to build our A 
records on top of this


$ORIGIN .
$TTL 86400  ; 1 day
atlanta.comIN SOA  local.atlanta.com. master.atlanta.com. (
2001062522 ; serial
21600  ; refresh (6 hours)
3600   ; retry (1 hour)
604800 ; expire (1 week)
86400  ; minimum (1 day)
)
NS  local.atlanta.com.
NS  kabulvm8.atlanta.com.
$ORIGIN atlanta.com.
$TTL 300; 5 minutes
local   A   127.0.0.1
kabulvm8A   10.54.49.43



So I wanted to understand some things about this Domain


A. Why are there 2 $ORIGIN directives?

B. Can the above be replaced as below


$ORIGIN atlanta.com.
$TTL 86400  ; 1 day
@ IN SOA  local.atlanta.com. master.atlanta.com. (
2001062522 ; serial
21600  ; refresh (6 hours)
3600   ; retry (1 hour)
604800 ; expire (1 week)
86400  ; minimum (1 day)
)
NS  local.atlanta.com.
NS  kabulvm8.atlanta.com.
;A Records
local   A   127.0.0.1
kabulvm8A   10.54.49.43






Thanks

Harshith
___
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: Need of 2 $ORIGIN Directives

[Ray Bellis]

On 21/12/2016 12:57, Harshith Mulky wrote:

> So I wanted to understand some things about this Domain
> 
> A. Why are there 2 $ORIGIN directives?

Because someone thought they were being clever? :)
> 
> B. Can the above be replaced as below

Yes, and you could even remove the trailing `atlanta.com.` on some of
those records.

> $ORIGIN atlanta.com.
> $TTL 86400  ; 1 day
> @ IN SOA  local.atlanta.com. master.atlanta.com. (
> 2001062522 ; serial
> 21600  ; refresh (6 hours)
> 3600   ; retry (1 hour)
> 604800 ; expire (1 week)
> 86400  ; minimum (1 day)
> )
> NS  local.atlanta.com.
> NS  kabulvm8.atlanta.com.
> ;A Records
> local   A   127.0.0.1
> kabulvm8A   10.54.49.43

Ray


___
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: Need of 2 $ORIGIN Directives

[Petr Mensik]

A) $ORIGIN changes appended suffix to all hostnames without trailing . for all 
following records. You can change it more than one time.
Unless I am mistaken, NS records of first section would expand to
. NS local.atlanta.com.
. NS kabulvm8.atlanta.com.

That seems wrong to me.

B) Yes, it is almost equal. NS records are correct this time. I would prefer 
this variant myself.

However if those zones are output of some tool or script, you should try to 
support multiple usage of $ORIGIN directive in any tools you use.

--
Petr Menšík
Software Engineer
Red Hat, http://www.redhat.com/
email: pemen...@redhat.com  PGP: 65C6C973

- Original Message -
From: "Harshith Mulky" 
To: bind-users@lists.isc.org
Sent: Wednesday, December 21, 2016 1:57:35 PM
Subject: Need of 2 $ORIGIN Directives



Hello, 




We have bind running bind-9.9.4-29.el7.x86_64 




We have a domain file with these configurations and we have to build our A 
records on top of this 






$ORIGIN . 
$TTL 86400 ; 1 day 
atlanta.com IN SOA local.atlanta.com. master.atlanta.com. ( 
2001062522 ; serial 
21600 ; refresh (6 hours) 
3600 ; retry (1 hour) 
604800 ; expire (1 week) 
86400 ; minimum (1 day) 
) 
NS local.atlanta.com. 
NS kabulvm8.atlanta.com. 
$ORIGIN atlanta.com. 
$TTL 300 ; 5 minutes 
local A 127.0.0.1 
kabulvm8 A 10.54.49.43 



So I wanted to understand some things about this Domain 




A. Why are there 2 $ORIGIN directives? 


B. Can the above be replaced as below 





$ORIGIN atlanta.com. 
$TTL 86400 ; 1 day 
@ IN SOA local.atlanta.com. master.atlanta.com. ( 
2001062522 ; serial 
21600 ; refresh (6 hours) 
3600 ; retry (1 hour) 
604800 ; expire (1 week) 
86400 ; minimum (1 day) 
) 
NS local.atlanta.com. 
NS kabulvm8.atlanta.com. 
;A Records 
local A 127.0.0.1 
kabulvm8 A 10.54.49.43 








Thanks 

Harshith 

___
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
___
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: Need of 2 $ORIGIN Directives

[Nis Wechselberg]

Am 21.12.2016 um 14:12 schrieb Petr Mensik:
> A) $ORIGIN changes appended suffix to all hostnames without trailing . for 
> all following records. You can change it more than one time.
> Unless I am mistaken, NS records of first section would expand to
> . NS local.atlanta.com.
> . NS kabulvm8.atlanta.com.

I think you are mistaken. If the record name is empty it reuses the
previous entry, so the entries should both expand to 'atlanta.com.'

At least, I always used it that way ;)

Regards,
Nis



signature.asc
Description: OpenPGP digital 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: Need of 2 $ORIGIN Directives

[/dev/rob0]

On Wed, Dec 21, 2016 at 01:00:22PM +, Ray Bellis wrote:
> On 21/12/2016 12:57, Harshith Mulky wrote:
> 
> > So I wanted to understand some things about this Domain
> > 
> > A. Why are there 2 $ORIGIN directives?
> 
> Because someone thought they were being clever? :)

named itself does this in automatically-generated zone files, but 
that's no reason for a human editor of zone files to do the same.

> > B. Can the above be replaced as below
> 
> Yes, and you could even remove the trailing `atlanta.com.` on some 
> of those records.
> 
> > $ORIGIN atlanta.com.

Furthermore this too could be omitted, since:

zone "atlanta.com" IN { ...

a zone statement implicitly sets $ORIGIN to the name of the zone.

> > $TTL 86400  ; 1 day
> > @ IN SOA  local.atlanta.com. master.atlanta.com. (

These names could be relative rather than absolute:

@   IN  SOA local master (

> > 2001062522 ; serial
> > 21600  ; refresh (6 hours)
> > 3600   ; retry (1 hour)
> > 604800 ; expire (1 week)
> > 86400  ; minimum (1 day)
> > )
> > NS  local.atlanta.com.
> > NS  kabulvm8.atlanta.com.

and these, likewise.

NS  local
NS  kabulvm8

> > ;A Records
> > local   A   127.0.0.1
> > kabulvm8A   10.54.49.43
-- 
  http://rob0.nodns4.us/
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
___
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: BIND transferring zones with incorrect view

[Matthew Pounsett]

On 20 December 2016 at 16:45, Asai  wrote:

> Greetings,
>
> Quick question.  Using BIND 9.9.4.  I have 2 zones.  One for LAN traffic,
> and one for WAN traffic.  My secondary server is transferring the wrong
> zones, so that my WAN zone has all the A records for my LAN zone.
>
> Any insights on this?
>
> Most likely you've misconfigured your master server such that the slave
(secondary) sees the wrong zone when doing zone transfers.  But, because
you haven't provided any real detail about your configuration, no one is
going to be able to provide much in the way of advice about how to fix it.

You should read the article that Mark Andrews linked, and if you still are
not able to solve the problem you should return with some details about
your setup.
___
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: BIND transferring zones with incorrect view

[Asai]

Yes, thank you.  I think Mark’s link to the article is the proper solution.  
Thank you for your reply.


> On Dec 21, 2016, at 10:55 AM, Matthew Pounsett  wrote:
> 
> 
> 
> On 20 December 2016 at 16:45, Asai  > wrote:
> Greetings,
> 
> Quick question.  Using BIND 9.9.4.  I have 2 zones.  One for LAN traffic, and 
> one for WAN traffic.  My secondary server is transferring the wrong zones, so 
> that my WAN zone has all the A records for my LAN zone.
> 
> Any insights on this?
> 
> Most likely you've misconfigured your master server such that the slave 
> (secondary) sees the wrong zone when doing zone transfers.  But, because you 
> haven't provided any real detail about your configuration, no one is going to 
> be able to provide much in the way of advice about how to fix it.
> 
> You should read the article that Mark Andrews linked, and if you still are 
> not able to solve the problem you should return with some details about your 
> setup. 
> 

___
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