DynDNS and MX-record

[lada04]

Hi,

after many years on pfsense, I'm migrating to opnsense (24.7.8-amd64).

In pfsense, I had to use the complete URI to update the DynDNS (strato). In os-ddclient plugin (v1.25) there are profiles for many providers, but I haven't found an option to include the MX-record in the update. Finally I use the custom profile with custom-GET using the URI
   https://dyndns.strato.com/nic/update?mx=domain.cc

Is there a more elegant way to include the update of the MX record? My impression is that this option is not considered in the profiles. Actually it would be great to have an option in the webinterface to include also the MX-record.

[Monviech (Cedrik)]

But the MX record points to an FQDN, why would it need any updates?

[meyergru]

No, it may not, according to RFC 2181, at least you cannot specify a CNAME pointing to your dynamic entry.

There are also other types of records that cannot be specified as a CNAME, e.g.: @ (meaning the domain itself), because there are usually other entries that may be needed apart from an address, like MX or SOA or TXT records.

[lada04]

If I do not specify the MX record, the default server of the provider handles the email (and rejects).

[viragomann]

But you can specify the host name of your dynacmic IP as MX, which is static. So there should be no need to update it.

[lada04]

Yes, I agree, it is a fixed setting. However, each time I send an update after ip change, the default server is set again. I looked for a setting at my provider, but haven't found any option. I'll ask for support.

[lada04]

The provider explained to me that it is not possible to change the A-record without setting the MX-record.

[Monviech (Cedrik)]

Really they reset the whole zone if you send an update for single record? Which DNS provider is it?

[lada04]

It is an isp (strato) where dyndns is just an option. I suppose the MX record by default points to their server (for the whole zone) so after updating the A-record the MX-record needs to be individually adjusted if it should not point to the default server. I can specify an alternative MX record for my domain permanently but not in case of dyndns.

[lada04]

I just discovered that my attempt to include the update of the MX-record doesn't work, neither with native nor the ddclient backend.
Sending the update manually does. Is there any way to solve it with ddclient as implemented in opnsense?
I'd appreciate a simple solution like in pfsense, based on an arbitrary URI and authentication.