Well... DOHH.. Looks like if I don't typo it... it is a feature that works the way you'd expect. /thanks
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.115.0.10 and a lookup. DT:~$ dig -x 10.40.19.30 @216.115.0.8 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> -x 10.40.19.30 @216.115.0.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18771 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;30.19.40.10.in-addr.arpa. IN PTR ;; ANSWER SECTION: 30.19.40.10.in-addr.arpa. 86127 IN PTR test-lookup.cpe.coreds.net. ;; Query time: 1 msec ;; SERVER: 216.115.0.8#53(216.115.0.8) ;; WHEN: Tue Jan 09 08:43:03 PST 2018 ;; MSG SIZE rcvd: 103 On Mon, Jan 8, 2018 at 7:31 PM, David <[email protected]> wrote: > 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" > > 168.192.in-addr.arpa=216.115.0.5, 216.115.0.10 >> 16-31.172.in-addr.arpa=216.115.0.5, 216.115.0.10 >> > > 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=216.115.0.5, 216.115.0.10 >> >> >> On Mon, Jan 8, 2018 at 1:43 PM, David <[email protected]> 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=1.2.3.4, 2.2.3.4 >>>> >>>> However can I wildcard the reverse zone somehow? I just want it to >>>> goto my servers for ALL rfc1918 space. >>>> >>>> Tried >>>> 10.in.addr.arpa=1.2.3.4, 2.2.3.4 >>>> 168.192.in-addr.arpa=1.2.3.4, 2.2.3.4 >>>> 16-31.172.in-addr.arpa=1.2.3.4, 2.2.3.4 >>>> >>> >>> >>> 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". >>> >>> https://blog.powerdns.com/2016/01/18/open-source-support- >>> out-in-the-open/ >>> >>> >>> >>> >>>> As that's the way the documentation mentions them in the serve-rfc1918 >>>> option. >>>> >>>> Don't really want to have to update the forward file each time ops >>>> adds a rfc-1918 /24 network. >>>> >>>> /thanks >>>> /rh >>>> _______________________________________________ >>>> Pdns-users mailing list >>>> [email protected] >>>> https://mailman.powerdns.com/mailman/listinfo/pdns-users >>>> >>>> >>> _______________________________________________ >>> Pdns-users mailing list >>> [email protected] >>> https://mailman.powerdns.com/mailman/listinfo/pdns-users >>> >> >> >> >> > -- Richard Holbo Hunter Communications Network Operations 541.414.1365
_______________________________________________ Pdns-users mailing list [email protected] https://mailman.powerdns.com/mailman/listinfo/pdns-users
