Website up, then down, then up, etc.

[Charles Howse]

> On Sat, Oct 25, 2003 at 10:58:53AM -0500, Charles Howse wrote:
> > I did change the listen address to 8080 in httpd.conf and 
> in the port
> > forward on the router, and rebooted.
> > NOW IT IS WORKING! As of 10:42 CDT, which is 16:42 UTC.
> > http:/howse.homeunix.net:8080
> > Is there anything else to look at, or any files to peruse?
> > Running on port 8080 is _*not really acceptable for the long run*_.
> 
> 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.
> 
> 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.

ARRRRRGGGGGGHHHHHHHHHHH!!!!!!
Are you talking about my ISP (Charter Communications) or my Dynamic DNS
service (DYNdns.org)?

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.

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:

(Me)
[snip]
> > Can you think of *anything* on your end that may be contributing to
> > this problem? 

(Them)
> No, nothing on our end would be contributing to this. Since the host
> name is resolving the DNS is working correctly. Connections on port
> 80 are being refused so this would seem to be a problem with your
> router or with the web server itself.