dynamically updated zone and $GENERATE

Sten Carlsen ccc2716 at vip.cybercity.dk
Wed Apr 5 23:50:46 UTC 2006


Ok, I use a combination of static and dynamic configuration and I forgot
the dump process because it always looks the same in my case when I do
static updates with a stopped nameserver.
If $generate should work under dynamic updates, it would have to be
processed (and changed) at all times when a new copy of the database is
written regardles of the cause.

I assume you are right, it does not work or at least there is no easy
consistent way it could work.

Kevin Darcy wrote:
> Sten Carlsen wrote:
>
>   
>> I think this depends upon how the $generate statements are interpreted.
>> I would believe that they are just a kind of shorthand for writing long
>> and systematic sequences.
>> So, in short:
>> If it works like the cpp C-preprocessor with C, it should be fine to use
>> it with dynamic updated zones for providing the basic content.
>>
>>     
> How do you come to that conclusion? Under Dynamic Update, the individual 
> updates are committed first to the journal, and only periodically 
> "dumped" out to the main zone file. In order to preserve $INCLUDEs and 
> $GENERATEs and whatnot in the midst of that dumping process, named would 
> have to set up special code paths, data structures, etc. and the effort 
> hardly seems worth it.
>
>                                                                          
>                                                       - Kevin
>
>   
>> If on the other hand the processing of $generate statements is closely
>> intertwined with the other operations, they should be impossible to use
>> with dynamic updates.
>>
>> So the question is: how does bind process $generate statements before
>> initially loading the zone or after loading it?
>>
>> I don't know, maybe somebody else does on this list.
>>
>> Kevin Darcy wrote:
>>  
>>
>>     
>>> andrey.lakhno at gmail.com wrote:
>>>
>>>  
>>>    
>>>
>>>       
>>>> Hello,
>>>>
>>>> Is it possible to use $GENERATE/$INCLUDE in dynamicaly updated zone
>>>> with latest BIND 9 ?
>>>>
>>>>    
>>>>      
>>>>
>>>>         
>>> I don't believe so. Once Dynamic Update is enabled for a zone, then 
>>> named "owns" the zone file and writes whatever it wants to it, whenever 
>>> it wants, which is probably going to wipe out your $GENERATEs and/or 
>>> $INCLUDEs.
>>>
>>> Use nsupdate or some other Dynamic Update client to maintain the zone's 
>>> "manual" data. If the data in your $GENERATEs and/or $INCLUDEs are 
>>> static, then you just issue the relevant nsupdate commands one time to 
>>> achieve the same result. If, on the other hand, your $GENERATE/$INCLUDE 
>>> data tend to change fairly often, then you'd be wise to insert some 
>>> scripted nsupdates into your change process.
>>>
>>>                                                                         
>>>                                                                  - Kevin
>>>
>>>
>>>
>>>  
>>>    
>>>
>>>       
>>  
>>
>>     
>
>
>
>   

-- 
Best regards

Sten Carlsen

Let HIM who has an empty INBOX send the first mail.





More information about the bind-users mailing list