Ausu RT-AC66U router, asus dynamic domain name system +IP cameras

[Dlan2]

I’m trying to set up remote monitoring for my home dlink camera.
On my router, I’ve set the ‘Enable the DDNS client” to yes. Entered name “DXXXX” and hit apply.
Asus nslookup shows ip address for DXXXX.asuscomm.com as 99.XXX.XX.XX so that seems to be correct. However ‘web redirect’ times out.
I’ve set ‘port forwarding’ to yes. Added to forward list, Cam1 – 8721 – 192.168.1.XX – 8721. Apply. This shows up in the listing. (I had already changed camera port to 8721)
I am able to access the camera on internet by using ‘current-IP:8721’. If I understand all this correctly, I should be able to also access by using DXXXX.asuscomm.com:8721. But it doesn’t work, just times out.
What am I missing, or am I just I doing something wrong?

 

[kanewolf]

It sounds like the DNS isn't working. IF you just created the DDNS entry, it may take up to a day to propagate to the DNS server you are currently using.

 

[Dlan2]

This was set up 3 days ago. Thought tha may be the problem at first, could it take longer than 3 days?

 

[kanewolf]

Can you ping the URL for your DDNS?

 

[Dlan2]

Just tried to ping dXXXX.asuscomm.com, timed out.
------------------------------

Would the settings

Wan IP setting
'Connect to DNS Server automatically = Yes

'WAN DNS Setting'
Connect to DNS Server automatically = 'No'
DNS server1 '8.8.8.8
DNS server2 '8.8.4.4

be correct and would that have any thing to do with this?

 

[kanewolf]

Does this website resolve your address correctly -- http://iplookup.asus.com/nslookup.php


Also read through this thread -- https://www.snbforums.com/threads/asus-dynamic-dns-myhost-asuscomm-com-problem.17016/

 

[Dlan2]

I had answered that earlier, but here it is again.

Asus nslookup shows ip address for DXXXX.asuscomm.com as 99.XXX.XX.XX so that seems to be correct. However ‘web redirect’ times out.
------------------------
I have spent the last 4 or 5 days reading and trying to learn about this and then trying to understand why I can't get it to work. Today I came to the conclusion that I have to ask someone with more experience.

 

[kanewolf]

Sorry, I use dyndns (the $20 is worth it to me) so I don't have anything specific to your DDNS issue.

 

[BuddhaSkoota]

I’m trying to set up remote monitoring for my home dlink camera.
On my router, I’ve set the ‘Enable the DDNS client” to yes. Entered name “DXXXX” and hit apply.
Asus nslookup shows ip address for DXXXX.asuscomm.com as 99.XXX.XX.XX so that seems to be correct. However ‘web redirect’ times out.
I’ve set ‘port forwarding’ to yes. Added to forward list, Cam1 – 8721 – 192.168.1.XX – 8721. Apply. This shows up in the listing. (I had already changed camera port to 8721)
I am able to access the camera on internet by using ‘current-IP:8721’. If I understand all this correctly, I should be able to also access by using DXXXX.asuscomm.com:8721. But it doesn’t work, just times out.
What am I missing, or am I just I doing something wrong?

Instead of using the Asus nslookup, perform an nslookup from a command prompt.

nslookup DXXXX.asuscomm.com

It's not clear from your post, but does the IP address from the nslookup match the WAN IP address of your router?

 

[Dlan2]

no they are different..

nslookup DXXXX.asuscomm.com reports:
Name: DXXXX.asuscomm.com
Address: 99.XX.XXX.XX (the same as the asus lookup)

Router - Internet status:
Connected
WAN IP: 65.XX.XX.XX
DDNS: DXXXX.asuscomm.com

This is the last page of the router log if that helps any,

Jul 31 20:00:35 ddns update: ez-ipupdate: starting...
Jul 31 20:00:35 miniupnpd[631]: version 1.9 started
Jul 31 20:00:35 miniupnpd[631]: HTTP listening on port 40590
Jul 31 20:00:35 miniupnpd[631]: Listening for NAT-PMP/PCP traffic on port 5351
Jul 31 20:00:35 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 80.
Jul 31 20:00:38 ddns update: Asus update entry:: return: HTTP/1.1 203 |dlan.asuscomm.com|dlan4037.asuscomm.com^M Date: Fri, 16 Jun 2017 22:56:31 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Content-Type: text/html; charset=UTF-8^M ^M
Jul 31 20:00:38 ddns update: retval= 1, ddns_return_code (,203)
Jul 31 20:00:38 ddns update: asusddns_update: 1
Jul 31 20:00:38 ntp: start NTP update
Jun 16 18:56:34 rc_service: ntp 637:notify_rc restart_upnp
Jun 16 18:56:34 miniupnpd[631]: shutting down MiniUPnPd
Jun 16 18:56:34 rc_service: ntp 637:notify_rc restart_diskmon
Jun 16 18:56:34 disk_monitor: Finish
Jun 16 18:56:34 miniupnpd[653]: version 1.9 started
Jun 16 18:56:34 miniupnpd[653]: HTTP listening on port 50045
Jun 16 18:56:34 miniupnpd[653]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 16 18:56:34 disk monitor: be idle
Jun 16 18:56:40 rc_service: zcip 668:notify_rc start_firewall
Jun 16 18:56:40 zcip client: configured 169.254.53.128
Jun 16 18:56:40 miniupnpd[653]: shutting down MiniUPnPd
Jun 16 18:56:40 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jun 16 18:56:40 miniupnpd[692]: version 1.9 started
Jun 16 18:56:40 miniupnpd[692]: HTTP listening on port 53313
Jun 16 18:56:40 miniupnpd[692]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 16 18:56:57 crond[320]: time disparity of 987776 minutes detected
Jun 16 19:00:34 disk_monitor: Got SIGALRM...


C:\WINDOWS\system32>

 

[BuddhaSkoota]

no they are different..

nslookup DXXXX.asuscomm.com reports:
Name: DXXXX.asuscomm.com
Address: 99.XX.XXX.XX (the same as the asus lookup)

Router - Internet status:
Connected
WAN IP: 65.XX.XX.XX
DDNS: DXXXX.asuscomm.com

The problem is that the subdomain DXXXX is pointing to a different address than your given public IP of 65.x.x.x. It's possible that DXXXX is already registered to someone else.

I'm not sure what sort of registration process is used by the Asus DDNS, but it could be that it doesn't notify you properly of existing names that can't be used.

You might consider using one of the other DDNS services. I personally use NoIP.com, which is free and has worked well for me. You would get a domain name of DXXXX.ddns.net, and get a notifier to verify it once a month. Of course there are other services available depending on your needs/wishes.

edit for grammar

 

[Ralston18]

Question about those early router log entry dates -- July?

The router log sort of reads as if there was a time update made and I see a reference to GMT

And I see some "time disparity detection" in the second to last log entry.

Is there some sort of clock or time zone error that is timing out the "lookup" process?

Network Time Protocols.....?

And it was mentioned that the process can take some time to propagate.

Going out of my comfort zone but curious and wondering....

 

[Dlan2]

Thanks for your help. Guess i'll take a look at NOip. Checking a box in the router just seemed like such an easy method.

*I saw that date thing also, no clue....