mirror of
https://github.com/qdm12/ddns-updater.git
synced 2026-07-07 14:31:43 -04:00
Feature request: [Strato] set custom MX Record #95
Assignees
saavagebueno
Clear assignees
saavagebueno
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/ddns-updater#95
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wawerzineks on GitHub (Feb 2, 2021).
Originally assigned to: @qdm12 on GitHub.
I am using the MX Record option for strato, e.g.:
https://dyndns.strato.com/nic/update?hostname=domain.com&myip=ip&system=dyndns&wildcard=NOCHG&mx=mail.provider.com&backmx=NOCHG"`
Would it be possible to integrate such a option?
@fredericrous commented on GitHub (Feb 7, 2021):
Hey @wawerzineks, what is the wildcard option? Documentation is hard to find for strato, I can see the options
mxandbackmxare valid and that the default value is NOCHG like No Change, but I don't seewildcard. The best doc I found is here (in German): https://www.strato.de/faq/domains/so-einfach-richten-sie-dyndns-fuer-ihre-domains-ein/And what about system. I understand that if it is omitted it defaults to dyndns but what is this option for?
I'm trying to understand because if we update the provider for strato, it would be interesting to support all the options in one go.
UPDATE: looking at dnsomatic provider, it seems to be the same API. wildcard should then be either NOCHG or ON
@qdm12 commented on GitHub (Feb 7, 2021):
I think @wawerzineks wants support for MX records on top of A and AAAA records. I guess it's possible to add it for strato only for now.
Regarding user inputs in the json config, would a
"custom_record_type"field be ok? Or maybe have a"record_type"for all providers where you could set it toA,AAAAorMX(for strato only for now)?@wawerzineks commented on GitHub (Feb 8, 2021):
@fredericrous good question, I think it is an obsolete option and was related to something like subdomains. But for now this topic is not covered by the official Strato documentation anymore. All options you can set in the Strato Admin Center are the following:
@qdm12 right, I think the first option would be sufficient, otherwise existing configs would have to be changed right?
@qdm12 commented on GitHub (Feb 8, 2021):
We could change the scheme and still support older fields, but yeah it's not ideal for the poor developers haha
So just to be clear, you would want to set your IPv4 (or IPv6) address as a value for your MX-record right? I think adding a custom_record_type would be nice for now, we can always do a v2 one day to break things eventually.
@wawerzineks commented on GitHub (Feb 9, 2021):
Yep, but not exactly my IPv4, more a DNS Name of a Email-Provider, like aspmx.l.google.com
@qdm12 commented on GitHub (Feb 9, 2021):
Sorry if I'm missing the point but why would you need this program to add a constant value to your domain?
@wawerzineks commented on GitHub (Feb 9, 2021):
When I activate the DynDNS option at Stratos Admin Center the MX Record can exclusively be set by the dyndns client and the button for managing the mx record gets deactivated. I guess this is just a behavior of Strato :(
@qdm12 commented on GitHub (Feb 9, 2021):
Interesting, although maybe a bit out of scope. Maybe reach out to them so they fix their UI or give a reason for that 'graying'? If they're not willing to fix it, we could have a field specific to strato for mx records so that it sets it at the program start only once?