Guest User!

You are not Sophos Staff.

cloudflare ddns

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

Parents Reply
  • 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

Children
  • 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