This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ddns issue

Hi,

I'm having a strange issue with DDNS on our XG firewall (firmware SFOS 17.5.0 GA).

Using the Sophos DDNS service everything seems to work as expected, the IP address is regularly updated without any failure.

However, when pinging "g****t.myfirewall.co", I get  "could not find host". Waiting more than 24 hours didn't solve the problem. The address is updated in the firewall, but unreachable.

Pinging the ip address works fine, also connecting through SSL VPN by using the ip address.

Any ideas ?

Rudolph



This thread was automatically locked due to age.
Parents
  • Which DNS Server do you use? 

    The myfirewall.co DNS Record should be globally available. 

    Is the XG behind some NAT or something else? 

    __________________________________________________________________________________________________________________

Reply
  • Which DNS Server do you use? 

    The myfirewall.co DNS Record should be globally available. 

    Is the XG behind some NAT or something else? 

    __________________________________________________________________________________________________________________

Children
  • Hi,

    Thanks for your reply.

    Using DNS servers from Internet provider (Orange in France). And yes, XG is behind NAT (in provider's router's DMZ).

    But I don't see how DNS server could be the problem, since XG ddns updates regularly with the correct NATed public IP address.

    Pinging "x.myfirewall.co" doesn't work, whatever DNS server I use (not through mobile network, not through completely other Internet provider).

    Exactly the same setup has worked fine with another XG box (and a different x.myfirewall.co name).

    ?

  • Can you perform some dig / nslookup ´s with different DNS Servers to check, if your DNS Record is already published? 

    Maybe there is some issue currently with this service. 

    __________________________________________________________________________________________________________________

  • By using digwebinterface.com (all nameservers) I only get

    myfirewall.co. 899 IN SOA ns-1407.awsdns-47.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

    from all DNS servers (nothing in front of the myfirewall.co domain)

     

    When I lookup one of my other XG ddns boxes I get

    xxxxxxx.myfirewall.co.	59	IN	A	90.50.86.220



    So it looks like the XG box updates the IP address but the record is not published?

  • __________________________________________________________________________________________________________________

  • After reboot:

     

    Dec 24 18:07:50.821670: Environment variable DDC = { "accountid": [ 1 ], "loginn
    ame": [ "" ], "password": [ "" ], "refreshinterval": [ 20 ], "hostname": [ "g****t.myfirewall.co" ], "extiface": [ "Port2" ], "checkipusingport": [ "standard" ]
    , "displayname": [ "Sophos" ], "serverstring": [ "myfirewall.co" ], "iptype": [
    "0" ], "ipaddress": [ "192.168.0.254" ] }
    Dec 24 18:07:50.827377: set_plugin_routines: Sophos not found
    Dec 24 18:07:50.827420: add_plugin: invalid plugin Sophos
    Dec 24 18:07:50.827593: DDC initialized successfully

     And in GUI XG says last updated time 2018-12-24 18:13:02, success and correct public IPaddress.......

    In system log (GUI):

    2018-12-24 18:13:02SYSTEMmessageid="17815" log_type="Event" log_component="DDNS" log_subtype="System" status="Success" host="g****t.myfirewall.co" updated_ip="90.**.**.***" reason="" message="DDNS update for host gelpat.myfirewall.co was Successful. Updated with IP 90.**.**.2***."

  • I'm also facing the same issue. 

    2018-12-25 02:58:39SYSTEMmessageid="17815" log_type="Event" log_component="DDNS" log_subtype="System" status="Success" host="n****8.myfirewall.co" updated_ip="192.228.218.73" reason="" message="DDNS update for host n****8.myfirewall.co was Successful. Updated with IP 192.228.218.73."

    It says Successful but when I try to resolve its not resolving to the latest IP.