Moving dns off site

Re: Moving dns off site

From:

Date:

Time:

Your comment about two cross-country trips tells me you have a
misunderstanding of how DNS works.

Web traffic doesn't go through the DNS server. The web browser
contacts its local DNS server (as configured in TCP/IP settings),
gets the address of the web server, and then contacts the web server
directly.

The DNS server, in the process of figuring out the answer to the
browser's question, may have to send queries all over the world. And
yet, because DNS is a very lightweight and fast protocol, it usually
takes less than a second to get an answer, despite potentially having
to query three or more other DNS servers.

Chris Buxton
Men & Mice - Making DNS Easy

At 8:42 AM -0800 12/18/04, jimsheffer wrote:
>Aaron-
>
>Right now, we have servers in FL and Seattle. We have separate DNS servers
>at each location. What I want to do is re appropriate the dns server in
>Seattle for a different use.
>
>Here's the situation:
>
>Florida location has 2 dns servers, serving information for the Florida
>machines.
>
>Seattle has 2 dns servers, serving information for the Seattle machines.
>
>I want Florida to serve information for both machines.
>Latency IS what I'm concerned about.
>
>Right now, if I try to connect to the server in Seattle, I will be directed
>to the dns server in Seattle, then to the server at the same location- no
>latency between the dns server and the actual server.
>
>If I move all dns to Florida, and If I'm on the west coast and go to one of
>the Seattle servers, I would essentially be directed to the dns server in
>Florida, which would then redirect me to the server in Seattle- two cross
>country trips.
>
>I'm wondering how much of an issue this will be for the Seattle servers
>latency wise.
>I understand it all depends on where the servers are, ie how far off the
>backbones, etc, but I'm trying to assess the move of DNS servers BEFORE I do
>it.
>
>Thanks for your reply.
>
>Jim Sheffer,
>
>OmniPilot Software http://www.omnipilot.com
>Systems Administrator jimsheffer@omnipilot.com
>
>
>
>On 12/17/04 11:14 AM, "Aaron Lynch" <a.list@ninewire.com> wrote:
>
>> You connection speed should decrease for people on the east coast. Most of
>> the delay in looking up a website is because of the time it taks to do
>> lookups, not the actual connection to the webserver. And so for people on
>> the east coast, those lookups should be shorter.
>>
>> And should stay the same for westies.
>>
>> The 'connection' speed is not really the same thing as latentcy,
>> Which is what people tend to percieve as the 'speed' of a site.
>>
>>
>> If your site transfers files at 100 Mbits a second, but it takes 45 sec to
>> make the initial connection ppl will perceive it as 'slow'
>>
>>
>>
>>
>>
>>
>>
>> On 12/17/04 10:51 AM, jimsheffer mashed the following keys :
>>
>>> Hi all-
>>>
>>> We have servers in 2 locations. I want to move the dns to another server
>>> that is across the country.
>>>
>>> But here's my concern:
>>> Won't the connection speed drop, as one has to hit the dns server on the
>>> east coast, then get to the specified server on the west coast?
>>> Seems that's a lot of hops...
>>>
>>> Jim Sheffer,
>>>
>>> OmniPilot Software http://www.omnipilot.com
>>> Systems Administrator jimsheffer@omnipilot.com
>>>
>>>
>>>
>>
>>
>>

Sales:
888/4-DPOINT

Support:
858/452-3696