Port forward works for IP but not FQDN

kjurkic · 11-17-2011, 09:33 AM

Hello all

Perhaps my search terms were wrong, but I did not find a post with this specific problem.

I have a working port forward to an internal web server, so that folks from off-site can type in the Untangle firewall IP and a sub-directory and get routed to the login page, ie __htt_p://xx.xx.xx.xx/egroupware

When they try the same with a FQDN, they get a "404 Page not found"
ie h_ttp://our.fqdn.ca/egroupware. I will note that this message is coming from the internal server, not from the untangle firewall.

I know that my forward rules are working as noted above, but I am curious as to why the FQDN would change the forwarding behavior?

The internal host does not have the FQDN assigned as host name; is this perhaps the problem?

thanks
Ken

sky-knight · 11-17-2011, 10:09 AM

FQDN doesn't change forwarding behavior, all the DNS name does is resolve to the IP you're using and the IP based forward is what delivers the packets.

What you need to do is fix your web server, it isn't configure to properly serve requests for the domain name, the key here is likely the host header configuration on the web server.

Mathiau · 11-17-2011, 12:37 PM

yup, did you also set your FQDN to forward properly to your IP from your domain provider?

kjurkic · 11-17-2011, 04:07 PM

Hi & thanks guys

I kinda figured it wasn't in issue with Untangle, but wanted to positively remove it as a candidate; I have to support a lot of different IT, security, media, & communication systems without the opportunity to become an expert at any one.

Mathiau: my FQDN is good; as I dug a bit more, I was able to confirm that the request was going through the firewall, but just not getting proper response from the internal server. It was confusing me that the internal server could function properly serving the IP request, but not the FQDN request.

regards
Ken

sky-knight · 11-17-2011, 04:22 PM

That is usually the "host header", it's the magic that allows a web server to host multiple domains.

If you provide the www server and version you're using someone may be able to point you in the right direction.

Mathiau · 11-18-2011, 12:42 PM

Apache

http://www.thegeekstuff.com/2011/07/...-virtual-host/

IIS6
http://www.visualwin.com/host-header/

IIS7
http://technet.microsoft.com/en-us/l...95(WS.10).aspx

11-17-2011, 09:33 AM	#1 (permalink)
kjurkic Newbie Join Date: Dec 2009 Posts: 2	Port forward works for IP but not FQDN Hello all Perhaps my search terms were wrong, but I did not find a post with this specific problem. I have a working port forward to an internal web server, so that folks from off-site can type in the Untangle firewall IP and a sub-directory and get routed to the login page, ie __htt_p://xx.xx.xx.xx/egroupware When they try the same with a FQDN, they get a "404 Page not found" ie h_ttp://our.fqdn.ca/egroupware. I will note that this message is coming from the internal server, not from the untangle firewall. I know that my forward rules are working as noted above, but I am curious as to why the FQDN would change the forwarding behavior? The internal host does not have the FQDN assigned as host name; is this perhaps the problem? thanks Ken

11-17-2011, 10:09 AM	#2 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 8 Posts: 15,454	FQDN doesn't change forwarding behavior, all the DNS name does is resolve to the IP you're using and the IP based forward is what delivers the packets. What you need to do is fix your web server, it isn't configure to properly serve requests for the domain name, the key here is likely the host header configuration on the web server. __________________ Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879

11-17-2011, 12:37 PM	#3 (permalink)
Mathiau Join Date: Feb 2008 Location: Costa Frickn' Rica Posts: 1,467	yup, did you also set your FQDN to forward properly to your IP from your domain provider? __________________ Def1:Started:UT 7.1 x64 -- Current :UT 9.1 x64\| Gigabyte GM-G31 mATX \| Intel Q8200 \| 8G DDR2 800 \| 80G WD \| 4x Intel Pro 1000 GT NIC's \| Corsair 550W PSU \| Norco RPC-250 2U Case \| 50mb/50mb \| 10 users

11-17-2011, 04:07 PM	#4 (permalink)
kjurkic Newbie Join Date: Dec 2009 Posts: 2	FQDN port forward Hi & thanks guys I kinda figured it wasn't in issue with Untangle, but wanted to positively remove it as a candidate; I have to support a lot of different IT, security, media, & communication systems without the opportunity to become an expert at any one. Mathiau: my FQDN is good; as I dug a bit more, I was able to confirm that the request was going through the firewall, but just not getting proper response from the internal server. It was confusing me that the internal server could function properly serving the IP request, but not the FQDN request. regards Ken

11-17-2011, 04:22 PM	#5 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 8 Posts: 15,454	That is usually the "host header", it's the magic that allows a web server to host multiple domains. If you provide the www server and version you're using someone may be able to point you in the right direction. __________________ Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879

Protect

Filter

Perform

Connect

Manage

Add-Ons

11-18-2011, 12:42 PM	#6 (permalink)
Mathiau Join Date: Feb 2008 Location: Costa Frickn' Rica Posts: 1,467	Apache http://www.thegeekstuff.com/2011/07/...-virtual-host/ IIS6 http://www.visualwin.com/host-header/ IIS7 http://technet.microsoft.com/en-us/l...95(WS.10).aspx __________________ Def1:Started:UT 7.1 x64 -- Current :UT 9.1 x64\| Gigabyte GM-G31 mATX \| Intel Q8200 \| 8G DDR2 800 \| 80G WD \| 4x Intel Pro 1000 GT NIC's \| Corsair 550W PSU \| Norco RPC-250 2U Case \| 50mb/50mb \| 10 users