Hi Martin n 25/01/2019 09:33, Martin Kellermann via Pdns-users wrote: > hi Andy, > >> 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. > > but that doesnt work with powerdns on client side, at least for me. > taking your example with /31 instead of /32, the client zone would be named > "118-31.82.119.85.in-addr.arpa" and contains > 118 PTR diablo.404.cx. > 119 PTR xyz.404.cx. > unfortunately, this does not work with powerdns. setting up such a zone and > doing a > dig 85.119.82.119 [client powerdns IP] gives a "Host > 85.119.82.119.in-addr.arpa not found: 5(REFUSED)" > when renaming the zone to "82.119.85.in-addr.arpa" it works - obviously. > but this can't be correct. since the client server will give wrong answers > for 85.119.82.0-117 and 85.119.82.120-255 > sorry, i really can't see, what i am missing.
You cant ask your dns directly, it only knows about the zone 118-31.82.119.85.in-addr.arpa. So you would need do do: dig 118.18-31.82.119.85.in-addr.arpa ptr @dnsip to get a correct result you have to ask the dns at the provider and there you get back a cname pointing to your entry,. Regards Matthias -- Matthias Cramer / mc322-ripe Senior Network & Security Engineer iway AG Phone +41 43 500 1111 Badenerstrasse 569 Fax +41 44 271 3535 CH-8048 Zürich http://www.iway.ch/ GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E 3959 B62F DF1C 2D20 8250 _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users