an error occured while updating your ip opendns updater

#An error occured while updating your ip opendns updater update

So, in Cases 2 and 3, you don't explicitly define the FQDN on the interface which has the IP to be updated, so the ASA will use one of those other methods to determine what the FQDN should be. Configure the ASA host name, and define the domain in the dns server-group DefaultDNS Configure the ASA host name as your FQDN:ģ. This domain can be defined to be sent for DDNS updates in one of three ways.ġ.

#An error occured while updating your ip opendns updater update

It can be done in several different ways (per my interpretation of the documentation):ġ) Specifically LIST the FQDN on the interface that will be sending out the updates (outside interface), using the ddns update hostname command.Ģ) Give the ASA a hostname of the FQDN for your siteģ) Give the ASA a hostname, combined with defining the domain in the DNS server-group DefaultDNS (or other group).Īs an example, say your FQDN is. According to the documentation, you need to specify the FQDN that will be sent to the DDNS provider. One area I mulled over for quite a bit (because the documentation is pretty lame) deals with specifying the FQDN that you want to update with the IP address. Have you run a packet capture to see whether the requests are being sent out, and what the replies are? Or, if there even IS a reply? I still believe that it's a configuration issue on your ASA that is preventing the update from being sent. If this did not work, standalone clients such as ddclient would also fail to update DNS records. Just as your example shows, when going to the request gets directed to the appropriate load balancer front ending the servers that handle the update requests. If that's done, then the load balancer looks at the requested URL, and using content switching, will direct the request to the correct load balancer handling the servers that can answer the request. It is totally possible to set up multiple URLs, even to different domains, all from the same public IP address, provided that the public IP address is presented via a content switching load balancer. I work as a network engineer, and have extensive experience working with load balancers and content switching. With that said, I call BS on Cisco TAC's 'resolution' of your issue. I did find the DDTS ticket opened for your issue: I searched through the bug ID tool to see if there was an issue related to DDNS on the ASA that got fixed between 9.15.x and 9.16.x, but couldn't find anything. I'd appreciate any help about what to try next - thank you!

I've tried to enable the debug mode (debug ddns) and initiate the update, but it doesn't help much: DDNS update request = /nic/update?hostname=&myip=Īsa(config-if)# Failed to send HTTP(s) requestĭDNS: Another update completed, outstanding = 0 I can confirm if I curl that ddns url from the box inside of my network, I see it works (I see the confirmation in the email from dnsomatic), so it is not the credentials issue either. Success rate is 100 percent (5/5), round-trip min/avg/max = 20/20/20 ms

I can ping the ddns host, so the issue likely is not the connectivity, but ssl: ping Reason : Could not establish a connection to the server Last Update attempted on 07:45:14.815 UTC Mon Nov 9 2020 What I'm getting is: sh ddns update interface outside However, if a check the update status via show ddns update interface outside My config is: ddns update method dnsomatic_webĭon't know if its needed, but I also configured a ca trustpoint, as described in - downloaded a 'HydrantID SSL ICA G2' intermediate CA certificate and installed it via: crypto ca trustpoint DDNS_TrustpointĬrypto ca authenticate DDNS_Trustpoint nointeractive Hi all - has anybody tried to use the new web update-url for ddns introduced in 9.15.1?