[Pdns-users] Quick question re: recursing rfc-1918 in.addr.arpa
opendak at shaw.ca
Tue Jan 9 03:31:18 UTC 2018
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=220.127.116.11, 18.104.22.168
So this should be "in-addr"
> 168.192.in-addr.arpa=22.214.171.124, 126.96.36.199
> 16-31.172.in-addr.arpa=188.8.131.52, 184.108.40.206
I'm afraid you'll have to separate these out, unless this is a feature
that works that I don't know about.
> This works as I'd expect, just don't want to have to keep adding /24s
> as it'll be a LONG list and change pretty regularly...
> 19.40.10.in-addr.arpa=220.127.116.11, 18.104.22.168
> On Mon, Jan 8, 2018 at 1:43 PM, David <opendak at shaw.ca> wrote:
>> 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=22.214.171.124, 126.96.36.199
>>> However can I wildcard the reverse zone somehow? I just want it to
>>> goto my servers for ALL rfc1918 space.
>>> 10.in.addr.arpa=188.8.131.52, 184.108.40.206
>>> 168.192.in-addr.arpa=220.127.116.11, 18.104.22.168
>>> 16-31.172.in-addr.arpa=22.214.171.124, 126.96.36.199
>> Is this really what you used? Can you show what you actually tried without
>> editing? The first entry would clearly be wrong. The last one doesn't
>> support doing that format to specify a "range".
>>> As that's the way the documentation mentions them in the serve-rfc1918
>>> Don't really want to have to update the forward file each time ops
>>> adds a rfc-1918 /24 network.
>>> Pdns-users mailing list
>>> Pdns-users at mailman.powerdns.com
>> Pdns-users mailing list
>> Pdns-users at mailman.powerdns.com
More information about the Pdns-users