Dedicated Server Routing and What It Means To You

Getting from here to there.

What happens when a client types the address of your dedicated server into their browser? In a perfect world, they would be taken directly to your site(s). But of course, this is simply not possible. Any request to your server must first pass through a variety of network devices before finally reaching its intended destination.

Navigating the virtual maze.

Before you sign a hosting agreement –try this. Type the command “tracert” (from a windows PC command prompt) and then insert a known IP address from that service provider. What do you see? How many “hops” does your packet have to pass through before finally reaching its destination? This can be a crucial factor when determining which Internet Service Provider is best for your needs.

For example, many ISPs are simply subsidiaries of even larger service providers which could in turn, be subsidiaries of other service providers, etc, etc. In this scenario, a request to your server may have to jump through multiple hops before reaching its destination and of course, all of this equals slower and slower response times.

Fortunately, Internet routers are configured to attempt to find the shortest path between network devices, but this does not always mean that your server will be just a few short hops away from any given location and of course, it’s important to keep in mind that someone half way across the world will still have to “travel” half way across the world (and thus, through multiple networks) in order to reach your site. After all, some things are simply unavoidable.

The Internet “backbone”.

A handful of communications companies own the Internet “backbone” that all of us must use when browsing the web, but these companies have no control over the seemingly endless maze of routers, switches, servers, firewalls and various other devices that may lie between your dedicated server and the rest of the world.

Many small Internet Service Providers are stuck behind a virtual maze of devices between their location and the Internet backbone and if speed and connectivity are crucial factors in your web development plan, you should take a close look at just how complex the path between your server and the rest of the world actually is.

Of course, closer connectivity to the Internet backbone usually equals greater cost, but you should be able to easily weigh the advantages of dollars over connectivity when you are armed with the proper tools and a clear idea of how much “lag time” is acceptable to you. In essence, we are essentially talking about milliseconds here –but in a world where even the smallest hurdles can quickly multiply into a monumental challenge, it’s important to squeeze as much speed as possible out of your dedicated server.

Before you sign on the dotted line.

Before signing a service agreement, ask your ISP about their backbone connectivity. Who is their Internet Service Provider? Do they have redundant routers in case one should happen to fail? Do they use technologies like Network Address Translation, hardware firewalls and other options that could slow the traffic to and from your site?

Copyright © 2005 WebHostAuditor.com
More Webmaster Articles