The @ Notation - Clarity

[Walker Simon-SWALKER1]

Thanks Len for the response! ... you are right I am confused.

So in effect I could have the following in my named.conf pointing to my zone file :

zone "xyz.net" in {
	type master;
	file "db.xyz.net";

And the following in my zone data file (xyz.net) :

$TTL 3h
@ IN SOA host-123.xyz.net. admin.yxz.net. (
	1 ; serial
	3h ; refresh after 3 hours
	1h ; retry after 1 hour
	1w ; Expire after 1 week
	1h) ; Negative caching TTL of 1 day

;
; Name Servers
;
			IN NS host-123.xyz.net.
;
; Addresses For Canonical Names
;
localhost	IN A 127.0.0.1
host-123 	IN A 192.168.10.1
host-456 	IN A 192.168.10.2


And the hosts would still be build correctly to be, for example host-123.xyz.net. as the @ notation completes the current origin, that being xyz.net.

Phew....

Regards, 

Si.


> -----Original Message-----
> From: Len Conrad [mailto:LConrad at Go2France.com]
> Sent: Thursday, December 05, 2002 9:51 AM
> To: bind-users at isc.org
> Subject: Re: The @ Notation - Clarity
> 
> 
> 
> 
> >It mentions shortcuts and one of them in the "@" notation.
> >
> >As I have read the @ is replaced in the zone file by the
> 
> ... "current" ...
> 
> >origin, which comes
> >from the zone statement in named.conf?
> 
> ... which provide the "default" origin to the "top" of the zone file
> 
> >  The main question is do I need to
> >have a trailing period (.) in the zone statement so that @ 
> is complete when
> >it is replaced in the zone file.
> 
> no.
> 
> >So should named.conf be like so?
> >
> >zone "xyz.com."{
> >type master;
> >file "bxyz.com.";
> >};
> >
> >With the trailing period (.) or can I leave it off
> 
> yes
> 
> >as BIND would know this is complete.
> 
> You are confusing zone file syntax with the completely 
> different named.conf 
> syntax.
> 
> Len
> 
> 
>