NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
SXR80 DDNS with No-IP
Hello, I'm trying to setup my new SXR80 Orbi router to work with DDNS using my existing No-IP.com account. I only need to fill in 3 fields: hostname, user, and password. I don't know what the hostna...
To follow up on this here is what's working for me.
There is no need to config DDNS in the router. Do not select the checkbox to us a DDNS service under the Advanced tab-->Advanced setup-->Dynamic DNS. Don't use it at all.
On the machine running the MAMP server
- do not use the Dynamic DNS service. Also, do not set any of the individual hosts to use DDNS.
- I am running no-ip's DUC which updates the IP address to all my hosts.
I used to have to access websites on my MAMP server from my desktop by using a DDNS hostname setup on no-ip. Though the host machine was on my local network it was a different IP address and afaik that was the only way to access it. The request for a website would go out, find no-ip, and then get routed back to the MAMP server. That worked well for several years. For some reason that stopped working and it was probably due to a software update.
I have installed MAMP's related app NAMO on the MAMP server. This lets me access all hosts from any machine on my local network including phones and tablets.
This has been working and it's a solution I'm happy with. So far.
duanemitchell wrote:
I heard from no-ip support and was instructed NOT to config DDNS on the router. Instead use their Dynamic Update Client (DUC). This runs in the background and can update all my no-ip hosts while the router only updates one.
For some reason I cannot access a no-ip host from within my local network. I always could. My server is on one machine and I try to hit a website on it using a no-ip host. The request goes out to no-ip and directs it back in and it gets routed to the webserver. Not working like that anymore but it does work if I use a VPN so it thinks its coming from a completely different part of the world.
For your use case with the multiple services on the MAMP host, no doubts. To me it looks like MAMP does include the DUC as a component anyway, thus I had put up that hint before already.
If you operate a VPN server on your router for accessing your home network from remote, the DDNS update with a dedicated hostname from the router is very appropriate.
Note: The fact MAMP does default to the port 8888/TCP instead of 443/TCP for https (resp. 80/TCP for http in case) is just a K.I.S.S. solution to avoid problems with routers and ISPs not allowing to use that port, and to avoid possible other services on the MAMP host are fighting for the standard ports. This and the port forwarding to 8888/TCP instead is unrelated to the DDNS name resolution and update part.
duanemitchell wrote:
For some reason I cannot access a no-ip host from within my local network. I always could. My server is on one machine and I try to hit a website on it using a no-ip host.
This reads to me like the Orbi Pro 6 AX system has a problem with the NAT loopback. BruceGuo please, your business.
duanemitchell wrote:
The request goes out to no-ip and directs it back in and it gets routed to the webserver. Not working like that anymore but it does work if I use a VPN so it thinks its coming from a completely different part of the world.
I don't think you are using a Web redirection on No-IP. Much more No-IP "just" serves the yourwww.domain.whatever host A DNS query and points to the router WAN IP address, from where the port requested by the client is forwarded. If you are acessing your MAMP hosted server from "out-there" but you can't from the LAN (with that same name resolving to the public IP) it's the NAT loopback issue. Covinced Netgear will look into this.
Just for the curiosity, is the MAMP host connected to the SXR80 router, a VLAN physically connected and configured to the SXR80, or is it probably connected to an SXS80 satellite?
So, I think we have rolled out the carpet with all possible causes. That's all I can do from here as just yet another community member for now.
Wish you a wonderful time!
Regards,
-Kurt
To follow up on this here is what's working for me.
There is no need to config DDNS in the router. Do not select the checkbox to us a DDNS service under the Advanced tab-->Advanced setup-->Dynamic DNS. Don't use it at all.
On the machine running the MAMP server
- do not use the Dynamic DNS service. Also, do not set any of the individual hosts to use DDNS.
- I am running no-ip's DUC which updates the IP address to all my hosts.
I used to have to access websites on my MAMP server from my desktop by using a DDNS hostname setup on no-ip. Though the host machine was on my local network it was a different IP address and afaik that was the only way to access it. The request for a website would go out, find no-ip, and then get routed back to the MAMP server. That worked well for several years. For some reason that stopped working and it was probably due to a software update.
I have installed MAMP's related app NAMO on the MAMP server. This lets me access all hosts from any machine on my local network including phones and tablets.
This has been working and it's a solution I'm happy with. So far.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
