On 2018-01-08 5:25 PM, Richard Holbo wrote:
Other than being overly cautious.. I suppose there's no reason not to..
These don't and I didn't really expect them to, but it does represent
what I'm trying to do.
10.in.addr.arpa=216.115.0.5, 216.115.0.10
So this should be "in-addr"
Other than being overly cautious.. I suppose there's no reason not to..
These don't and I didn't really expect them to, but it does represent
what I'm trying to do.
10.in.addr.arpa=216.115.0.5, 216.115.0.10
168.192.in-addr.arpa=216.115.0.5, 216.115.0.10
16-31.172.in-addr.arpa=216.115.0.5, 216.11
On 2018-01-08 2:01 PM, Richard Holbo wrote:
Am fairly new to PDNS, have 4 auth and 4 recursive servers setup.
rfc1918 zones in the authoritative servers work as expected. RFC1918
in the recursors works appropriately if I have a forward statement of:
1.2.10.in-addr.arpa=1.2.3.4, 2.2.3.4
However
Am fairly new to PDNS, have 4 auth and 4 recursive servers setup.
rfc1918 zones in the authoritative servers work as expected. RFC1918
in the recursors works appropriately if I have a forward statement of:
1.2.10.in-addr.arpa=1.2.3.4, 2.2.3.4
However can I wildcard the reverse zone somehow? I j
