DynDNS

[shadowbeckoner]

I have a basic HFS page up and running at my ip address, but I'm not entirely sure how to make it accessible from a DNS hostname.  Specifically, the address that I tried to make it was thatguy.doesntexist.com.  I know that portforwarding is working correctly, because I followed everything from the website, and my firewall was off when I tried to access it.  If it helps, the ip address that it should be taking it from is 207.255.229.230, and I'm using DynDNS.com.  Any help would be greatly appreciated, as I'm trying to learn about this kind of stuff but don't really have any prior experience.

[bacter]

First, use the selftest from HFS (the first option in the menu). If selftest returns ok, your friends should be able to access yous server using your ip typing http://207.255.229.230:portYouUse/.

If you have a domain with DynDNS, then you have 3 ways to update your domainname with your current IP:
1. In the router (not all models do support this option).
2. Using the small programa DynDNSupdater form DynDNS
3. Using HFS (main menu:-> Dynamic DNS updater --> DynDNS wizard.)

Whatever method you choose, DynDNS will update the nameserver with your current external IP when it changes and people may access you server typing http://thatguy.doesntexist.com:portYouUse/.

Note that you can NOT access yourself using the domainname nor your external ip ! To see your page use your local ip or http://localhost:port

[parade]

Note that you can NOT access yourself using the domainname nor your external ip !

I do it all the time.

[Unknown8063]

Note that you can NOT access yourself using the domainname nor your external ip !

I do it all the time.

Same here.  I've never understood the concept of not being able to access your own machine via the external IP.

[Foggy]

The concept behind not being able to access locally via the external ip is quite simple.

The external ip is the ip of the router/modem and any requests it gets are simply forwards following the port forwarding rules you have set, and this works fine for external users but not for internal users because the router sees you are on the local network and thinks you are trying to access it. Although I believe it is possible with some routers/modems to use the external ip locally when not using the port of the web interface.

[parade]

The external ip is the ip of the router/modem and any requests it gets are simply forwards following the port forwarding rules you have set, and this works fine for external users but not for internal users because the router sees you are on the local network and thinks you are trying to access it. Although I believe it is possible with some routers/modems to use the external ip locally when not using the port of the web interface.

I am not quite sure, what you mean with "Web-Interface". Do you mean the web-interface of the router? My router uses port 80.

What you are telling is, that the router does'nt care about the forwarding rules for port 80 if you try to access your HFS adressing the external IP or domain-name.
I had several routers for home-use and I never had one that did not forward local requests via domain or external ip on port 80 and direct them to my http-server.

[bacter]

Checked access with external ip to yourself with two ISProviders and three routers. I'm not sure why it doesn't work,  but I think ISProvider will drop packets with sourceIP=destinationIP, what is naturally a nonsense.

Would be interesting a traceroute where you can access yourself with external ip!

[parade]

Would be interesting a traceroute where you can access yourself with external ip!

I am pretty sure, that it is not a real external access. I think that my router redirects directly to my internal IP.
So there is only one line in tracert: my external IP

But that was not the question.
I answered because you wrote:
"Note that you can NOT access yourself using the domainname nor your external ip !"

[troglo]

Another question:
Should I able to see my files through the myname.dyndns.org:3393 command?
Or does the self test through  207.210.215.90 work differently?
Troglo

[bacter]

Troglo:

It's not another question, it's the same. As you can deduce from what parade and I wrote above, it's not clear if router or isp does allow or not that you access from your lan to your lan with external ip or domainname. So just try to see if you can.

In either case, what you will see on your screen with the selftest is exaclty the same as you would see from outside of your lan using your domainname or address.

[shadowbeckoner]

Well, it is working now...in a sense.  I can access it from thatguy.doesntexist.com from my computer and from other computers I've tried.  Oddly enough, though, it seems like after HFS has been running for a day or so the site is no longer accessible even after I use the DNS updater.  I wait for a while, close the program, restart my computer, and restart HFS and it works perfectly for about another day.  What's happening?

Also, I wanted to know if anyone knew if it would be easy to edit the template with code generated from FrontPage or Dreamweaver.

[bacter]

it seems like after HFS has been running for a day or so the site is no longer accessible even after I use the DNS updater

1. Does HFS work?   --> Open in browser
2. What external IP does HFS show? Is this the actual IP ?
3. Did your IP change while HFS was running?

To change your template you need some knowledge of html. You can't edit it with a wysiwyg-editor, but you can paste some code generated with them into a suitable place of your template - if you know what you do!

[rejetto]

1. use the self test to know if HFS is working
2. go to this site and see if your dns address is actually pointing to your external address