Date: Sat, 25 Oct 2003 17:07:31 -0500 From: "Charles Howse" <chowse@charter.net> To: "'Matthew Seaman'" <m.seaman@infracaninophile.co.uk> Cc: freebsd-questions@freebsd.org Subject: RE: Website up, then down, then up, etc. Message-ID: <003201c39b44$63850810$04fea8c0@moe> In-Reply-To: <20031025203609.GA66626@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote: >=20 > > > That's good in one way: it means that your system is=20 > actually working > > > perfectly well. Unfortunately it also implies that the problem is > > > actually somewhere in the network downstream of you. =20 > Since it seems > > > to affect all external users equally, the problem must be=20 > within your > > > service provider's network. The only thing you can do is open a > > > ticket with your support and pray that it gets looked at=20 > by someone > > > with a clue. > > >=20 > > > The on/off behaviour often means that you're interacting=20 > with a dual > > > server system, which is possibly meant to provide=20 > redundancy, but one > > > of the servers isn't working correctly and the load balance isn't > > > cutting out the duff machine. > >=20 > > ARRRRRGGGGGGHHHHHHHHHHH!!!!!! > > Are you talking about my ISP (Charter Communications) or my=20 > Dynamic DNS > > service (DYNdns.org)? > >=20 > > I have just spoken to Charter Tech Support for the second time about > > this, and the tech assured me that they were not=20 > 'affecting' port 80 in > > any way, nor were they using anything similar to portsentry. > >=20 > > It seems more likely to me that the culprit is DYNdns.org,=20 > since I have > > only been using them since about the 11th of this month,=20 > and *also* they > > have just completed a major task - moving their datacenter. > > http://www.dyndns.org/news/status/ >=20 > > Check out all that they did within the last 5 days. > > I have corresponded with them once and here is the gist of it: >=20 > Hmmm... It's not the basic "look up the IP number" part as that's > working just fine. You don't seem to be using their (dynDNS) web > redirection service (ie. howse.homeunix.net resolves to 66.168.145.25 > which whois reports belongs to Charter Communications). Correct, I'm not. I can't get 'homeunix.net' as a domain using WebHop. Shouldn't need it anyway, things were working perfectly without it until last week. > I think that dynDNS would seem to have managed to pull off their > datacenter move without much noticable fallout. That's pretty > impressive... >=20 > If Charter are denying any interference with the port 80 traffic at > all, then they are almost certainly correct. >=20 > I think you've established that your FreeBSD box is working correctly. There's no possibility that I've hosed anything like /etc/hosts.allow or one of the files that restricts connections? > So, I guess, by a process of elimination you might have a problem with > your cable router/modem? Is this a device that has a HTTP interface > that you can configure it with? -- since it seems to be working > perfectly well for all of the other ports, there must be some reason > for it to do nasty things specifically to the port 80 stuff. Yes, the router has a web interface for configuration. It had been set to forward requests on port 80 to the webserver on port 80. That was working perfectly for over a year. I've now set it to port 8080, in and out, which is, of course, working. I have also enabled the DMZ, which, AFAIK, places the server outside the firewall, thereby eliminating it...? Now I've told apache to listen on port 80, no joy. Change back to 8080, perfect! > It certainly is perplexing. It is, isn't it? Dyndns support just answered my last post to them, and basically just explained what DNS does as a way of denying that they are at fault, and I believe them. To quote them, "DNS is just like the Yellow Pages. Your phone book doesn't know you are going through it, calling every number, and subsequently start deleting entries."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003201c39b44$63850810$04fea8c0>