birger,
From: birger <birger(a)birger.sh>
This is off topic since the router is responsible here.
OK, but that is why I asked - I wasn't sure if it was Fedora networking
. .
When you use fqdn you are probably hitting your routers public ip,
right? You then use port forwarding to forward the requests to the
internal server.
Right, that makes sense . .
Sadly, many routers only do that port forwarding when
you actually hit from the outside.
Why sadly? If my router was doing that I wouldn't have a problem . .
Thanks,
Phil.
29. okt. 2015 7.58 a.m. skrev Philip Rhoades
<phil(a)pricom.com.au>:
>
> People,
>
> Most of my domains are on cloud servers but a couple of less critical
> ones I have hosted a server (192.168.1.10) on my LAN. The port
> forwarding on the router is OK and people from outside see the web
> sites
> no problem. Although the way I have my networking set up seems to be
> fine in all other respects, when I browse to the FQDN of one of the
> LAN
> Server-hosted web sites - from a workstation on the LAN, instead of
> seeing the web site, I see the admin login screen for the modem /
> router
> (192.168.1.1).
>
> I am guessing there is something simple that will fix this problem but
> my messing around with networking so far hasn't got me anywhere . .
>
> Any suggestions?
>
> Thanks,
>
> Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au