Re: Keeping dynamic and static zone data separated

2018-01-03 Thread Tony Finch
Matthias Pigulla wrote: > Tony Finch wrote: > > > Best solution is to put the dynamic stuff in a subdomain so it can be > > in a separate zone. > > Unfortunately, I need to have a final result of dynamic-rr.myzone.tld and > static-rr.myzone.tld, that is, both need to go together. Is there any way

Re: Keeping dynamic and static zone data separated

2018-01-03 Thread Matthias Pigulla
Tony Finch wrote: > Best solution is to put the dynamic stuff in a subdomain so it can be in >a > separate zone. Unfortunately, I need to have a final result of dynamic-rr.myzone.tld and static-rr.myzone.tld, that is, both need to go together. Is there any way to import and/or alias a subdomain/

Re: Keeping dynamic and static zone data separated

2018-01-03 Thread Tony Finch
Matthias Pigulla wrote: > > So, how do you handle the situation of mixed static and dynamic RRs? Is > there another way to keep these separated and possibly under version > control? Best solution is to put the dynamic stuff in a subdomain so it can be in a separate zone. Alternatively, you might

Keeping dynamic and static zone data separated

2018-01-03 Thread Matthias Pigulla
Dear bind-users, I am running a zone with dynamic updates, but will also need to add "static" RRs. My first attempt was to use /etc/bind/db.myzone for the SOA and static RRs. Then, use something like /var/lib/bind/db.myzone as the zone file and $INCLUDE /etc/bind/db.myzone from there. I was hop