Root Cause for my DSL Woes Solved. Downtime.

I take the unusual measure, of hosting my Web-site and thus my blog, on my private computer here at home. This gives more-mainstream users – who go through a professional hosting service – the advantage, that professionals also work to prevent downtime. With me, if anything cuts my connection to the WAN – the Wide-Area Network – my site and my blog become unreachable to the public.

There have been ongoing problems with my DSL service, which provides my home access to the WAN, and which I also commented about Here.

Well, this morning between 9h00 and 10h00, my externally-provided DSL cut out on me again. This time I placed a service call to my ISP, and as before, they offered me a prompt, rapid response from a technician. But unlike last time, I took this offer, and received professional service within the same day.

According to how it now stands, the root cause for the previous malfunction has been found this time. Last time, the repair that was done was faster to carry out, but did not solve the root problem.

So I am finally looking forward to a stable connection, and should be publicly visible as of 16h30 the same day…

Oh. Because I also needed to reboot my computer, my server-side cache has been cleared, and this blog will seem to load whichever postings you prefer to read more slowly for a little while, again.

I apologize for any inconvenience.

Continue reading Root Cause for my DSL Woes Solved. Downtime.

So. My Blog is back online.

One of the facts which I have written about numerous times, is that I take the unusual approach, of hosting my Web-site and my Blog, on my own Server at home. This differs from what most people would do, which would be to go to a commercial / professional hosting service.

They have an advantage over me, in that their provider has better resources to ensure the availability of their content.

I, on the other hand, can simply be taken offline, as soon as my physical connection – my Home DSL – becomes faulty.

This was exactly what happened to me, between 4h00 on Saturday morning, October 22, and now, 11h00, Tuesday morning, October 25.

A technician from my ISP honored his appointment today, and came, and did repair my connection.

My ISP was actually willing, to set me up with a technician as early as Sunday afternoon, but I skipped that choice in the automated system, where I created my repair ticket, because on Sunday afternoon I had a prior engagement – to play the RPG Quest-Masters with a group of friends – and because I did not see this tech support case as an emergency myself.

I am confident that my site will be visible again for some time. But I also recognize, that due to 3-4 days of having been offline, of course my search-engine rankings will have suffered. So for the next little while, I do not expect to be receiving as many hits per day, as I had been receiving prior to Saturday.

Easy come, easy go.



The problem with my DSL is worse than I thought.

I have paid closer attention, to the ‘Internet Connection Failure’, which I just posted about Here. Even though the public cannot read my blog right now, the way I am set up, still allows me to write entries.

When I checked my DSL more carefully, I noticed that I do not have a dial-tone. And, every half hour, to every two hours apart, the DSL connection is dropping out on me. This does not seem to have been a problem with the router per se.

For the past few days, Montreal has been experiencing continuous, heavy rainfall, starting on ?Tuesday? The weather is going to stay this wet, until tomorrow (Sunday). I suppose that what can happen, is that excess water can seep into the cables, and can cause those DSL wires with the weakest insulation to fail. I hear crackling noises when I listen on my phone, for an expected dial-tone.

Certain services are more sensitive than others, to errors in the transmission of packets. It would seem that the Teredo gateway has no tolerance for those at all, for which reason it was dropping my client connection frequently.

And, had I left things as they were, the ‘DynDNS’ service would have attempted inexhaustibly, to keep associating new IPv4 addresses with my URL, even as the modem was dropping the connections, and establishing new ones.

The only responsible thing I was able to do in response, was to shut down my DynDNS service for now, to avoid future, excessive update-requests, which also means that the public cannot be reading this as I am writing it.

The technician from my ISP is scheduled to come by on Tuesday, to see what can be done to remedy this problem. And my blog and site will have to remain offline until then.