DNS servers in Germany

[Theo]

Since Sedo opened up office in the US - in August if I recall correctly - we are still left with the nameservers ns1 & ns2.sedoparking.com in Germany.

The problem is that for the bulk "quality" traffic originating in the US, the location of the DNS servers is too far away. The hop times exceed 150 ms over a fast network. The acceptable times would be sub-60 ms.

So the obvious question is, when will Sedo establish nameservers on US soil?

Example below:

traceroute to ****** (212.227.34.3), 64 hops max, 40 byte packets
 1  woody.telcom.arizona.edu (128.196.128.253)  0 ms  0 ms  0 ms
 2  128.196.24.167 (128.196.24.167)  1 ms  1 ms  1 ms
 3  wyatt.telcom.Arizona.EDU (192.80.43.42)  1 ms  1 ms  1 ms
 4  12.125.99.77 (12.125.99.77)  4 ms  3 ms  3 ms
 5  gbr2-p70.phmaz.ip.att.net (12.123.142.50)  3 ms  4 ms  4 ms
 6  tbr2-p013702.dlstx.ip.att.net (12.122.10.85)  24 ms  24 ms  24 ms
 7  ggr2-p390.dlstx.ip.att.net (12.123.17.85)  23 ms  23 ms  23 ms
 8  att-gw.dfw.sprint.net (192.205.32.70)  25 ms  25 ms  25 ms
 9  sl-bb22-pen-13-0.sprintlink.net (144.232.9.30)  114 ms  224 ms  212 ms
10  sl-bb27-pen-9-0.sprintlink.net (144.232.16.54)  85 ms  78 ms  80 ms
11  sl-bb21-nyc-2-0.sprintlink.net (144.232.20.96)  67 ms  67 ms  67 ms
12  sl-bb23-nyc-3-0.sprintlink.net (144.232.7.109)  67 ms  67 ms  67 ms
13  sl-bb20-par-11-0.sprintlink.net (144.232.20.44)  212 ms  305 ms  286 ms
14  sl-bb21-fra-13-0.sprintlink.net (213.206.129.66)  148 ms  148 ms  148 ms
15  sl-gw20-fra-1-1.sprintlink.net (217.147.96.227)  148 ms  148 ms  148 ms
16  sle-schlun-2-0.sprintlink.net (217.147.97.58)  146 ms  146 ms  147 ms
17  so-5000.gw-backbone-a.bs.ka.schlund.net (212.227.120.6)  154 ms  154 ms  156 ms
18  a0kac1a.gw-dists-a.bs.ka.schlund.net (212.227.116.208)  148 ms  149 ms  151 ms
19  www1.sedoparking.com (212.227.34.3)  150 ms  148 ms  148 ms

 

[Theo]

The silence is deafening.

 

[Prosperous]

lol, I hear (pun intended) you. :-D


.

 

[SedoCoUk]

Hi there,

Sorry for the delay in replying. I have been away wasting money in the UK for the past few days. It's great to be back though.

I have talked to the head of the tech team and he has given me the following answer:

Firstly, the traceroute you have shown goes directly to the parked page rather than to the DNS which means that the actual loss in time won't be quite as long as it may seem.

However, we do fully appreciate that the best solution would be to have
nameservers on US soil and we are hoping to implement this within the next six months. We see this as a vital long-term goal for Sedo, but it is a system which takes time to implement as database replication is far harder across the Atlantic than in our own server room in Germany!

We do believe that the loss to our US customers or customers with US traffic is absolutely minimal, but we are working to set up DNS servers on US soil in our ongoing efforts to make the perfect domain platform.

Thank you for voicing your concerns. It is something we have been working on for some time and we can hopefully implement it in the near future.

Feel free to email me directly with any questions at [email protected]

Regards,

Ed
Key Account Manager
UK Marketing Associate
_______________________________________________

SEDO.CO.UK :: Buy and Sell Domain Names and Websites
tel within UK 0871 900 8450 :: fax 0871 900 8451
tel +49 221.420.758.156 :: fax +49 221.420.758.11
tel (US) (877)-349-5902 :: fax (212)-202-3951
email: [email protected] :: http://www.sedo.co.uk

_______________________ :: make a name for yourself.

 

[Domagon]

I say things the way I see them ... in this instance, Sedo's tech is right in the sense that DNS isn't much of an issue.

When one first visits a webpage, the name servers will likely be queried, but afterwords will be cached - not necessarily just for that particular user, but also for many other users too on the same network / ISP.

So in a nutshell, location of name servers, in particular for popular sites, is often a minimal issue - a bigger issue in regards to Sedo parking is where the content is being served from, server configuration, and the quality of the network it's connected to.

Ron

 

[Theo]

Not sure what I had in mind; of course I wanted to refer to the actual content-serving servers, which are in Germany.