Zone Template

[Sten Carlsen]

Ok, ok.

My fault, I was not aware this could be done so I had to do a test. I
did not look closely enough. Implementing the last correction made
everything work correctly.

I learnt something today; thank you.


Bill Larson wrote:
> On Oct 7, 2006, at 12:10 PM, Sten Carlsen wrote:
>
>   
>> Doesn't work on 9.21, I just get "hostmaster."  in an soa query  
>> from dig.
>>
>> I know 9.21 is ancient (the whole system is waiting to be replaced)  
>> but
>> has this changed since then? If so, about when.
>>     
>
> This functioned back in BIND-8.  Actually, it worked in BIND-4 but  
> those were the good old days.
>
> If you are using the same zone file that you showed previously, what  
> was your origin with the SOA record?  If your origin were simply ".",  
> then you get exactly what you said.  You would end up with just  
> "hostmaster.".  Any unqualified name, any name that does not end with  
> a period, is fully qualified by adding the value of the origin to them.
>
> If you use relative names, the names are relative to the origin.  If  
> your origin is ".", you basically have defeated the ability to use  
> relative names.  If your origin were "domain_hosted.com", then any  
> name would be fully qualified with "domain_hosted.com".
>
> For example, if your origin were "domain_hosted.com" and your SOA  
> record simply specified "hostmaster" as the RNAME (email address),  
> then this RNAME would be fully qualified as  
> "hostmaster.domain_hosted.com".
>
> Now, my rant, why do people think that they must specify the origin  
> at the beginning of their zone files?  There is no need for this as  
> Barry demonstrated.
>
> Bill Larson
>
>   
>> 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!!!"
>>
>>
>>     
>
>
>   


-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"