Open tkald opened 7 years ago
It could certainly be done, though since it's not a feature that I would use, perhaps you could help by describing how you might expect it to work from a user perspective?
Would you be managing separate zones on each server? If so, would you expect the list of zones to be all presented together, or separated in some way? A higher level of navigation above the zone level perhaps? Or just include the server name in the zone list table?
Would you expect the need to have a different administrative group for each server?
Any further thoughts about how it should work?
Thanks for your interest and for any further information you can provide.
@thomasp-opera
From my perspective, I imagine that we could have first top ui tab "servers", so you can switch between dns servers.
Every server has it's own zones, templates. Admin group users with possibility to grant server/zone permissions to regular users. Personally I don't need different admin or user groups for every server but someone else might.
So adding / editing / removing servers from UI (or into config file) we could define per Powerdns server:
+1
Any network of decent size has redundant DNS servers. Managing them all from one UI makes the most sense.
I'd like to voice support for this as well. The PowerDNS API also has support for multiple servers, but every web UI I've seen so far is either hard-coded to use localhost
or only a single user-configured server. Being able to specify multiple DNS URLs and also being able to use all of the servers listed by the /api/v1/servers
endpoint would be amazing.
Example with server "localhost", which is the only server returned by pdns_server or pdns_recursor. pdnsmgrd and pdnscontrol MUST NOT return “localhost”, but SHOULD return other servers. https://doc.powerdns.com/authoritative/http-api/server.html
Would be nice if we could manage more than one PowerDns server...