I have a number of slave domains that I would like a naming scheme and
not have to go to each and change the filename.
I have the following zones
zone "1.168.192.in-addr.arpa" {
include "named.slave";
};
zone "2.168.192.in-addr.arpa" {
include "named.slave";
};
zone "3.168.192.in-addr.arpa" {
include "named.slave";
};
zone "4.168.192.in-addr.arpa" {
include "named.slave";
};
zone "5.168.192.in-addr.arpa" {
include "named.slave";
};
zone "6.168.192.in-addr.arpa" {
include "named.slave";
};
zone "7.168.192.in-addr.arpa" {
include "named.slave";
};
zone "8.168.192.in-addr.arpa" {
include "named.slave";
};
zone "9.168.192.in-addr.arpa" {
include "named.slave";
};
zone "10.168.192.in-addr.arpa" {
include "named.slave";
};
named.slave looks as follows
type slave;
masters {192.168.1.2;};
file "data/db.@.slave";
It appears to work on my queries.
nslookup 192.168.1.2
2.1.168.192.in-addr.arpa name = pdc.<domain>
nslookup 192.168.1.1
1.1.168.192.in-addr.arpa name = gw1.<domain>
nslookup 192.168.2.1
1.2.168.192.in-addr.arpa name = gw2.<domain>
the only file created in my data directory seems to be db.@.slave
with the at sign.
Do I really need to have each zone with its own file?
Is there a special syntax to get what I expect?
expected files:
data/db.1.168.192.in-addr.arpa.slave
data/db.2.168.192.in-addr.arpa.slave
data/db.3.168.192.in-addr.arpa.slave
...
data/db.10.168.192.in-addr.arpa.slave
if not I can have Make do it and build some scripts to do what I want
but if there is syntax to do what I want it would be nice.
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
