Moving dns off site

Re: Moving dns off site

From:

Date:

Time:

On 12/18/04 1:02 PM, "Aaron Lynch" <a.list@ninewire.com> wrote:

> You can use a third party utility, like the DNS timing utility at
> http://www.dnsstuff.com/
>
> Or the dig at men and mice's site and you can determine what the relative
> speed of the lookups is for each location to the third party's location.
>
> It sounds to me like you've overly complicated this in you own mind though,
> :)
>
> For any given site, you don't usually know if DNS is handled in iceland or
> by network solutions or anywhere else.
You've got a good point there. I'm just used to having the dns servers "on
location" of the servers, so I'm trying to find any roadblocks to moving the
dns so far away from the servers themselves. With only a dozen sites on the
dns server in question, it makes sense to me to consolidate the dns onto the
2 dns servers in Florida and free up a machine for other things :)

Just playing devil's advocate to my own ideas :)

Thanks for the help!

Jim
>
>
>
> On 12/18/04 8:42 AM, jimsheffer mashed the following keys :
>
>> 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