What's new

Has Asus abandoned asuscomm.com DDNS

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Maybe you meant to say that the "yourname" part of the "yourname.myname.com" is a PQDN? Becasue "yourname.myname.com" ends in "com" TLD and you can do a proper dns lookup on it.


which assumes asuscomm.com does not allow myname.asuscomm.com to exist on root.
The root name servers only answer for queries for TLDs, they don't have any knowledge regarding asuscomm.com. So there's no "allow" to begin with.
If you are to resolve "myname.asuscomm.com", first you go to root name server. It points you to the name server for ".com" (a.gtld-servers.net.) alone with the IP address with it. Then you go to a.gtld-servers.net to ask about asuscomm.com, it then tells you that asuscomm.com has been delegated to ns1.asuscomm.com. Then you go to ns1.asuscomm.com to get your final answer. As shown below.
Code:
 dig +trace +additional myname.asuscomm.com

; <<>> DiG 9.10.6 <<>> +trace +additional myname.asuscomm.com
;; global options: +cmd
.			402681	IN	NS	i.root-servers.net.
.			402681	IN	NS	m.root-servers.net.
.			402681	IN	NS	h.root-servers.net.
.			402681	IN	NS	e.root-servers.net.
.			402681	IN	NS	b.root-servers.net.
.			402681	IN	NS	d.root-servers.net.
.			402681	IN	NS	k.root-servers.net.
.			402681	IN	NS	f.root-servers.net.
.			402681	IN	NS	j.root-servers.net.
.			402681	IN	NS	c.root-servers.net.
.			402681	IN	NS	a.root-servers.net.
.			402681	IN	NS	g.root-servers.net.
.			402681	IN	NS	l.root-servers.net.
.			434820	IN	RRSIG	NS 8 0 518400 20211011170000 20210928160000 26838 . m3tJoQFhfGlQ8ShQao2SgWWeVUvSQjgYYOOeh8ZW3Yp40hkgEtc/vfAu UUywjfgZxUS+cnFNhR6/Na+bJkdPwOTWAcwG9hJ0EyHgXuB8WsVuYfz7 O3O+5rp0R0KgMwqr7XvWtnjrEZE0oNUJ0x5yTxYFEC/GpwwEv2PGO6Uz j216PvS46EmgrdhnriSsHWmpgoVEQocacvdum72TUhB1O+rKEBNeKigz Nb2vpiK/O3Q/6WRWdpeBGxPunuoPfBXzxktuf7YwhIvlR5epIqDdSI7u jYRjt+WtFg5dbcbuY2e/0pPVHPPNE7mMmPf6Kp5WQlIWlYvPOA2MaQaE mkFcyw==
;; Received 537 bytes from 66.253.214.16#53(66.253.214.16) in 3 ms

