get running config from recursor?
Charles Sprickman via Pdns-users <[email protected]> Sat, 30 May 2026 13:09:24 -0400
| Newsgroups | gmane.network.dns.powerdns.user |
|---|---|
| Message-ID | <[email protected]> |
--===============7972728025055256415== Content-Type: multipart/alternative; boundary="Apple-Mail=_49064816-AE95-48D7-89F6-5E8897FA9CF4" --Apple-Mail=_49064816-AE95-48D7-89F6-5E8897FA9CF4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all, This is a simple one, fits entirely in the subject line. :) I know I can get the startup config from the API or "rec_control = get-parameter [the paramater I want to check]", but how do I get the = current running config. I imagine most of your users at this point are folks running giant sites = and all, but we started using the recursor way, way back when we found = djb's dnscache couldn't keep up with what we were doing - like really = early days IIRC, and we just stuck with it, so please bear with me a bit = - I'm not at all a power user here, I haven't even touched things like = dnsdist (or had a need to) Basic scenario - I have the recursor running and want to make a change = to the running config, for example: "rec_control set-minimum-ttl 1000" And in the config file that value is either not set or is set to a = different value Now I come back in a few weeks and ask myself "what did I set that to? I = should probably put it in the config file!", so: "rec_control get-parameter minimum-ttl-override" And that provides me with the configured, but no running config. Same for something like: curl -s -H 'X-API-Key: secret' = http://10.99.88.131:8082/api/v1/servers/localhost/config|grep minimum I kind of hijacked a github issue, but I think we were talking past each = other here: https://github.com/PowerDNS/pdns/issues/2580 It should be possible to see the running config somewhere, right? Even = people running in a fully containerized, automated environment start = with some initial tinkering in a test environment somewhere where = they're manually making changes by hand and testing, right? And you need = to know where your config is at after a bunch of fiddling about with = various params... Thanks, Charles= --Apple-Mail=_49064816-AE95-48D7-89F6-5E8897FA9CF4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" = content=3D"text/html; charset=3Dus-ascii"></head><body = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;">Hi all,<div dir=3D"auto" = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;"></div><div><br></div><div>This is a = simple one, fits entirely in the subject line. = :)</div><div><br></div><div>I know I can get the startup config from the = API or "rec_control get-parameter [the paramater I want to check]", but = how do I get the current running config.</div><div><br></div><div>I = imagine most of your users at this point are folks running giant sites = and all, but we started using the recursor way, way back when we found = djb's dnscache couldn't keep up with what we were doing - like really = early days IIRC, and we just stuck with it, so please bear with me a bit = - I'm not at all a power user here, I haven't even touched things like = dnsdist (or had a need to)</div><div><br></div><div>Basic scenario - I = have the recursor running and want to make a change to the running = config, for example:</div><div><br></div><div>"rec_control = set-minimum-ttl 1000"</div><div><br></div><div>And in the config file = that value is either not set or is set to a different = value</div><div><br></div><div>Now I come back in a few weeks and ask = myself "what did I set that to? I should probably put it in the config = file!", so:</div><div><br></div><div>"rec_control get-parameter = minimum-ttl-override"</div><div><br></div><div>And that provides me with = the configured, but no running config.</div><div><br></div><div>Same for = something like:</div><div><br></div><div>curl -s -H 'X-API-Key: secret' = http://10.99.88.131:8082/api/v1/servers/localhost/config|grep = minimum</div><div><br></div><div>I kind of hijacked a github issue, but = I think we were talking past each other = here:</div><div><br></div><div><a = href=3D"https://github.com/PowerDNS/pdns/issues/2580">https://github.com/P= owerDNS/pdns/issues/2580</a></div><div><br></div><div>It should be = possible to see the running config somewhere, right? Even people running = in a fully containerized, automated environment start with some initial = tinkering in a test environment somewhere where they're manually making = changes by hand and testing, right? And you need to know where your = config is at after a bunch of fiddling about with various = params...</div><div><br></div><div>Thanks,</div><div><br></div><div>Charle= s</div></body></html>= --Apple-Mail=_49064816-AE95-48D7-89F6-5E8897FA9CF4-- --===============7972728025055256415== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Pdns-users mailing list [email protected] https://mailman.powerdns.com/mailman/listinfo/pdns-users --===============7972728025055256415==--