Forum Moderators: phranque

Message Too Old, No Replies

Router DMZ

Setting up DNS server with router: which IP do I use!?

         

nnjersey0

8:56 pm on Jul 10, 2004 (gmt 0)

10+ Year Member



i know my ISP blocks port 80, so im using port 69.
i setup apache as folowed:

Port 69
ServerName taxii.mine.nu

taxii.mine.nu is the dns address registered at dyndns.org

because im using a router, im very confused on which ip to use when setting up the dns address...

Network Connection Details [img30.photobucket.com]

...i wish i knew what i was doing.

gergoe

11:29 pm on Jul 10, 2004 (gmt 0)

10+ Year Member



I really don't know much about these dynamic dns things - like dyndns, but I can tell you what you need to use where;

In the apache configuration you need to specify your local ip address (for example 192.168.0.1) for the BindAddress, the port can be anything (in the case if you can turn the port in your incomming requests on your router to something else), so i sugegst you to use the default one.
An alternative is that you don't specify BindAddress nor Listen, only Port, then apache will be listening on every ip address on the given port. The ServerName (if you really want to configure one) can be the hostname you are about to use on the internet and which is pinting to your server, but it is rather useless to configure any if you want to host only one site.

In your router you need to open the port 69 (by the way I don't recommend using such a low port, I'd use 8080 or 8000 instead) and forward it to the ip address of your apache (the 192.168.x.x liek ip address), and if you configured the apache to listen on the default port, then you need to configure that also on the router (if you can; otherwise change the port on the apache to 69 or whatever you decided to use).

In the dns records (I really don't know how it is working with dyndns, so don't ask specific questions) you must have the ip address of your internet connection defined (should not be 127.0.0.1, 10.x.x.x, 172.16.x.x or 192.168.x.x but can be anything else). Additionally you can create CNAME (cannocial name) records in the zones (domain name records) which refers to a hostname, not to an ip address, so you can have it pointing to any dynamically updated hostname (like dyndns).

nnjersey0

4:49 am on Jul 11, 2004 (gmt 0)

10+ Year Member



i set it up like you told me to.

+ apache is set to port 8080
+ dyndns is set up to the ip addy of my internet connection.
+ port 8080 is being forwarded through my router:
In.Ports: 8080-8080
Destination IP: 192.168.2.1
Destination Port: 8080-8080

i got a friend to test out [taxii.mine.nu...]
PAGE CONNOT BE DISPLAYED
so i thought maybe [taxii.mine.nu:8080...]
still nothing
i try it, and i get the popup for username and password to enter the configuration pages for my router.

bleh.
::frustraited:

rlkanter

5:56 am on Jul 11, 2004 (gmt 0)

10+ Year Member



You have to narrow down where the problem is.

Try to connect to the webpage from the hosting machine, on port 8080. Generally this is localhost:8080.

Next try to connect to it from another machine on your LAN, if you can't do this you can try using the local LAN ip, but it there is a firewall problem on the hosting machine, you won't be able to debug this properly without this step.

If both of these steps work, make sure you have your WAN ip address correct in dyndns. You can check it by going to [whatsmyip.org...]

This will report your WAN ip address.

Now try to ping your domain name, even if you don't have pings going through, it should still show the ip address it's trying to ping. That IP should match your WAN ip.

If all this works, then re-check the port forwarding, make sure it's really mapping port 8080 to the correct LAN ip address.

Good luck.

gergoe

2:09 pm on Jul 11, 2004 (gmt 0)

10+ Year Member



Since your ISP blocking port 80 you can not use h**p://taxii.mine.nu (because then the default port is used, which is 80), only h**p://taxii.mine.nu:8080. If you got the login screen of your router when you type this url then it means that the web interface of your router is listening on the same port (and also that it is open to the internet which is a security risk by the way). Either try to change the port of the http interface of the router, or disable the access from the internet or change the 8080 port (in apache, and in the router's port forwarding settings) to something else, like 8000 or 8888.