Network / Domain Guru's a ?

[Thadeus]

Being a 4th year networking major I am rather disapointed that I have not figured out the cause for this yet, but I am still searching and don't have a ton of experiance handling domains.

here is the problem

I registered a domain name with godaddy.com

mysite.com

on my account on godaddy I have mysite.com forwarding to "mysite.dyndns.net" which I registered over at dnydns.org

mysite.dyndns.net then forwards to the IP from my cable company at my tiny apartment.

I am having a break in portforwarding between mysite.com and mysite.dyndns.net

For example if I setup everything to VNC into one of my servers for instance on say port 1111 (and lets say my current IP from my cable company was 1.1.1.1)

in that case when I try to VNC via 1.1.1.1:1111 (that is IP address 1.1.1.1 port 1111) It works!

So I know everything on my end is correct.

if I try it via mysite.dyndns.net:1111 That ALSO works

however trying it via mysite.com:1111 fails

Only HTTP (port 80 traffic) seems to forward correctly via the mysite.com to mysite.dyndns.net link.

Anyone ever seen a similar issue?

We seemed to have a plethra of uber geeks around here so thought I'd toss it out there.

[Paws]

Originally Posted by Thadeus

mysite.dyndns.net then forwards to the IP from my cable company at my tiny apartment.

You're hosting the pages on your home computer/server? If so contact your ISP and ensure ports necessary for this aren't blocked. Here in Australia they're blocked by default and ya need to either contact them to turn the blocking off or do so by logging into their website.

May be the same issue, may be something else entirely. Just throwing it out there since it's what has happened to me before.

[Lindline]

Are you utilizing 'www.' in front of any of those? It may seem like it would assume it but a lot of times you need to specify 'www.' or not.

[Thadeus]

Originally Posted by Paws

You're hosting the pages on your home computer/server? If so contact your ISP and ensure ports necessary for this aren't blocked. Here in Australia they're blocked by default and ya need to either contact them to turn the blocking off or do so by logging into their website.

May be the same issue, may be something else entirely. Just throwing it out there since it's what has happened to me before.

Thanks for the tip but I have ruled that out if that was the case accessing the various services directly by the external IP would not work either.

It seems to be an issue with the "link" between mysite.com and the domain it is forwarded to mysite.dyndns.net

[Thadeus]

Originally Posted by Lindline

Are you utilizing 'www.' in front of any of those? It may seem like it would assume it but a lot of times you need to specify 'www.' or not.

Unfortunately that not it either but thanks for the thought. Port 80 (aka HTTP aka web traffic) is the only port that does work no other ports seem to be forwarded.

[p0weruser]

I know it semantics but what OS are you running, if it's Linux I'm more familiar and might be able to help.

[Tim]

Your first bet is to telnet to the IP address of your public facing address that is serving the website, on port 80 (web port), from the outside, disinterested internet.

Next, do a nslookup and use a reliable dns server, such as 8.8.8.8 (type server 8.8.8.8) and then type in your domain. It should resolve to your public facing IP.

If the above 2 things are successful, then you've ruled out DNS and IP access to your system, and the rest would be internal to you.

Cheers

1 more quick note: Dynamic DNS is inherently not ultra reliable due to DNS cache updates when IP addresses change. Just keep that in mind.

[Thadeus]

Originally Posted by p0weruser

I know it semantics but what OS are you running, if it's Linux I'm more familiar and might be able to help.

What OS am I running on what? Unless you are talking about a local issue on the machines I am sitting at for my testing that should be completely irrelevant. But for the sake of argument I have done the above tests, from linux, windows xp, windows 7, and Android 2.1 on my phone.

[Thadeus]

Originally Posted by Tim

Your first bet is to telnet to the IP address of your public facing address that is serving the website, on port 80 (web port), from the outside, disinterested internet.

Next, do a nslookup and use a reliable dns server, such as 8.8.8.8 (type server 8.8.8.8) and then type in your domain. It should resolve to your public facing IP.

If the above 2 things are successful, then you've ruled out DNS and IP access to your system, and the rest would be internal to you.

Cheers

1 more quick note: Dynamic DNS is inherently not ultra reliable due to DNS cache updates when IP addresses change. Just keep that in mind.

I see where you are coming from but the problem actually isnt with Dynamic DNS. If it was I could understand.

mysite.dyndns.net forwards correctly to my external IP address of my router at my apartment correctly on ALL ports (well clearly I havent testing them "all" but 80, 21, 3389, 6060, ect ect ect ect ect all work, I just changed the external port of my forwarding entery for remote desktop to test this.)

For example in my "Router" (running pfsense) I have

Port Forwarding

External IP on port 1234 forward to IP of my desktop (local network) on port 3389

I am then able to remote desktop to my external IP on port 1234 and remote desktop to my desktop PC. If I change the external port number it still works.

If instead of doing it by IP address if I use my dyndns.org entery mysite.dyndns.net:1234 it still works

but if I do it via mysite.com (which is set to forward to mysite.dyndns.net via godaddy.com's account settings) it ONLY works if I use port 80.

Its just bizarre, I am trying to get a hold of godaddy but guess I'll see if they respond.

[ejt]

Have you tried accessing the domain from outside of the network?

I had alot of problems befor with not being able to reach my domain from within the network my server was, then I had to go via my IP-address.