Trying to get my DNS to work using ISPConfig

[petersfreeman]

Goal

I want to run a web server and a mail server and need to have them reachable from the Internet.

Progress

I have registered my domain with Hover (Tucows)

I have the mail server working for users on my LAN, we can send and receive mail to each other with email addresses such as peter@musgravelanding.net and mary@musgravelanding.net.

Within the LAN, this only works if we use 192.168.241.80 as the server name in Thunderbird as the address to the POP Mail Server. If I use mail.musgravelanding.net, it fails. Likewise, for the outgoing server in Thunderbird, to reach the SMTP Mail Server, I have to use 192.168.241.80 instead of mail.musgravelanding.net

I went to my account on Hover (https://www.hover.com/domain/musgravelanding.net) and forwarded the domain to my WAN ip address (25.95.xxx.xxxx), used the NAT on the first router connected to my ISP (at my home) to forward port 80, 25 and 110 to my second router, which in turn has these ports open and forwards them to my server at 192.168.241.80.

I get some indication that packets are able to get to the server now, since now when I use my browser within my LAN with the address www.musgravelanding.net, it loads up the login screen for the internal web server on my router even though the router said that it would switch its port to 8080.

If I get someone from outside my LAN and out on the Internet to use their browser to use www.musgravelanding.net, nothing comes up. This is probably because my router connected to my ISP is trying to connect it to its internal web service which will not allow remote management.

That is another problem I have to solve.

When I change the thunderbird setup from 192.168.241.80 to mail.musgravelanding.net, and try to get mail sent from the Internet, I get from Thunderbird: Sending of password did not succeed. Mail server mail.musgravelanding.net responded: Invalid

It is possible that the router connected to my ISP is not properly forwarding requests to my second router.

1. Can anyone help me with this?
2. What tests can I do to find out what is happening?

Thanks,

Peter

[falko]

So you use two routers? Do both routers use different subnets, or are both in the same subnet?

[petersfreeman]

Originally Posted by falko

So you use two routers? Do both routers use different subnets, or are both in the same subnet?

Yes, I get access to the Internet wirelessly through a Rogers Rocket Hub (Netcomm 3G HSPA WiFi Router) that was supplied by my ISP. On the internet side, it has an actual IPAddress of 25.95.xxx.xxx, however my ISP connection has no reverse DNS, so when finding the IPAddress from the Internet it shows as 74.198.151.59.

I assume that I will have to approach my ISP and ask for a public IPAddress?

Regardless, I have setup my Domain forwarding using the 25.95.xxx.xxx address to test the system first.

This Netcomm Router creates a LAN on the 192.168.1.x subnet (255.255.255.0 mask). For extra security, my own LAN sits behind a Cisco Business Router where I have created a LAN using 192.168.241.x (255.255.255.0 mask). My server sits on this LAN with address 192.168.241.80.

From the viewpoint of the Netcomm Router, I have setup the Cisco Router to have a fixed address of 192.168.1.241. I have opened ports 80, 25 and 110 on both the Cisco Router and the Netcomm Router.

Tracing the route, outgoing packets from the server start at 192.168.241.80, go to the gateway part of the Cisco Router at 192.168.241.1 on one side, then 192.168.1.241 on the other side. From there they go to the gateway part of the Netcomm Router at 192.168.1.1 one one side, then 25.95.xxx.xxx on the other side and then out on to the Internet.

When I set the port on the Rocket Hub for HTTP traffic, I see the first screen. When I click apply/save I get the dialog box telling me that it is moving the port for the Netcomm Router's internal web server from 80 to 8080 (See attachments).

I would expect that it is moving the Netcomm Router's internal web server aside so incoming HTTP traffice would be forwarded through to 192.168.1.241.

Any clues?

Thanks Falko