Centos 7 web site seen, but not on local net
 

Now on Centos v7, and working nicely - almost.
Web site is visible to the world, but not on the local network.
That makes it difficult when making changes - need to ask someone external if it worked.

It actually works if I use the local host IP address. But I can only get one specific
web page, since any link will automatically try to use the <web name address>/new page.
Any time I use <local ip addr>/new page - that works fine.

What needs to be properly configured to enable this? (so we can see our web (in normal mode)on local net)

I'm certain it's some "easy" config, but right now it's beyond me.

Thanks much !
Butch

Could you provide a little more information. I understand this to mean that

1) you have a public-facing website on a server in your local network,
2))that computers outside your local network can access the website via its public DNS,
3) that computers inside your local network cannot access it via the public DNS, but
4) that computers inside your local network can access it via their local network ip address.

Is that an accurate understanding of what's going on?

Do you mean by this that your browser is trying to use the name of the last page you visited or is something else happening?

Sorry, I didn't answer the second question (but I don't see my first reply - so I'll provide that as well.

- Answer to first question: You have it accurate.

- More info for the second question:
Since any link on the original page would try to take us thru <web name address>/link-page.html - it doesn't work.
If we instead use <ip address>/link-page.html - it can obtain/present the page.

Can't get there using <web name> - as in www.xxx.com/link-page.html

Is there something about having the server provide a different routing if it's talking to a "local" machine?
Or are the local machines not going out to the world to define the www.xxx.com address?
How to make this work?

Thanks much.

I really don't have any idea what's going on here, but I have a couple of thoughts regarding troubleshooting.

Try doing a dig and a whois from a local machine and comparing the results with the same commands run from an external machine. It could be that the DNS is not resolving properly from inside the network if your outfit is running it's own internal DNS servers (admittedly, this is stab in the dark).

Also, try the same experiment using traceroute (tracert on Windows). That may give some hint as to where the attempts to connect from within the local network are failing.

See the man files for the commands for more information about them.

The external machine seems to see everything correctly.

A local linux machine can't see via WHOIS. But both DIG and TRACEROUTE come up with the same network address.
TRACERT on windows notebook also provides the network address.

I'm wondering about the WHOIS on the linux machine. Think that's significant?

So you are saying that the traceroute from the internal machine reaches the destination without breaking somewhere along the way?

I think whois must be telling us something. I'm not sure what, but sure as shootin' someone here does. Can you post the output of the two "whois" results? For readability, please surround it with "code" tags, which become available when you click the "Go Advanced" button to the right of the "Quick Reply" button beneath the compose message window.

actually, now that you asked about "breaking". I believe the (local) windows TRACERT worked - because it did one jump?
It listed 1 line, and said Trace complete.

The (also local) linux machine (Fedora) listed 30 lines, and did not say Trace complete. I thought since it coughed up
the correct address that it "worked".

I sent a note to someone on an outside machine to send me a copy of his info - but we were working on the server a bunch,
and he's probably logged-off for the night.

ALL our computers have the DNS sites and our gateway defined. (or so I think).
How about I get the outside info, and make sure all computers have the same info. Expect that note tomorrow (possibly
afternoon unless I can get it all early before I head out on the road).

I don't want to keep you working this until I can give you 100% certain info.

Thanks much - again.

Sounds as if it did not so much complete as it died.

The last IP it reported can help us figure out where the trace died. That's why traceroute is such a useful command.

After a few years (and much frustration), I again went thru the settings on our primary router. I decided to experiment with some of them, one at a time. I discovered a WAN setting to: Filter internet NAT Redirection. When I read the router's online help about that setting, I decided to turn it off. I can now see my web site on the internal LAN. I'll get external verification that I didn't mess up the web from the world's viewpoint, and close this. So our architecture is: World -> DSL -> router -> LAN, including the server
;;;; The router was responsible for not seeing the web from the internal LAN (other than on the server, where it always appeared healthy)

Thanks so much for all your assist.