<div dir="ltr"><div><div>Well... DOHH.. Looks like if I don't typo it... it is a feature that works the way you'd expect.</div><div>/thanks</div><div><br></div><div>10.in-addr.arpa=216.115.0.5, 216.115.0.10<br>168.192.in-addr.arpa=216.115.0.5, 216.115.0.10<br>16-31.172.in-addr.arpa=216.115.0.5, 216.115.0.10<br></div><br></div>and a lookup.<br><br>DT:~$ dig -x 10.40.19.30 @<a href="http://216.115.0.8">216.115.0.8</a><br><br>; <<>> DiG 9.10.3-P4-Ubuntu <<>> -x 10.40.19.30 @<a href="http://216.115.0.8">216.115.0.8</a><br>;; global options: +cmd<br>;; Got answer:<br>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18771<br>;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1<br><br>;; OPT PSEUDOSECTION:<br>; EDNS: version: 0, flags:; udp: 4096<br>;; QUESTION SECTION:<br>;30.19.40.10.in-addr.arpa. IN PTR<br><br>;; ANSWER SECTION:<br>30.19.40.10.in-addr.arpa. 86127 IN PTR <a href="http://test-lookup.cpe.coreds.net">test-lookup.cpe.coreds.net</a>.<br><br>;; Query time: 1 msec<br>;; SERVER: 216.115.0.8#53(216.115.0.8)<br>;; WHEN: Tue Jan 09 08:43:03 PST 2018<br>;; MSG SIZE rcvd: 103<br><br><br><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 8, 2018 at 7:31 PM, David <span dir="ltr"><<a href="mailto:opendak@shaw.ca" target="_blank">opendak@shaw.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2018-01-08 5:25 PM, Richard Holbo wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Other than being overly cautious.. I suppose there's no reason not to..<br>
<br>
<br>
These don't and I didn't really expect them to, but it does represent<br>
what I'm trying to do.<br>
<br>
10.in.addr.arpa=216.115.0.5, 216.115.0.10<br>
</blockquote>
<br></span>
^^^^<br>
So this should be "in-addr"<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
168.192.in-addr.arpa=216.115.0<wbr>.5, 216.115.0.10<br>
16-31.172.in-addr.arpa=216.115<wbr>.0.5, 216.115.0.10<br>
</blockquote>
<br>
I'm afraid you'll have to separate these out, unless this is a feature that works that I don't know about.<div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
This works as I'd expect, just don't want to have to keep adding /24s<br>
as it'll be a LONG list and change pretty regularly...<br>
19.40.10.in-addr.arpa=216.115.<wbr>0.5, 216.115.0.10<br>
<br>
<br>
On Mon, Jan 8, 2018 at 1:43 PM, David <<a href="mailto:opendak@shaw.ca" target="_blank">opendak@shaw.ca</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2018-01-08 2:01 PM, Richard Holbo wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Am fairly new to PDNS, have 4 auth and 4 recursive servers setup.<br>
rfc1918 zones in the authoritative servers work as expected. RFC1918<br>
in the recursors works appropriately if I have a forward statement of:<br>
<br>
1.2.10.in-addr.arpa=1.2.3.4, 2.2.3.4<br>
<br>
However can I wildcard the reverse zone somehow? I just want it to<br>
goto my servers for ALL rfc1918 space.<br>
<br>
Tried<br>
10.in.addr.arpa=1.2.3.4, 2.2.3.4<br>
168.192.in-addr.arpa=1.2.3.4, 2.2.3.4<br>
16-31.172.in-addr.arpa=1.2.3.4<wbr>, 2.2.3.4<br>
</blockquote>
<br>
<br>
Is this really what you used? Can you show what you actually tried without<br>
editing? The first entry would clearly be wrong. The last one doesn't<br>
support doing that format to specify a "range".<br>
<br>
<a href="https://blog.powerdns.com/2016/01/18/open-source-support-out-in-the-open/" rel="noreferrer" target="_blank">https://blog.powerdns.com/2016<wbr>/01/18/open-source-support-<wbr>out-in-the-open/</a><br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
As that's the way the documentation mentions them in the serve-rfc1918<br>
option.<br>
<br>
Don't really want to have to update the forward file each time ops<br>
adds a rfc-1918 /24 network.<br>
<br>
/thanks<br>
/rh<br>
______________________________<wbr>_________________<br>
Pdns-users mailing list<br>
<a href="mailto:Pdns-users@mailman.powerdns.com" target="_blank">Pdns-users@mailman.powerdns.co<wbr>m</a><br>
<a href="https://mailman.powerdns.com/mailman/listinfo/pdns-users" rel="noreferrer" target="_blank">https://mailman.powerdns.com/m<wbr>ailman/listinfo/pdns-users</a><br>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
Pdns-users mailing list<br>
<a href="mailto:Pdns-users@mailman.powerdns.com" target="_blank">Pdns-users@mailman.powerdns.co<wbr>m</a><br>
<a href="https://mailman.powerdns.com/mailman/listinfo/pdns-users" rel="noreferrer" target="_blank">https://mailman.powerdns.com/m<wbr>ailman/listinfo/pdns-users</a><br>
</blockquote>
<br>
<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Richard Holbo<br>Hunter Communications<br>Network Operations 541.414.1365</div>
</div>