<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>On Thu, 2019-07-18 at 23:02 +0000, bryantz-pdns@zktech.com wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><div>We have a /27 block of IP's from our datacenter</div><div><br></div><div>Using binddns we listed them like this example </div><div><br></div><div>zone file - 60/27.1.1.1.in-addr.arpa</div><div>We then added PTR records for it would looks something like</div><div><br></div><div>62.60/27.1.1.1.in-addr.arpa. IN PTR <a href="//mail.ourserver.net" target="_blank">mail.ourserver.net</a></div><div>63.60/27.1.1.1.in-addr.arpa. IN PTR mail.ourotherserver.net</div><div><br></div><div>For some reason PowerDNS will not handle the reverse zone as 60/27.1.1.1.in-addr.arpa</div><div>It will not respond to reverse dns lookup requests. </div><div><br></div><div>If I pull the 60/27. off and use just the first 3 octets of the domain / zone I can get reverse lookup to work, but </div><div>We can't respond to the full /24 as we only have smaller blocks. </div><div><br></div><div>Is there any clean way to only listen on a subnet for reverse DNS lookup?</div><div><br></div></div><div><br></div><div><div>Any ideas on how to fix this?</div></div></blockquote><div><br></div><div><br></div><div>rfc2317 is the standard way to achieve this, which it looks like you're trying to do.</div><div><br></div><div>I just put your example (more or less) into a powerdns 4.1.10 bind backend config and it serves the PTRs just fine.</div><div><br></div><div>You likely just have a syntax error somewhere (like missing the trailing dots as in your example above) or the datacenter didn't set the CNAMEs or NS delegation correctly.</div></body></html>