<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 25/01/2019 08:33, Martin Kellermann
via Pdns-users wrote:<br>
</div>
<blockquote type="cite"
cite="mid:30AE9853470C2147891CED063F5EFC56016D24DE3B68@SKSERVER21.sk.local">
<pre class="moz-quote-pre" wrap="">hi Andy,
</pre>
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">By way of example, I (in the ISP role) delegate 85.119.82.118/32 to
an end user by putting the equivalent of:
118-32 NS ns1.abominable.org.uk.
118-32 NS ns2.abominable.org.uk.
118 CNAME 118.118-32.82.119.85.in-addr.arpa.
into the zone 82.119.85.in-addr.arpa. So they have been delegated
the zone "118-32.82.119.85.in-addr.arpa". In their zone they
(apparently) have put the equivalent of:
118 PTR diablo.404.cx.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">but that doesnt work with powerdns on client side, at least for me.</pre>
</blockquote>
<p>The point is, it *does* work with *that specific IP address*</p>
<p>$ dig @10.0.0.53 +short -x 85.119.82.118<br>
118.118-32.82.119.85.in-addr.arpa.<br>
diablo.404.cx.</p>
<p>(10.0.0.53 is running pdns-recursor 4.1.9). It works.</p>
<p>However, there are different ways to set up reverse DNS
delegation for subnets smaller than /24. Therefore, trying to
copy this for your own zone probably won't work.<br>
</p>
<p>If you tell us the actual IP address block that you're trying to
get reverse DNS working for, then we can determine through DNS
queries how your ISP has configured the delegation - and thus tell
you how to configure the zone.</p>
<p>Regards,</p>
<p>Brian.<br>
</p>
</body>
</html>