Realtimeregister provider pushing 0 priority to MX or SRV fail

[gunleik]

Describe the bug Realtimeregister provider pushing 0 priority to MX or SRV return: {"errors":{"6":{"prio":["Must be set for type MX"]}},"message":"Errors have been found in the DNS records","type":"DnsConfigurationException"} According to RealTimeRegister process log the API request did not contain any priority. Priority of 1 and above is ok.

To Reproduce Steps to reproduce the behavior: push a config with MX("@", 0, "mx1.xyz.com."),

Expected behavior Successful push and the priority of the MX or SRV record to be set to 0

DNS Provider Realtimeregister (I have not tested other providers)

[gunleik]

I testet the same with provider digitalocean, that works fine with priority 0. So either the digitalocean provider sends 0 as the priority or the API interprets unset priority as 0.

[gunleik]

Had time to look a bit at the code. I believe this might be the reason https://github.com/StackExchange/dnscontrol/blob/1a7cb205999b130f025e5e4c25752182d34dc43a/providers/realtimeregister/api.go#L39C30-L39C39

[cafferata]

Ping @PJEilers, the maintainer of the Realtime Register provider.

[PJEilers]

I will look into it

[cafferata]

Fixed by https://github.com/StackExchange/dnscontrol/pull/3724 & https://github.com/StackExchange/dnscontrol/pull/3725