Date: Sat, 25 Oct 2003 21:36:09 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Charles Howse <chowse@charter.net> Cc: freebsd-questions@freebsd.org Subject: Re: Website up, then down, then up, etc. Message-ID: <20031025203609.GA66626@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <002e01c39b2d$cfe1c820$04fea8c0@moe> References: <20031025175602.GA21699@happy-idiot-talk.infracaninophile.co.uk> <002e01c39b2d$cfe1c820$04fea8c0@moe>
next in thread | previous in thread | raw e-mail | index | archive | help
--d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote: > > That's good in one way: it means that your system is actually working > > perfectly well. Unfortunately it also implies that the problem is > > actually somewhere in the network downstream of you. Since it seems > > to affect all external users equally, the problem must be 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 by someone > > with a clue. > >=20 > > The on/off behaviour often means that you're interacting with a dual > > server system, which is possibly meant to provide 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 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 '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, since I have > only been using them since about the 11th of this month, and *also* they > have just completed a major task - moving their datacenter. > http://www.dyndns.org/news/status/ > Check out all that they did within the last 5 days. > I have corresponded with them once and here is the gist of it: 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). I think that dynDNS would seem to have managed to pull off their datacenter move without much noticable fallout. That's pretty impressive... If Charter are denying any interference with the port 80 traffic at all, then they are almost certainly correct. I think you've established that your FreeBSD box is working correctly. 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. It certainly is perplexing. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/mt65dtESqEQa7a0RAn6LAKCTRsBYlF2cCNtAIjKTxVRk83oRTwCfdgqr 0uldboNb6g/rkKF6bXMk98g= =V8+K -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031025203609.GA66626>