Zone Template

Sten Carlsen ccc2716 at vip.cybercity.dk
Sun Oct 8 01:01:34 UTC 2006


My problem was that I had overlooked an "$origin ." statement, I was
getting what I asked for. I was just asking for something else than what
I thought.

Again thanks to everyone, I learnt something today.

Barry Margolin wrote:
> In article <eg8qth$2823$1 at sf1.isc.org>,
>  Sten Carlsen <ccc2716 at vip.cybercity.dk> wrote:
>
>   
>> Doesn't work on 9.21, I just get "hostmaster."  in an soa query from dig.
>>     
>
> Then you must have typed "hostmaster." rather than "hostmaster".  Any 
> name without a trailing dot will have the origin appended, and this 
> includes the fields in the SOA record.
>
>   
>> I know 9.21 is ancient (the whole system is waiting to be replaced) but
>> has this changed since then? If so, about when.
>>
>> Barry Margolin wrote:
>>     
>>> In article <eg8mqf$1rcu$1 at sf1.isc.org>,
>>>  Sten Carlsen <ccc2716 at vip.cybercity.dk> wrote:
>>>
>>>   
>>>       
>>>> You would still have to change the mail address in the SOA. That is much
>>>> easier of course; I assume that @ can not be used there?
>>>>     
>>>>         
>>> But a relative name can.  If it's always root@<domain> or 
>>> hostmaster@<domain>, you can just put "root" or "hostmaster" there.
>>>
>>>   
>>>       
>>>> Barry Margolin wrote:
>>>>     
>>>>         
>>>>> In article <eg763f$2mfn$1 at sf1.isc.org>,
>>>>>  "Josh Hyles" <josh.maillists at gmail.com> wrote:
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>>>> I am running a windows BIND server and am trying to figure out what
>>>>>> the best template would be for creating new sites. I currently use the
>>>>>> following...
>>>>>>
>>>>>> $ORIGIN .
>>>>>> $TTL 86400	; 1 day
>>>>>> domain_hosted.com		IN SOA	NS1.domain.com. root.domain_hosted.com. (
>>>>>> 				2006053001 ; serial
>>>>>> 				3600       ; refresh (1 hour)
>>>>>> 				7200       ; retry (2 hours)
>>>>>> 				604800     ; expire (1 week)
>>>>>> 				43200      ; minimum (12 hours)
>>>>>> 				)
>>>>>> 			NS	NS1.domain.com.
>>>>>> 			NS	NS2.domain.com.
>>>>>> 			A	63.247.73.122
>>>>>> 			MX	5 mail.domain_hosted.com.
>>>>>> $ORIGIN domain_hosted.com.
>>>>>> ftp			A	123.456.789.012
>>>>>> mail			A	123.456.789.012
>>>>>> www			A	123.456.789.012
>>>>>>
>>>>>> All of the "domain_hosted" entries must be changed to the new domain
>>>>>> that I am hosting... is there any better to do this?
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> I'd leave out all the $ORIGIN statements, and use relative names (or @) 
>>>>> for the zone name.  Then you don't have to change anything for the new 
>>>>> domain -- the origin defaults to the name from the 'zone' statement in 
>>>>> named.conf.
>>>>>
>>>>> $TTL 86400      ; 1 day
>>>>> @               IN SOA  NS1.domain.com. root.domain_hosted.com. (
>>>>>                                 2006053001 ; serial
>>>>>                                 3600       ; refresh (1 hour)
>>>>>                                 7200       ; retry (2 hours)
>>>>>                                 604800     ; expire (1 week)
>>>>>                                 43200      ; minimum (12 hours)
>>>>>                                 )
>>>>>                         NS      NS1.domain.com.
>>>>>                         NS      NS2.domain.com.
>>>>>                         A       63.247.73.122
>>>>>                         MX      5 mail
>>>>> ftp                     A       123.456.789.012
>>>>> mail                    A       123.456.789.012
>>>>> www                     A       123.456.789.012
>>>>>
>>>>>
>>>>>       
>>>>>           
>>>       
>
>   

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!" 



More information about the bind-users mailing list