[Feature Request] Ignore Hostname for dnsomatic

[bobyang]

Feature request:

In DDNS setup page, if we select DNS-O-Matic may we ignore hostname passing to DNS-O-Matic update API? DNS-O-Matic has identify their position on updating all other DDNS and won't provide a hostname. https://dnsomatic.com/docs/faq


The Hostname field is important because we use it everywhere in the router, like VPN server, AIcloud2, FileSharing, SSH, external WebUI access... etc. it makes no sense to have a wrong router URL as all.dnsomatic.com everywhere. And if we enter something else in the hostname like test123.afraid.org we got an error from DNS-O-Matc because that's not a valid hostname because the router use the following API and actually, if we don't have hostname parm, the update will go through without any issues.

https://useremail:userpassword@updates.dnsomatic.com/nic/update?hostname=

test123.afraid.org

 

[RMerlin]

AFAIK, it should already be ignoring DNS-o-Matic at least when creating an OpenVPN client config. Where are you seeing it still use all.dnsomatic.com?

 

[bobyang]

AFAIK, it should already be ignoring DNS-o-Matic at least when creating an OpenVPN client config. Where are you seeing it still use all.dnsomatic.com?

I just upgraded to 388.1 and yes, I saw it is using IP in *. ovpn

One step further. Is it possible when it is using DNS-O-Matic, DDNS "Host Name" will be used in ovpn as well and not getting errors on registration DDNS?

thanks

 

[RMerlin]

You will have to check the DNS-o-Matic documentation. I thought that DNS-o-Matic required you to use the all.dnsomatic.com hostname when updating with a DDNS client.

 

[bobyang]

You will have to check the DNS-o-Matic documentation. I thought that DNS-o-Matic required you to use the all.dnsomatic.com hostname when updating with a DDNS client.

I read their documentation, they said the hostname can be empty or not passing that param in through URL. However, if the router requires that field and cannot be empty, then use "all.dnsomatic.com".

DNS-o-Matic will never provide hostname.dnsomatic.com kind. Therefore, it will be good if DNS-o-Matic is selected, then hostname field value will be used anywhere on the router, such as OpenVPN, but not sending that value to dnsomatic for update. Or always send as all.dnsomatic.com and disregard the value in that field.

https://useremail:userpassword@updates.dnsomatic.com/nic/update
or
https://useremail:userpassword@updates.dnsomatic.com/nic/update?hostname=all.dnsomatic.com