Is Asus DDNS Service Reliable?

[Ken Firch]

I've had my ASUS router registered with their asuscomm.com DDNS service for a long time, but have recently noticed a few connection issues while trying to connect to my NVR service. Sometimes, the iPhone NVR software can't find the NVR when using the registered MyHostName.asuscomm.com domain, but will always connects if I use the private 192.168.50... IP. The DDNS settings look good, the correct DDNS name is displayed on the Network Map page. The WAN port forwarding looks good.

Is anyone else having good luck using the ASUS DDNS service?
Is it reliable?
Should I use another DDNS service, not ASUS?

Thanks, Ken

 

[Tech9]

Is it reliable?

Has a record of reliability related issues in the past.

Asus DDNS problems?

Anyone else having Asus DDNS service issues? Router was connecting fine once set up, now I keep getting 'Server Error' on both the router and the asus smartphone app.

www.snbforums.com

DDNS Service -- Which is best?

I want to setup a VPN server. I understand that a DDNS service is required. In the DDNS tab in the WAN section of Merlin, there are 13 preset DDNS services to choose from and a custom. WWW.ASUS.COM DOMAINS.GOOGLE.COM WWW.DYNDNS.ORG (3) WWW.SELFHOST.DE WWW.ZONEDIT.COM WWW.DNSOMATIC.COM...

www.snbforums.com

 

[jksmurf]

I've had my ASUS router registered with their asuscomm.com DDNS service for a long time

I'm in the same boat as you, must be ten years plus with asuscomm.com, not noticed any major issues to be fair, although had the occasional hiccup with the Let's Encrypt certificate. Maybe I should try the afraid.org option, seems popular here.

 

[RMerlin]

First, check if the DDNS resolves to the correct IP address. If it doesn't, then your issue is not with the DDNS, but elsewhere in your setup.

 

[Ken Firch]

First, check if the DDNS resolves to the correct IP address. If it doesn't, then your issue is not with the DDNS, but elsewhere in your setup.

Yes, both nslookup and traceroute return the correct IP address. Of course the Asus DDNS service is working fine right now, and I can't troubleshoot it.
Maybe one of those Monday morning operating issues that are discovered and fixed.

 

[fotingo]

First, check if the DDNS resolves to the correct IP address. If it doesn't, then your issue is not with the DDNS, but elsewhere in your setup.

@RMerlin

Hi Merlin,
I've been having some issues with the DDNS service on my router. I have been using Asus, but lately it has been giving me issues.
If the ISP modem reboots or losses connection, once it comes back online, the DDNS service will not restart automatically as it stays "Inactive".

I have tried No-IP and it behaves similarly, once the modem comes back online, the service gets stuck in Processing and never starts up again.

Even If I Apply settings again, it stays in Processing. Is there a setting I need to change in order for the DDNS service to restart automatically?

 

[WTOram]

I run a pair of Thinkbroadband.com quality monitors 24/7 - one for Ipv4 and one for ipv6. In the past, I have tried to use my asuscomm.com DDNS FQDN for the ipv4 monitor but now (and for the last year or so) I just configure it with my ip address directly because, when using the domain name, the quality monitor was showing between three and six gaps in the connectivity reporting every day when the ipv6 one (always configured with the ip address) showed no connectivity issues at all.

As soon as I changed to using the ip address, the apparent drops in connectivity shown by the monitor dissapeared. My conclusion was that the asuscomm.com DDNS service was not reliable and failed to resolve to an ip address periodically during the course of the day.

 

[WTOram]

Just after my last post, I set up a new broadband quality monitor uaing my Asuscomm.com domain name. After 5 hours, this is what I see:

As you can see, within the last 5 hours there have been 4 periods (including the last failure which has not yet fixed itself) when the DDNS domain has not resolved to an ip address.

Conclusion: No. The asuscomm.com DDNS service is not reliable.

Edit: after 24 hours there were 14 such DDNS failures.