search

operasoftware / dns-ui

Opera's LDAP-authenticated PowerDNS user interface
Apache License 2.0
282 stars 57 forks source link

autocreate_reverse_records does not work with powerdns > 4.4 #192

Open aba-rechsteiner opened 2 years ago

aba-rechsteiner commented 2 years ago

as of PowerDNS version 4.4 the set-ptr feature is no longer supported and therefore the autocreate_reverse_records does not work.

https://github.com/PowerDNS/pdns/pull/9593/files#diff-7240b871c4a8ef68cfaf28739c49d762abb6613c13b176ab776256930f4705a1

thomas-pike commented 2 years ago

That's unfortunate :( I guess we either have to remove the functionality, or, preferably implement it ourselves.

aba-rechsteiner commented 2 years ago

yes I think this is a must have, because you always need a PTR for an A/AAAA record. It would be really cool if this would be implemented.

XANi commented 1 year ago

It actually works in funny way for us - for existing PTR domains it works, for nonexisting ones we get nondescriptive

image

and corresponding stack trace

2023/02/03 12:27:18 [error] 545#545: *2811 FastCGI sent in stderr: "
PHP message: 1675423638: BadData in /var/www/html/dns-ui-0.2.7/model/zone.php:727
PHP message: 1675423638: Stack trace:
PHP message: 1675423638: #0 /var/www/html/dns-ui-0.2.7/views/api.php(147): Zone->process_bulk_json_rrset_update()
PHP message: 1675423638: #1 /var/www/html/dns-ui-0.2.7/views/api.php(63): API->update_zone_rrsets()
PHP message: 1675423638: #2 /var/www/html/dns-ui-0.2.7/views/api.php(106): API->options()
PHP message: 1675423638: #3 /var/www/html/dns-ui-0.2.7/views/api.php(33): API->zone()
PHP message: 1675423638: #4 /var/www/html/dns-ui-0.2.7/requesthandler.php(62): require('/var/www/html/d...')
PHP message: 1675423638: #5 /var/www/html/dns-ui-0.2.3/public_html/init.php(18): require('/var/www/html/d...')
PHP message: 1675423638: #6 {main}" while reading response header from upstream, client: 127.0.0.1, server: _, request: "PATCH /api/v2/zones/example.com. HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "www.example.com", referrer: "https://www.example.com/zones/non.3dart.com?name=ttt"

We'd be entirely fine with PTR zones not being created automatically (more than fine; that's actual use case for us, we don't want to create PTR for random domains clients give us to manage and have to point to some external IP) , or records not being created if PTR doesn't exist, just don't block editing records