no-ip.com

azwethinkweiz · 2007-06-15 00:39:56

Ok...I set up an account with no-ip.com. Got my URL and got everything setup on my machine. However when I go to the URL from my machine it goes to the address for my router. Its only on mine because Im internal. Others have tried it and said it works fine for them. Any ideas?

Acid7711 · 2007-06-15 04:36:32

Forward port 80 on your router to your computer's local ip??

cactus · 2007-06-15 06:32:13

I think he means it goes out, and comes back in. Some little home routers puke on that.
Easy solution is to add an entry for that domain to your /etc/hosts file, and put in your *internal* ip address of that *webserver* machine, and use the *external* *domain name* that you have set up for no-ip. Then you will be able to access it by name, just as if you were from outside...but you will be inside.

127.0.0.1       localhost.localdomain  localhost 
192.168.100.10  mysweetbox.no-ip.com

azwethinkweiz · 2007-06-15 08:23:32

Heres what I have in /etc/hosts

# /etc/hosts: static lookup table for host names
#

#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost
192.168.0.10 taintedtux.sytes.net
# End of file

However now my issue is when I go to the url I get the Apache test page...and when other people go to the URL they get directed to my router. Im not sure if I have that file right...but Ive tried several differant ways and none work right so far.

Oh yes and as for port 80 it IS forwarded to the router and my ISP doesnt block port 80 because if that were the case other people wouldnt have been able to access the page before...correct? Heh which they cant now and either can I. 192.168.0.10 is the internal address I get when I run ifconfig -a so that is what I should be using right. Some people have said that that cant be my internal IP but theyre wrong because I set it up with a buddy of mine that way as a static IP Im not using dhcp.

Last edited by azwethinkweiz (2007-06-15 08:27:51)

mitsoko · 2007-06-15 08:42:45

there appears to be a misconfiguration on your router ... I visited the url and I get your router login.

you need to forward, from your router all requests for port 80 to your LAN machine 192.168.0.10.

your machine would be just listening for incoming requests on port 80 as usual, no change needs to take place there.

azwethinkweiz · 2007-06-15 09:05:29

well Im using the actiontec gt701-wg modem provided by Qwest which in my opinion is a piece of garbage. However its what Ive got. And being still pretty new to all this Im not really sure how to forward the port 80 traffic to my ip...especially on this modem. It seems very weird to configure in my opinion. But I also dont see why I need to forward it if it is not blocked by my ISP, as alot of ISP's do block port 80. However you very well may be right and Im willing to try it, especially seeing as Ive been screwing with this all day...again Im just not sure where to go or how to do it on this modem. Another thing that confuses me is why am I getting the apache test page now rather than my modem config...and everyone else is getting my modem now?? However the info from cactus was the same suggestion made in the FAQ section of no-ip.com.

slackhack · 2007-06-15 13:29:46

PDF, sorry:

http://www.qwest.com/internethelp/modem … 906msl.pdf

cactus · 2007-06-15 15:54:13

azwethinkweiz, I think there was some confusion about which name goes in the /etc/hosts file.

On the machine you are using as your client.. what is the ip address..
On the machine you are using as your internal webserver, what is the ip address...
And.. What is the no-ip domain that you are using.

Then... on the *client machine*, you need your hosts file to look like..

Lets use an example

Lets say I have two machines on my network. ClientA, and ServerB.
Lets say the domain name people use outside of my network to access my webserver is cactus.no-ip.com
Let us also say that everything is working for people not on my local network.

For this example, assume the following.
ClientA's ip address is 192.168.1.20
ServerB's ip address is 192.168.1.10
ServerB's external name is cactus.no-ip.com

For the /etc/hosts file on ClientA I would have...

127.0.0.1 localhost.localdomain localhost
192.168.1.20 clienta
192.168.1.10 cactus.no-ip.com

Then you would open a web browser on clientA, and type cactus.no-ip.com in the address bar.

Acid7711 · 2007-06-15 17:29:20

Actually, just for reference, i had port 80 forwarded on my router, and it still wouldn't properly forward to the computer, simply because the router's own http access page was what kept showing up. I had to actually disable that page for it to forward properly, but that was on the old router. My new router was going slow until I completely changed the firmware on it.

Maybe I'm way off, just shooting off ideas from what's personally happened to me.

Just for reference, this does work for me on my server:

127.0.0.1       localhost.localdomain localhost
192.168.0.122   server.maxthrottle.com  server

Last edited by Acid7711 (2007-06-15 17:31:10)

azwethinkweiz · 2007-06-15 23:24:01

Got it! thanks alot

Arch Linux

#1 2007-06-15 00:39:56

no-ip.com

#2 2007-06-15 04:36:32

Re: no-ip.com

#3 2007-06-15 06:32:13

Re: no-ip.com

#4 2007-06-15 08:23:32

Re: no-ip.com

#5 2007-06-15 08:42:45

Re: no-ip.com

#6 2007-06-15 09:05:29

Re: no-ip.com

#7 2007-06-15 13:29:46

Re: no-ip.com

#8 2007-06-15 15:54:13

Re: no-ip.com

#9 2007-06-15 17:29:20

Re: no-ip.com

#10 2007-06-15 23:24:01

Re: no-ip.com

Board footer