hi, we're migrating from bind to powerdns and get confused about how to setup reverse delegation correctly, since subnets smaller /24 seems not to work out oft he box.
example: our ISP delegates the subnet 10.10.10.192/27 to our server as primary NS. what ist he correct way to setup this reverse zone? in bind we just used the zone 192.10.10.10.in-addr-arpa with PTRs from 193 to 222 and it worked without problems. the zone2sql tool converted this zone to powerdns, but it wasn't working as expected. it seems that powerdns thinks 192.10.10.10.in-addr.arpa 10.10.10.192/32! when changing the zone to 10.10.10.in-addr.arpa it works, but i think this means, powerdns manages this zone for 10.10.10.0/24 subnet not 10.10.10.192/27. so i'm wondering, what ist he correct way to setup such a reverse zone in powerdns? while searching for the right answer, i stumbled upon RFC2317 which from what i understand explaines how the ISPs have to setup their nameservers to provide subnets smaller than /24 to customers. does this mean the in-addr.arpa lookups only works in /24 chunks? regards. MK
_______________________________________________ Pdns-users mailing list [email protected] https://mailman.powerdns.com/mailman/listinfo/pdns-users
