NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Dynamic DNS updating IP address that doesn't match router's IP
This may have been answered elsewhere but I couldn't find a similar question. I'm not talking about NAT here. I understand my devices have different IP addresses that are issued out by the router (...
Yes, there two layers of NAT, one by your router and one by the ISP. And, yes, that means that Dynamic DNS won't work. One way to work around that is to connect your home server to a VPN provider.
You would have to check with your ISP about the nature of your IPv6 address. If it's fairly stable, then there are Dynamic DNS providers out there that support IPv6.
You may think you are not talking about NAT, but your situation actually involves NAT. Your ISP is doing Carrier Grade NAT. :smileysurprised:
You may be wondering, "Why is my ISP doing NAT?" You see, there are actually no more public IPv4 addresses available. Unfortunately, your ISP doesn't have enough public addresses to give one to every customer, so they have to resort to using NAT. Your ISP actually posted about this in their blog (link).
IP address 100.65.140.24 belongs to subnet 100.64.0.0/10, which is a private address range set aside for ISPs to perform Carrier Grade NAT (CGN). See IETF RFC 6598 (link). Your ISP assigned it to your router but it is not a public IP address.
IP address 199.87.86.198 is a public IP address. Technically, it doesn't belong to you. Rather, it's shared by you and everyone else in your ISP's NAT domain.
The one mystery is why you can connect to your home server using 100.65.140.24. 100.65.140.24 is not reachable from the Internet. One possibility is that you are accessing it from somewhere else inside your ISP's NAT domain, like a neighbor's place who also has the same ISP.
Moving to IPv6 will certainly get you out of the CGN mess.
Hope this helps.
Hey Ether,
Thanks a bunch for the reply. I sorta get the reason for NAT and I thought I at least understood it at my router level. It sounds sorta like there is just another level at my ISP... or something like that.
I also see what you're saying about it being unreachable. I think its working as you'd expect. What confused me was that when seeing my private address as the IP target in my noip configuration then my port was reachable - but you're right, it's only on my network.
So this makes more sense now. But does that mean that given my ISPs setup I can't use a dynamic dns service like No-IP?
My IPv6 address isn't static, right? Is there a way to configure a no-ip/like solution with IPv6? On No-IP i see a AAAA type but it requires be to give both a IPv4 and IPv6 address. I tried it and when the updates happen it still changes the IP target to my public IP which as we discussed can't be routed to my particular network/port.
Any ideas? Long story short, I'm just trying to set up a dynamic dns mapping to my home server. Thanks again!
Yes, there two layers of NAT, one by your router and one by the ISP. And, yes, that means that Dynamic DNS won't work. One way to work around that is to connect your home server to a VPN provider.
You would have to check with your ISP about the nature of your IPv6 address. If it's fairly stable, then there are Dynamic DNS providers out there that support IPv6.