com.			172800	IN	NS	a.gtld-servers.net.
com.			172800	IN	NS	b.gtld-servers.net.
com.			172800	IN	NS	c.gtld-servers.net.
com.			172800	IN	NS	d.gtld-servers.net.
com.			172800	IN	NS	e.gtld-servers.net.
com.			172800	IN	NS	f.gtld-servers.net.
com.			172800	IN	NS	g.gtld-servers.net.
com.			172800	IN	NS	h.gtld-servers.net.
com.			172800	IN	NS	i.gtld-servers.net.
com.			172800	IN	NS	j.gtld-servers.net.
com.			172800	IN	NS	k.gtld-servers.net.
com.			172800	IN	NS	l.gtld-servers.net.
com.			172800	IN	NS	m.gtld-servers.net.
com.			86400	IN	DS	30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com.			86400	IN	RRSIG	DS 8 1 86400 20211012170000 20210929160000 26838 . M1Yhs89LAi3ydnaZmVzP/TkIf1RGlCM8lv5wqXV60Bm3WSCG9zDQdoif vj4WfY00I0FGJYjmaXgk57lHX/QGdABACWSnz7hN9RPCuKRMdAMC7pj1 H4ivxRKz26unnzPzXE41BKOcx4HtPVdF2Dc8EJIMl4C32ykYfutMmJdY 8zDWlII7U9Sdu9e3P6BhS9vzo4UxR/W5JCtgl3rML/dwEdEpVc/qE8mZ +P65jiYPbaYDZclnLJV7HgTvMMp3lmvVN3KnU1jqjbqIjAQks9tj7qob fJmPE8Y0kI5IBoqIBRTCBgkf2i1pQ92qo9kH3fGcOHbElMA+2NZLPXf/ GrXAnQ==
a.gtld-servers.net.	172800	IN	A	192.5.6.30
a.gtld-servers.net.	172800	IN	AAAA	2001:503:a83e::2:30
b.gtld-servers.net.	172800	IN	A	192.33.14.30
b.gtld-servers.net.	172800	IN	AAAA	2001:503:231d::2:30
c.gtld-servers.net.	172800	IN	A	192.26.92.30
c.gtld-servers.net.	172800	IN	AAAA	2001:503:83eb::30
d.gtld-servers.net.	172800	IN	A	192.31.80.30
d.gtld-servers.net.	172800	IN	AAAA	2001:500:856e::30
e.gtld-servers.net.	172800	IN	A	192.12.94.30
e.gtld-servers.net.	172800	IN	AAAA	2001:502:1ca1::30
f.gtld-servers.net.	172800	IN	A	192.35.51.30
f.gtld-servers.net.	172800	IN	AAAA	2001:503:d414::30
g.gtld-servers.net.	172800	IN	A	192.42.93.30
g.gtld-servers.net.	172800	IN	AAAA	2001:503:eea3::30
h.gtld-servers.net.	172800	IN	A	192.54.112.30
h.gtld-servers.net.	172800	IN	AAAA	2001:502:8cc::30
i.gtld-servers.net.	172800	IN	A	192.43.172.30
i.gtld-servers.net.	172800	IN	AAAA	2001:503:39c1::30
j.gtld-servers.net.	172800	IN	A	192.48.79.30
j.gtld-servers.net.	172800	IN	AAAA	2001:502:7094::30
k.gtld-servers.net.	172800	IN	A	192.52.178.30
k.gtld-servers.net.	172800	IN	AAAA	2001:503:d2d::30
l.gtld-servers.net.	172800	IN	A	192.41.162.30
l.gtld-servers.net.	172800	IN	AAAA	2001:500:d937::30
m.gtld-servers.net.	172800	IN	A	192.55.83.30
m.gtld-servers.net.	172800	IN	AAAA	2001:501:b1f9::30
;; Received 1179 bytes from 199.9.14.201#53(b.root-servers.net) in 31 ms

asuscomm.com.		172800	IN	NS	ns1.asuscomm.com.
asuscomm.com.		172800	IN	NS	ns2.asuscomm.com.
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A  NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20211003042352 20210926031352 39343 com. fdKztlvTFtfJm793/ER3F5+kzv7I1SUP3+JqqHCbk5HotOwsZeqzU4U4 DqkanSWZkzl2rC4qL8Q02oo6F53HSZgaVXEzCAcRRj2gRIlhCsL+0iQx X7SLPer7CVmSf1Fm9DL82E1Y4RBemd8K9+8xeRd+VoPA0x+0Z/afPO7B Em6wmLHmxBoYEdG6HAuWvLnNresmCnk8YvKPsc3wElk2yQ==
TN9880IANNUHQ1U2L5V50ELO3F6SIGB5.com. 86400 IN NSEC3 1 1 0 - TN9909T8N02F0KG2NTTI6OKMHCFHSMVF  NS DS RRSIG
TN9880IANNUHQ1U2L5V50ELO3F6SIGB5.com. 86400 IN RRSIG NSEC3 8 2 86400 20211003144128 20210926133128 39343 com. h/Ymto1R5ah1zrRcllKb8MOhYuVfBIOA6u5FftufDOOYfg6t4OaAi2Xm JJ3D5Spz5grkyw7Av2WzEJ1EfblPMMuFNDFQ3V9FRmeEOeQu6NFK8DDP L4RUQHfvSvCGClHBEdkCsaBZ7RnFgyO/I6X+bjXW8bJdUe+z8z0jfmgx JIG0Tifvvz5UM8Oun5c7HpX7KwDYOS8x/zmKQpRrT90grA==
ns1.asuscomm.com.	172800	IN	A	52.250.42.40
ns2.asuscomm.com.	172800	IN	A	52.250.42.40
;; Received 665 bytes from 2001:500:d937::30#53(l.gtld-servers.net) in 22 ms

