Have you forwarded port 80 on your router to your ispconfig server? Is mydomainname.dom pointing to your external IP address?

Click to expand...

Yes to your first question. NAPT is by default forwarding everything to my server where the ISPConfig firewall takes care of business.

As to the second question I'm not sure if I understand correctly. When I check DNS www.mydomainname.dom is forwarded to my external IP which is the router. NAPT then takes care of business in forwarding to the internal IP.

In another thread I raised the issue of not being able to connect to https://www.mydomainname.dom:81 from LAN. As suggested I changed this in a file to my.internal.IP.x:81. Which works.

But what if I want to host the regular website http://www.mydomainname.dom as well? http://www.mydomainname.dom errors out (from inside my LAN) and when I use the IP address I get the error page telling me that I'm looking at a shared IP address and that I should use the full webaddress instead.

Click to expand...

From inside your LAN this seems to be this loopback problem with your router.

Regarding accesses from the outside: have you set up www.domainname.dom and domainname.dom for that web site?

I have set up www.mydomain.dom in ISPConfig (and can find it using www.dnsreport.com) I have not set up domainname.dom using ISPConfig, but it passes a dnsreport.com check.

Click to expand...

Don't you have domainname.dom on the Co-Domains tab of the www.domainname.dom web site? Then you should add it there because otherwise people can access the web site using www.domainname.dom, but not domainname.dom.

Don't you have domainname.dom on the Co-Domains tab of the www.domainname.dom web site? Then you should add it there because otherwise people can access the web site using www.domainname.dom, but not domainname.dom.

Click to expand...

Good point. I'll do that as soon as I'm back home and will see if that helps.