Bind9 "split zones"

Taavi Ansper taavi.ansper at cyber.ee
Mon Mar 4 15:35:35 UTC 2024


Hi

I am trying to understand bind9 more thorughly.

Backstory: We have been using bind9 for a long time and overhauling it 
for more "usage".

We have been using a "hidden master dns" logic with views for different 
usages.

E.g. Client -> Slave DNS Server <- (Transfer zones from hidden master)-> 
Hidden Master.

We had two views "external" and "internal" and now we added a new view 
"dmz" aswell.

In one of those zones we had an interesting DNS "thingy" where for 
example a CIDR 192.168.100.0/24 was generating entries to the main 
"hidden dns" server via includes. It uses a domain called example.com. 
Now another DNS server created DNS entries for the same CIDR 
192.168.100.0/24 but it had a different domain "subdomain.example.com". 
Including that info was easy.

In the Slave DNS

zone "example.com" {
     file blaah
     type slave
     masters { main_hidden_dns_server }
}

zone "subdomain.example.com" {
     file blaah
     type slave;
     masters { other_dns_server }
}

But now comes the problem. When generating a PTR record 
100.168.192.in-addr.arpa, I wish to combine both of these "results" into 
one lookup. How can I do that? I tried to add:

zone "100.168.192.in-addr.arpa" {
     file blaah
     type slave;
     masters { other_dns_server }
     forward first;
     forwarders {  main_hidden_dns_server }
}

But this forwarding logic doesnt work. I have a feeling the forwarding 
only works specific zones.  and you can't combine two of the same 
"names" into one. Am I correct and in order for PTR records to work I 
need to get them into a single file?

-- 
----
Taavi Ansper
taavi.ansper at cyber.ee



More information about the bind-users mailing list