found a critical missing feature
Version 18.5 mr2 had cloudflare as a DDNS option V19 does not why was that removed or not added?
Also dnsomatic does not work either with just a noconnect message
found a critical missing feature
Version 18.5 mr2 had cloudflare as a DDNS option V19 does not why was that removed or not added?
Also dnsomatic does not work either with just a noconnect message
Some changes of V18.5 MR2 are not included in V19.0 EAP1. Those will be included in the next EAP Release (EAP2) coming over the next weeks.
__________________________________________________________________________________________________________________
what about dnsomatic
according to this dnsomattic is not configured right on the sophos page
and even following this i still do not get it to work with v19
Wondering, as i cannot commend on the DNS-o-Matic thing. Personally, i am using Google DNS for some time now.
__________________________________________________________________________________________________________________
I'm also waiting for Cloudflare Provider DDNS in V19 so if indeed its due in EAP2 I'll be fine to use that, I have tried to use DNS O Matic many times with V18.5 and V19 but for some reason I couldn't get it to work right. DNS-O-Matic works with Cloudflare itself but XG to DNS-O-Matic kept failing. But I recently tried Cloudflare DDNS with V18.5.2 which works perfectly, for now ill just wait until V19 gets Cloudflare added as a DDNS Provider.
JK
I did finally get it working on dnsomatic but it is a pain and the steps are not correct
can you share how you managed it; also can you say what you had to do different from what the documentation says to setup??
Just tried again and it fails with reason nohost??
Do not worry I managed to answer my own question through good old trial and error!! I had Sophos XG DDNS correct, I was wrong on the DNS-O-Matic setup, under the hostname I hadn't used the full FQDN only the Prefix once I added the FQDN under hostname it worked so basically I were assuming wrongly that the hostname and domain fields meant the FQDN would be the 2 fields combined but that assumption was wrong the domain was still required but for hostname It needed to be the full FQDN which now I'm assuming that hostname field needs to be the same set on XG's DDNS. Thanks for the hint that it worked. Does not help that the DNS o Matic documentation is not sufficient.
JK
Sophos firewall settings
dnosomatic
hostanme(.dns.net) this is the domain you create in DNSoMatic
in dnsomatic
hostname(.dns.net) this is what you create in cloudflare
domain
your real domain name
in cloudflare
Create a record that you will use in dnsomatic and sophos firewall
hostname(.dns.net) can be anything you want
now create a short name of what you actually want to have
cname
hostname than point to hostname(.dns.net).realdomain.com
Sophos firewall settings
dnosomatic
hostanme(.dns.net) this is the domain you create in DNSoMatic
in dnsomatic
hostname(.dns.net) this is what you create in cloudflare
domain
your real domain name
in cloudflare
Create a record that you will use in dnsomatic and sophos firewall
hostname(.dns.net) can be anything you want
now create a short name of what you actually want to have
cname
hostname than point to hostname(.dns.net).realdomain.com