First post.... Lan/some Vlans cant get to website, some vlans can

VillageIT

ok guys.... I've traded all the DNS in my system to use the pfsense box, and moved all the phones, etc to the networks I wanted them on, and pretty much got the networks the way I think they should be (or reasonably close so we can run this way indefinitely). Yesterday I didn't seem to have any issue getting to the tools (we have a maintenance ticket system, transportation calendar (booked is the software if you are familiar), a phpbb "communication log" and a couple similar things.....

This morning at 10:30 they went unreachable again. One more data point I hadn't realized before... They are on domain.net/log, domain.net/maint, and domain.net/calendar.... The index.html at the base domain is simply a time/date page one of our shared monitors use to display thaat info.... I can get to the domain.net.
WTH?!?!?!?!?
What can cause the base domain to be reachable but not the folders under it? Intermittently????? Not sure this is a pfsense thing..... Not sure it's my issue at all.... Hostgator says they have no idea.....
AAAGGGHHHH

johnpoz

@VillageIT how would it be a pfsense thing.. pfsense has zero to do with you getting to domain.tld vs domain.tld/index.html or index.php or otherpage.html on that domain.

Unless your running proxy or ips - pfsense just sends the packets on, and to whatever IP the fqdn resolves too..

VillageIT

@johnpoz I mean a setup thing on my end...
Came back up all by itself at 1:30. It's gotta be something here, just can't get my head around it. It's just to strange that it's one of 4 websites we use all day every day. I used to have them hosted on site (I have a cpanel metal box here) but moved them to hostgator because I thought about getting rid of the cpanel when their prices went nuts. Might have to move them back.

Are we allowed to solicit moderators to take a look? You'd probably find my error in minutes.

bmeeks

Your problem as described in your previous post is not a pfSense issue. It is something on your web server setup. Your domain.net I assume resolves to a single IP. The URLs have the domain name in them, but then also include a web path that only the web server (or a web proxy) can read and understand. DNS and pfSense stop at the end of net in your example. The trailing slash and everything after that is the responsibility of the web host the URL is directed towards.