update a TXT record containing an SPF string? #208

Closed
opened 2025-11-20 04:21:33 -05:00 by saavagebueno · 4 comments
Owner

Originally created by @JuicyFruiter on GitHub (Aug 26, 2022).

Hi,
As a possible feature, I'd like to be able to update a TXT record which is currently in the format:
v=spf1 a mx ip4:example.com ~all

Because the SPF record refers to a domain name instead of an IP address, this is causing a low email reputation.
I'd like to be able to use ddns-updater to update the TXT record to:
v=spf1 a mx ip4:123.123.123.123 ~all

Is this supported already? or if not, can it be integrated, please?

Originally created by @JuicyFruiter on GitHub (Aug 26, 2022). Hi, As a possible feature, I'd like to be able to update a TXT record which is currently in the format: v=spf1 a mx ip4:example.com ~all Because the SPF record refers to a domain name instead of an IP address, this is causing a low email reputation. I'd like to be able to use ddns-updater to update the TXT record to: v=spf1 a mx ip4:123.123.123.123 ~all Is this supported already? or if not, can it be integrated, please?
Author
Owner

@qdm12 commented on GitHub (Aug 26, 2022):

Not supported, but it won't be implemented anytime soon, there is already a huge backlog of issues, I'm the sole maintainer and I'm pretty much out of time continuously. Sorry, maybe one day though!

@qdm12 commented on GitHub (Aug 26, 2022): Not supported, but it won't be implemented anytime soon, there is already a huge backlog of issues, I'm the sole maintainer and I'm pretty much out of time continuously. Sorry, maybe one day though!
Author
Owner

@favonia commented on GitHub (Sep 7, 2022):

@JuicyFruiter Out of curiosity, why is the ip4 SPF mechanism needed when the a SPF mechanism is in use and A and/or AAAA DNS records are probably updated by ddns-updater? My naive reading of the standards seems to indicate that the ipv4 SPF mechanism (which should match exactly the same IP the A DNS record is pointing to) is not needed in this case.

@favonia commented on GitHub (Sep 7, 2022): @JuicyFruiter Out of curiosity, why is the `ip4` SPF mechanism needed when the `a` SPF mechanism is in use and `A` and/or `AAAA` DNS records are probably updated by ddns-updater? My naive reading of the standards seems to indicate that the `ipv4` SPF mechanism (which should match exactly the same IP the `A` DNS record is pointing to) is not needed in this case.
Author
Owner

@JuicyFruiter commented on GitHub (Sep 8, 2022):

Interesting and good spot! Not an intended inclusion - I used an automatically generated service to generate the SPF record when troubleshooting an issue during initial setup (the issue had been resolved by deleting and re-creating the SPF record from scratch, but at some point I had assumed that the syntax must have been incorrect so used an automatically generated field along the way.)

@JuicyFruiter commented on GitHub (Sep 8, 2022): Interesting and good spot! Not an intended inclusion - I used an automatically generated service to generate the SPF record when troubleshooting an issue during initial setup (the issue had been resolved by deleting and re-creating the SPF record from scratch, but at some point I had assumed that the syntax must have been incorrect so used an automatically generated field along the way.)
Author
Owner

@JuicyFruiter commented on GitHub (Sep 8, 2022):

Update: Thanks. I think that has resolved the need for this feature request. removing the ip4 mechanism means the ip address is no longer required 👍

@JuicyFruiter commented on GitHub (Sep 8, 2022): Update: Thanks. I think that has resolved the need for this feature request. removing the `ip4` mechanism means the ip address is no longer required 👍
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#208