Hi all,
(First post here, please let me know if anything can be improved. Cheers!)
I think I have found a design fault/mistake when using SophosXG DDNS with DNS-O-Matic, not sure if any of you also encountered the same.
Right now, I have setup DNS-O-Matic DDNS successfully with workaround (see below).
Sophos XG version: SFOS 18.5.1 MR-1-Build326 (Free/Home license)
Here is the issue description.
For example, I want to setup DDNS to ddns.mydomain.net
In XG's DDNS config page, you need to input FQDN in hostname, that is "ddns.mydomain.net",
if you input "ddns", you got the red box of error "DDNS "ddns" account could not be created" displayed on top.
However, after you input hostname as "ddns.mydomain.net", DNS-O-Matic will return "noshot", as it is expecting hostname "ddns" in API request.
This create a situation which seems Sophos XG did not allow you to input the value DNS-O-Matic is expecting.
The workaround working for me is as following:
In DNS hosting (I'm using CloudFlare):
+ A: ddns.dummy.net(.mydomain.net) = 1.2.3.4 (will be updated by DNS-O-Matic)
+ CNAME: ddns.mydomain.net = ddns.dummy.net.mydomain.net
(edit: CloudFlare will ignore the ending part which equals to your root domain, that why using dummy.net as A record)
In DNS-O-Matic Service:
+ Hostname: ddns.dummy.net
+ Domain: mydomain.net
+ Email & API Token: from your DNS hosting
In Sophos XG DDNS:
+ Hostname: ddns.mydomain.net
+ Service provider: DNS-O-Matic
+ Login name: DNS-O-Matic username
+ Password: DNS-O-Matic password
This seems to be a design mistake which makes setting up DDNS with DNS-O-Matic not so intuitive,
I have to study the API document and do some trial-and-error to figure out the above workaround.
Even though, I do admire having DNS-O-Matic in SFOS 18, it's a great feature which makes Sophos XG can work with many DNS hosting even if they aren't natively support by Sophos.
I personally use CloudFlare and TunnelBroker.net for my Home Lab, and it works great.
This thread was automatically locked due to age.