My asuscomm.com DDNS isn't working properly on my Asus RT-BE92U

[cubim]

I have an Asus RT-BE92U router with Asuswrt-Merlin firmware 3006.102.6, daisy-chained to my ISP's Huawei router, from which it obtains a private IPv4 address and a public IPv6 address. My problem is that I've never been able to use the asuscomm.com DDNS and I have to use cron jobs to update my DDNS from other public internet services.

Sometimes I get IPv4 results from the command 'dig A <private-ddns>.asuscomm.com', or IPv6 results from the command 'dig AAAA <private-ddns>.asuscomm.com', but this doesn't always happen.

Does anyone know why my asuscomm.com DDNS isn't working properly?

 

[Tech9]

Intermittent issues with ASUS free DDNS service were reported multiple times. You may want to explore and switch to more reliable DDNS services.

 

[hervon]

I have been on Afraid freedns for years but lately it has not been very reliable. Any suggestion for other free reliable DDNS service ? Thanks.

 

[octopus]

I have been on Afraid freedns for years but lately it has not been very reliable. Any suggestion for other free reliable DDNS service ? Thanks.

I have used afraid.org for years and it was working just fine whole time.
Using theirs token to login to update.
Only thing is when free domain is deleted for som reason, have to generate new tokens.

 

[bennor]

No issue, for years, with the free No-IP.com other than getting a email every 30 days from them where one renews the free service.

 

[Tech9]

Free and Reliable usually don't go very well in one sentence. I personally have for years so called "Enhanced Dynamic DNS" plan with No-IP ($3/month), but I also use DDNS service on multiple locations. The "Free Dynamic DNS" plan is perhaps good enough for home use in single location.

 

[hervon]

I have used afraid.org for years and it was working just fine whole time.
Using theirs token to login to update.
Only thing is when free domain is deleted for som reason, have to generate new tokens.

I’ll regenerate new tokens to try to fix the issue. Thanks.

 

[octopus]

I’ll regenerate new tokens to try to fix the issue. Thanks.

You only need token (afraid.org-keyauth), no username.
Use eg a (dot) as that field can't be blank.

 

[RMerlin]

Afraid has been very reliable for me for many years.

 

[hervon]

Guess issue is on my side. I’ll check that. Thanks!

 

[martinr]

I have an Asus RT-BE92U router with Asuswrt-Merlin firmware 3006.102.6, daisy-chained to my ISP's Huawei router, from which it obtains a private IPv4 address and a public IPv6 address. My problem is that I've never been able to use the asuscomm.com DDNS and I have to use cron jobs to update my DDNS from other public internet services.

Sometimes I get IPv4 results from the command 'dig A <private-ddns>.asuscomm.com', or IPv6 results from the command 'dig AAAA <private-ddns>.asuscomm.com', but this doesn't always happen.

Does anyone know why my asuscomm.com DDNS isn't working properly?

Welcome to the forum.

I have used asuscomm.com for my DDNS for many years - well over 10 - I only once encountered a problem, and I believe that was probably of my own making. I’d say I use it daily, for my VPN server. Its appeal to me was its ease of setup; it’s so easy, quick and pain-free that the first time I set it up I thought I must have missed something.

My point is, I wouldn't be too hasty to blame asuscomm.com: your problem may well lie elsewhere eg on your daisy-chain setup? But your testing with a different DDNS will soon provide a definitive answer.

 

[hervon]

Guess issue is on my side. I’ll check that. Thanks!

Finally the issue was with the modem that created a double NAT. Nothing to do with afraid.org. Fixed. Thanks.

 

[cubim]

Welcome to the forum.

I have used asuscomm.com for my DDNS for many years - well over 10 - I only once encountered a problem, and I believe that was probably of my own making. I’d say I use it daily, for my VPN server. Its appeal to me was its ease of setup; it’s so easy, quick and pain-free that the first time I set it up I thought I must have missed something.

My point is, I wouldn't be too hasty to blame asuscomm.com: your problem may well lie elsewhere eg on your daisy-chain setup? But your testing with a different DDNS will soon provide a definitive answer.

Thanks for your reply. My DDNS names work on both IPv4 and IPv6, and they're complex: valid letters, numbers, and special characters. Since I've had problems with the asuscomm.com DDNS, I simultaneously use two other free internet services that I don't want to mention (asuscomm via the router's web configuration plus two cron scripts within the router). With the first DDNS, asuscomm.com, the registration is valid but only lasts a few days; with the second DDNS, which is a popular free service, it works quite well, although sometimes the service's administration website goes down, but IP address resolution is usually correct; with the third DDNS, it's a small, little-known, and free service that's difficult to configure, but it always works very well. In my country, internet access is controlled by powerful interests with court authorization, and this is why I don't mention the DDNS services I use.

I'll try the asuscomm.com DDNS again with a simpler name. Thanks.

 

[martinr]

Thanks for your reply. My DDNS names work on both IPv4 and IPv6, and they're complex: valid letters, numbers, and special characters. Since I've had problems with the asuscomm.com DDNS, I simultaneously use two other free internet services that I don't want to mention (asuscomm via the router's web configuration plus two cron scripts within the router). With the first DDNS, asuscomm.com, the registration is valid but only lasts a few days; with the second DDNS, which is a popular free service, it works quite well, although sometimes the service's administration website goes down, but IP address resolution is usually correct; with the third DDNS, it's a small, little-known, and free service that's difficult to configure, but it always works very well. In my country, internet access is controlled by powerful interests with court authorization, and this is why I don't mention the DDNS services I use.

I'll try the asuscomm.com DDNS again with a simpler name. Thanks.

Thank you, Cubim. Please do keep us updated.

Martin

 

[cubim]

My Asus DDNS stopped working today. The 'dig' command behaves as if my DDNS is unregistered and shows no IPv4 or IPv6 values, even though my Asus router's web interface shows it as registered. The website https://iplookup.asus.com/nslookup.php confirms that my DDNS is not registered.

Furthermore, when trying to use a custom script for Asus DDNS, I was horrified to find that the asuswrt-merlin script dated February 22, 2025, at https://github.com/RMerl/asuswrt-merlin.ng/wiki/DDNS-Sample-Scripts#asus is a complete disaster:

- The "wgc1" network interface does not exist on my router and could be disabled because it is entirely unnecessary.

- The 'echo' commands are also out of place in a cron script; some should be omitted and others replaced with the 'logger' command so they appear in the router's 'System Log'.

- The VPNIP variable is meaningless and should be replaced with the IPv4 and IPv6 variables.

- Obtaining the IP address via http://myip.dnsomatic.com/ does not use HTTPS protection and often fails due to server overload; the method for obtaining the IP address needs to be changed.

- Sending the IP address to the Asus server does not use HTTPS protection, and I'm not even sure it will work.

In short, the web-based DDNS configuration asuscomm.com on the Asus router in a double NAT environment is unusable, and the asuswrt-merlin script https://github.com/RMerl/asuswrt-merlin.ng/wiki/DDNS-Sample-Scripts#asus is insecure and unusable.

I would like an expert from asuswrt-merlin to review and modify the asuscomm.com DDNS script in the firmware of Asus routers.

 

[RMerlin]

I would like an expert from asuswrt-merlin to review and modify the asuscomm.com DDNS script in the firmware of Asus routers.

That script is probably obsolete and shouldn`t be used. Asuswrt has had built-in DDNS support for their own DDNS since day one, and I did the initial backport of their support in inadyn, which since then has been taken over and maintained by Asus themselves as they moved to a new API.