Pdns: auth: remove SOA autofilling

Created on 12 Jun 2019  路  9Comments  路  Source: PowerDNS/pdns

  • Program: Authoritative
  • Issue type: Feature removal

Short description

Proposal: in 4.3.0, remove these settings:

# default-soa-mail  mail address to insert in the SOA record if none set in the backend
# default-soa-mail=
# default-soa-name  name to insert in the SOA record if none set in the backend
# default-soa-name=a.misconfigured.powerdns.server
# soa-expire-default    Default SOA expire
# soa-expire-default=604800
# soa-minimum-ttl   Default SOA minimum ttl
# soa-minimum-ttl=3600
# soa-refresh-default   Default SOA refresh
# soa-refresh-default=10800
# soa-retry-default Default SOA retry
# soa-retry-default=3600

This would close #6248, #5382, #4321, #3518.

It is my suspicion that not many users rely on the feature, or at least, that most of those that do, could also pretty easily live without, now that we've been pushing the API for a while.

@mind04 mentions that PowerAdmin users might be relying on this feature; we should check that and maybe help them change that.

auth

Most helpful comment

If we do this, we'll need to add a fill-unfilled-soas command to the pdnsutil in 4.2.x, so users can prepare their databases. For 4.3.0 we could keep that command, but then the user will have to specify the values on the commandline (e.g. fill-unfilled-soas ns1.example. hostmaster.domain.example. 10800 3600 604800 3600)

All 9 comments

Related #7918

If we do this, we'll need to add a fill-unfilled-soas command to the pdnsutil in 4.2.x, so users can prepare their databases. For 4.3.0 we could keep that command, but then the user will have to specify the values on the commandline (e.g. fill-unfilled-soas ns1.example. hostmaster.domain.example. 10800 3600 604800 3600)

@franklouwers points out that pdnsutil create-zone also uses these settings, so we either keep the settings but stop using them outside of create-zone, or we empower the create-zone user to control these values some other way.

As explained on irc: I like the fact that pdnsutil create-zone inserts a "sane" SOA by default, and that we can control what "sane defaults" it uses.

So while I understand this issue is mostly about autofilling non-complete SOAs, I would still like create-zone to use those parameters to create SOAs. I would propose the first option then.

Variant to the first option: replace the bottom 4 settings by a single setting that takes four numbers in a row.

Variant to the first option: replace the bottom 4 settings by a single setting that takes four numbers in a row.

I think that makes sense.... The API uses default-SOA-* settings when POSTing to the zone endpoint to create a domain

What is against creating a zone without records?
I prefer an empty zone over a magic default zone that always need editing.

A much better solution, for example, is to add an import a zone file option to create-zone.

Or add a "default-template-file" option which is used for all create zone actions.

What is against creating a zone without records?

The SOA's "disabled" field is used to disable the zone; and I think without the SOA record, various core bits don't "see" the zone. So at least that record has to exist.

I don't have time for this for 4.3.0; postponing until 4.4.0. Will need to bump that number in settings.rst.

Was this page helpful?
0 / 5 - 0 ratings