From http://www.ferreum.net
How Do You Know If Your Website Is Down?
By Ferreum Corporation
Nov 3, 2005 - 4:08:00 PM
If you can't reach your website, but the rest of the internet appears
to be fine, how do you know for sure if your website is down or you are
having a computer or intranet problem?
First, we need to understand how a server - the computer where your
website resides - is found. A connection to the server has a sort of
phone number or id. It's called an IP (Internet Protocol) address. It
usually, if it's truly part of the world wide web, has a Domain Name.
For added security, many of us use what's called a proxy server. A
proxy server masks your server under a general pipeline or connection.
You can reach your website by Domain Name, but not by IP address.
Why is the idea of proxy servers important in understanding whether or not your website is actually up and running correctly?
Because
we can use a proxy server, in this case Megaproxy.com, to determine if
the site is actually functioning correctly and rule out server,
pipeline or Domain Name problems.
A server problem would be hardware related or simply the server
actually crashed and the backup did not kick in. A pipeline problem is
when the connection going out and coming in from the internet is down
or unstable. A Domain Name problem is when the Domain Name and the IP
address has gotten muddled in the connections made on the internet to
reach your website.
It's the Domain Name problem which is the tricky one to fix and the one
that requires the most drastic measures. If the server is down, it's
replaced or rebooted. The pipeline is fixed by the telephone provider
and it can be tested locally.
Domain Name problems? In comes megaproxy.com and not a direct IP
connection. But why? Most IT specialists would think that an IP address
and direct connection will determine if the problem is with the server
or on their computer or intranet. Not true. The missing factor is
Domain Name registration.
If the Domain Name registration has gotten garbled, neither technique
will determine this at all. A direct connection will be made even
though some locales, or all, will not be able to surf and reach the
site through normal web surfing standards - domain name.
Before drastic measures are taken, from re-establishing the Domain,
refreshing or changing the IP address, removing Proxy servers or
changing servers as a last resort, IT specialists should use
Megaproxy.com. With megaproxy.com, you leave your own intranet
environment and use a proxy server to send out and receive web pages.
If you can view the site through megaproxy.com, you have discovered
three things at once:
- The server is up and running serving up pages correctly.
- The domain name is working and leading you to the correct website.
- If you cannot surf that particular site directly, the problem is local and not with the server or registration.
DRASTIC MEASURES
When IT specialists believe there is a
problem reaching a site by Domain Name and insist that the problem is
not their intranet, drastic measures are many times taken. They are
drastic because the site will be down between 20 minutes to several
hours or more. The effect is the same. You are sending out a new DNS
message into the world wide web to reestablish a correct connection to
the server. This could include removing proxy servers, changing IP
addresses and/or simply renewing the domain.
The short term effects are sometimes peculiar - from "no server found",
to being sent to the wrong home page and in one case we can recall
surfing the net using the domain name and finding the server - the computer you were using to surf the net!
Understanding the connections and how they work on the net can be a
lifesaver. Using Megaproxy.com, it's free to try if you're in a jam,
can help IT specialists determine what may be going wrong and keep the
drastic measures at bay. They can also help you work with others in
your field to rule out server or DNS problems and allow them to focus on
their intranets instead.
© Copyright 2002-2006 by http://www.ferreum.net