myname.asuscomm.com.	120	IN	A	5.65.219.124
asuscomm.com.		86400	IN	NS	ns1.asuscomm.com.
ns1.asuscomm.com.	604800	IN	A	52.250.42.40
;; Received 87 bytes from 52.250.42.40#53(ns1.asuscomm.com) in 101 ms
 
Maybe you meant to say that the "yourname" part of the "yourname.myname.com" is a PQDN?
Thank you for the clarification — yes.

However, as fun as all of this is I do think we've gotten just a bit off track here. That is unless the point is that using isitdownorjust.me to verify up/down status is an invalid test if one doesn't use their myname.asuscomm.com v just asuscomm.com. If that's the point — OK.

It's still down even using myname.asuscomm.com, at least for me. So it appears YMMV however, that it is down substantially is still of concern. Again, I am guessing here, but since many of those here far longer than I appear to be having little or no trouble it seems the issues I am encountering may be somewhat isolated. That's good news, if correct. There is also the possibility I may have an issue in my setup, which is actually even better new because if that's the case it's something that I can, ultimately, address.
 
It's still down even using myname.asuscomm.com, at least for me. So it appears YMMV however, that it is down substantially is still of concern.
Is your webUI running at port 8443? If so, that would appear down every time. I don't think isitdownorjust.me checks for ports other than 80 or 443.
 
Is your webUI running at port 8443? If so, that would appear down every time. I don't think isitdownorjust.me checks for ports other than 80 or 443.
o_O Ah, I see. Oh, phooey!

Well if it's not asuscomm.com, that leaves me with my setup which worked but intermittently failed with increasing frequency until I changed DDNS providers and hardware and software (hmm, bunch of changes all at once, that never muddies the water) at which point it once again worked solidly and that addresses my end — or a failing piece of tech someplace along the internet normally routed from my usual confines.

But there's an at least as likely if not more probable culprit: the AiCloud 2.0 / iOS app. That's actually where it all started: not being able to properly move photos from phones to the LAN storage.

Oh double phooey!! Now I'm intrigued. That's awful! It always leads to poking and prodding which leads to changing source endpoint | AP route | route-intersect | endpoint by playing over something like cell service, then tracing, then engineers, phone calls, maps, illustrations, screen shots, field techs, etc., etc., and that's a real mess I've been through before and is a total time suck ad infinitum until "they" finally replace that old piece of junk that's been dead for ages and Bob told them to replace five years ago, then all is good again. Like PG&E handling communications, might as well be a hobby

Nope, not going there. No, no, no!

I got it fixed by changing DDNS/hardware/mobile apps and it works. That's my story and I'm sticking to it.

Sky falling
 
Just received bad news from my ISP. They will stop providing dynamic public IP and implement cgnat instead. :mad:

Look at the reason given:
For security purposes to avoid other intruders to identify public IPv4 assigned to the customers.
 
Just received bad news from my ISP. They will stop providing dynamic public IP and implement cgnat instead. :mad:

Look at the reason given:
For security purposes to avoid other intruders to identify public IPv4 assigned to the customers.
You have two options:
Get a VPS with public IP and run Zerotier on it.
Try to talk to your ISP. My ISP gave me public IP after I asked for it.
 
You have two options:
Get a VPS with public IP and run Zerotier on it.
Try to talk to your ISP. My ISP gave me public IP after I asked for it.
I have heard success story with another ISP, customers who complaint they cannot access their home CCTV are provided with public IP. Will see how it goes when they start implement it in the coming months. Apparently this only applies to lower/mid tier package. Those who pay premium for higher speed package are not affected.
 
Is it possible to use DDNS while the router is in AP mode? I'm just using freedns but I need to login every now and then to keep my account alive, which is a pain.
 
Hello
My ddns service constantly stopping working after one day just after updating to last fw version on my RT AC5300 ( 386.3_2) . When I switch off service and start it again it will work up to next ip change by provider. So it look like that updating mechanism is not working.
Anyone has same router behaviour?
If I do off that function and on it again my ip is updated in about 20 seconds or so. Up to next ip change.
 
Last edited:
Hello,

My IP resolves in DDNS, but when I use it for VPN I cannot connect. Works fine if I put the IP though.

Any ideals?
 
Hello,

My IP resolves in DDNS, but when I use it for VPN I cannot connect. Works fine if I put the IP though.

Any ideals?
Which VPN? OpenVPN works fine here as well as Instantguard.
 
After downgrade and upgrade again to last version of fm my rtac5300 started to update its ip automatically as should. Strange.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top