Weird IP being updated

If you email me with your username from the email address you have on file, I can redirect your request to the appropriate people.

Mike

Community Manager, Dyn

Is the WAN IP of your D-Link by any chance 10.102.100.76? Many hardware clients blindly update with their WAN IP.

If you have any paid services you can ask DynDNS. Otherwise your only option is to identify if you have any device with that IP address or change the password on your account and then update just the one update client.

And no my WAN IP is definitely not 10.102.100.76 - that would be impossible wouldn't it? My actual wan IP starts with 95.xxxxxxxxxx.

That wouldn't at all be impossible. Is the 95. address what is shown in the management screen of your DSL-2641R?

I've checked and now after I've manually updated my IP to my real external IP at http://account.dyn.com it seems the real IP is staying. We'll see for how long... :)

I'd expect until your mystery device updates your hostname, at which point anything you get working will break...

I've got another question in the meantime: I've forwarded a port on my router and I can do a succesful

telnet mydyndnshostname portnumber

from another network, but the same telnet is unsuccesful when done from the same network. It's as if the routing was wrong. Ping resolves to the correct IP but telnet on the specified port doesn't work when tried from the same machine the port is being forwarded from.

That's to be expected, few low end routers support what's known as NAT reflection (or loopback). From within the network you need to use the LAN IP, or replace your router with one that supports NAT reflection.

The 95. address is what's shown at http://www.whatismyip.com as well as at http://account.dyn.com where it suggests your IP to replace the currently assigned one (I guess it uses a similar lookup service).

However that doesn't answer the question. We absolutely need to know what the IP shown on the management pages of your modem/router. What web sites display can be completely wrong.

AFAIK 10.xx address space is reserved for internal networks, that's why I thought it'd be impossible to have this sort of address as my public IP?

Ah, you're confusing a WAN IP and a public IP. The WAN IP is simply the ISP allocated IP address. It can be any IP the ISP chooses to use, and some chose to allocate RFC 1918 IP addresses. That is why we keep asking for the WAN IP shown in the router or modem's management pages, not what's shown by any web site.

There is a community maintained list of known well behaved routers and other update clients.

I am using a free service so not sure how much help I can get by sending my email address to you Mike.

And no my WAN IP is definitely not 10.102.100.76 - that would be impossible wouldn't it? My actual wan IP starts with 95.xxxxxxxxxx.

I've checked and now after I've manually updated my IP to my real external IP at http://account.dyn.com it seems the real IP is staying. We'll see for how long... :)

I've got another question in the meantime: I've forwarded a port on my router and I can do a succesful

telnet mydyndnshostname portnumber

from another network, but the same telnet is unsuccesful when done from the same network. It's as if the routing was wrong. Ping resolves to the correct IP but telnet on the specified port doesn't work when tried from the same machine the port is being forwarded from.

Am I doing something wrong?

The 95.* address is what's shown at http://www.whatismyip.com as well as at http://account.dyn.com where it suggests your IP to replace the currently assigned one (I guess it uses a similar lookup service).

Forget about anything you see at a website. (And no, this is not a lookup service, but a simple server script using your HTTP header.) This shows only what the internet sees from you where you are coming from and not where you have to go. I.e. it does not show you the way back, how to reach your network from outside.

The only place to see your WAN IP address is your internet facing side of the router or modem, whatever is outer. So check that status page for your WAN IP address. And if it is one from the RFC-1918 private ranges, then your ISP assigns you a private IP address, and you cannot reach your network from outside with this ISP product. Full Stop.

AFAIK 10.xx address space is reserved for internal networks, that's why I thought it'd be impossible to have this sort of address as my public IP?

Sure, especially mobile connections (3G etc) use private IP addresses.

Edit:

Yes the WAN interface in the router is showing 95.* as well.

Then the DDNS update client in your router is badly behaving.