Dedicated server fine to nominet but latency within nominet ?

[ukdomains]

Got my script working but server is a major issue at the moment.

tried to catch ssa.co.uk failed !

got many tracerouters back from different suppliers who peer with nominet.

They are saying theirs some latency within nominet

1 0.892 ms 0.878 ms 0.869 ms
2 0.861 ms 0.852 ms 0.844 ms
3 0.836 ms 0.829 ms 0.822 ms
4 fe1-1-nom-col2.nominet.org.uk (195.66.226.61) 1.790 ms 1.784 ms 1.777 ms
5 host-213-248-206-1.nominet.org.uk (213.248.206.1) 3.761 ms 3.756 ms 3.744 ms

Hmm i puzzled with that traceroute from the dedicated server to nominet 1.8ms then for the packets to reach the next point jumps to 3.761.

im i doing something wrong ?

not asking for any secrets just hints


cheers guys for any pointers

 

[DaveH]

Latency within corporate networks is typical and Nominet is not an exception. They'll have firewalls / packet shapers / proxy servers etc...

"tried to catch ssa.co.uk failed !"

On a side note, You could have the fastest connect to Nominet yet still have little chance of catching ssa.co.uk.

 

[monaghan]

tried to catch ssa.co.uk failed !

I should think you were up against at most public and private catchers for that name

If the name is worth having, then expect a lot of competition and initially you won't get much success, but you can beat people to the better names occasionally and in time you can tweak and learn.

You'll probably rewrite your script several times before catching your 1st "big one", but the enjoyment of seeing that notification in your inbox for a LLL.co.uk can't be beaten

Don't worry about anything past Nominet's border router, there's not a lot that can be done (unless you can convince Nominet to assign your traffic a higher priority than the rest of us )

Keep at it and the results will arrive.

 

[armistice]

Got my script working but server is a major issue at the moment.

tried to catch ssa.co.uk failed !

got many tracerouters back from different suppliers who peer with nominet.

They are saying theirs some latency within nominet


Hmm i puzzled with that traceroute from the dedicated server to nominet 1.8ms then for the packets to reach the next point jumps to 3.761.

im i doing something wrong ?

not asking for any secrets just hints


cheers guys for any pointers

Latency on any network is normal, nominet are no exception. For a more acurate picture than either traceroute or ping can show you, create a test script and time using a high resolution timer the ellapsed time between query sent and answer received.

eg.

Start Timer
Dac query -> example.co.uk
Read Dac answer
Stop timer

If you use .net the stopwatch class is easy to use and high resolution. You can do a few and get the average. You can also test epp in the same way (timing a hello message).

Competetion is fierce for the top domains, and having the fastest times doesn't guarantee catches, the problem is the dac limit stopping you quering at a higher frequency.

It would be interesting to see what timings people get,
To get us started my time for the dac query <> answer above is 4ms give or take 1/10th of a ms.

 

[ukdomains]

Latency within corporate networks is typical and Nominet is not an exception. They'll have firewalls / packet shapers / proxy servers etc...

"tried to catch ssa.co.uk failed !"

On a side note, You could have the fastest connect to Nominet yet still have little chance of catching ssa.co.uk.

Reason i said that was because i saw my script return the answer ssa.co.uk dropped trying to register domain lol

Thanks Dave

 

[ukdomains]

I should think you were up against at most public and private catchers for that name

If the name is worth having, then expect a lot of competition and initially you won't get much success, but you can beat people to the better names occasionally and in time you can tweak and learn.

You'll probably rewrite your script several times before catching your 1st "big one", but the enjoyment of seeing that notification in your inbox for a LLL.co.uk can't be beaten

Don't worry about anything past Nominet's border router, there's not a lot that can be done (unless you can convince Nominet to assign your traffic a higher priority than the rest of us )

Keep at it and the results will arrive.

Thanks, At the moment i think its okish the script i got. Then again i havn't booked many domains but next couple of days i have booked some domains il see what i get from that list.

 

[ukdomains]

Latency on any network is normal, nominet are no exception. For a more acurate picture than either traceroute or ping can show you, create a test script and time using a high resolution timer the ellapsed time between query sent and answer received.

eg.

Start Timer
Dac query -> example.co.uk
Read Dac answer
Stop timer

If you use .net the stopwatch class is easy to use and high resolution. You can do a few and get the average. You can also test epp in the same way (timing a hello message).

Competetion is fierce for the top domains, and having the fastest times doesn't guarantee catches, the problem is the dac limit stopping you quering at a higher frequency.

It would be interesting to see what timings people get,
To get us started my time for the dac query <> answer above is 4ms give or take 1/10th of a ms.

Thats a good idea i did try that with a windows 7 sidebar gadget lol it was about 2-3 seconds.

 

[DaveH]

Reason i said that was because i saw my script return the answer ssa.co.uk dropped trying to register domain lol

Thanks Dave

Most people get the ,N notification. It's just getting your registration request in first.

 

[essexboy]

How do you get a display of the actual trace time instead of <1ms is that only linux/unix? and not windows?

I do a trace to nom and I get fluctuating responses, 1 minute its <4ms the next its 2ms,30ms,50ms etc... and they are supposed to be peered.

 

[ukdomains]

How do you get a display of the actual trace time instead of <1ms is that only linux/unix? and not windows?

I do a trace to nom and I get fluctuating responses, 1 minute its <4ms the next its 2ms,30ms,50ms etc... and they are supposed to be peered.

well from the linux box you can do :

tracepath and traceroute

from windows
try traceroute

thats what i use

 

[essexboy]

I'm on a windows server so it only shows <1ms.

 

[ukdomains]

1 0.892 ms 0.878 ms 0.869 ms
2 0.861 ms 0.852 ms 0.844 ms
3 0.836 ms 0.829 ms 0.822 ms
4 fe1-1-nom-col2.nominet.org.uk (195.66.226.61) 1.790 ms 1.784 ms 1.777 ms
5 host-213-248-206-1.nominet.org.uk (213.248.206.1) 3.761 ms 3.756 ms 3.744 ms

I am still puzzled with the traceroute.

Even if i get 195.66.226.61 to respond back at 0.5ms(never will get that) , point 5 will return back a higher response back i.e. 3ms etc

Why is that ?

 

[stender]

what does it matter?