cancel
Showing results for 
Search instead for 
Did you mean: 

Ongoing DNS Issues? Timeouts....

npr
Pro
Posts: 1,898
Thanks: 119
Fixes: 9
Registered: ‎21-01-2013

Re: Ongoing DNS Issues? Timeouts....

The attached results from dnsbenchmark shows an unacceptable level of failed look ups from a number of dns servers. The red through the IP address represents the amount of failed look ups.
I've previously reported this but PN have shown no interest, admittedly it could be a issue with my line although I doubt it.
If you're suspecting a dns issue you could run DNSBenchmark to confirm this and post any poor results here.
Download dnsbenchmark:
https://www.grc.com/dns/benchmark.htm
Alternatively you could run your own DNS resolver Wink
http://npr.me.uk/unbound.html
or try a dns proxy
http://mayakron.altervista.org/wikibase/show.php?id=AcrylicHome
Kelly
Hero
Posts: 5,497
Thanks: 380
Fixes: 9
Registered: ‎04-04-2007

Re: Ongoing DNS Issues? Timeouts....

Totally not seeing the same problems. Connected via ptn.
Kelly Dorset
Ex-Broadband Service Manager
30FTTC06
Pro
Posts: 2,286
Thanks: 108
Fixes: 4
Registered: ‎18-02-2013

Re: Ongoing DNS Issues? Timeouts....

ptn-ag03 still.
I still have loss on Level3, looks like kelly has the same.
servers.ini
4.2.2.1             a.resolvers.level3.net
4.2.2.2            b.resolvers.Level3.net
4.2.2.3            c.resolvers.level3.net
4.2.2.4            d.resolvers.level3.net
4.2.2.5            e.resolvers.level3.net
4.2.2.6            resolver8.Level3.net
194.72.6.51        newns0.bt.net
194.72.6.57        indnsc10.ukcore.bt.net
194.73.82.242      indnsc50.bt.net
208.67.220.123      resolver2-fs.opendns.com
208.67.220.220      resolver2.opendns.com
208.67.220.222      resolver4.opendns.com
208.67.222.123      resolver1-fs.opendns.com
208.67.222.220      resolver3.opendns.com
208.67.222.222      resolver1.opendns.com
209.244.0.3        resolver1.level3.net
209.244.0.4        resolver2.level3.net
212.159.6.9        cdns01.plus.net
212.159.6.10        cdns02.plus.net
212.159.13.49      cdns01.plus.net
212.159.13.50      cdns02.plus.net
ejs
Aspiring Hero
Posts: 5,442
Thanks: 631
Fixes: 25
Registered: ‎10-06-2010

Re: Ongoing DNS Issues? Timeouts....

The PN dns servers have been OK since 6th March and so I've stopped my graph drawing.
npr
Pro
Posts: 1,898
Thanks: 119
Fixes: 9
Registered: ‎21-01-2013

Re: Ongoing DNS Issues? Timeouts....

Quote from: Kelly
Totally not seeing the same problems. Connected via ptn.


I'm on pcl-ag03
30FTTC06
Pro
Posts: 2,286
Thanks: 108
Fixes: 4
Registered: ‎18-02-2013

Re: Ongoing DNS Issues? Timeouts....

I would be interested in seeing what results you get with ns_bench npr http://pflog.net/ns_bench/
[tt]To use this on windows:
- Extract this zip file somewhere, then either right click
  and "Command prompt here" on the ns_bench folder, or:
- Click start -> run
- type "cmd" (if on Windows ME/98, type command)
- hit enter
- in the command window, cd to where you downloaded and unzipped this,
  probably:  cd C:\Documents and Settings\YourUsernameHere\Desktop\ns_bench\win32
- run the program:
  ns_bench.exe <ip> <ip> ...
  For example:
  ns_bench.exe 127.0.0.1 4.2.2.1 4.2.2.2 4.2.2.3 4.2.2.4 4.2.2.5 4.2.2.6 194.72.6.51 194.72.6.57 194.73.82.242 208.67.220.123 208.67.220.220 208.67.220.222 208.67.222.123 208.67.222.220 208.67.222.222 209.244.0.3 209.244.0.4 212.159.6.9 212.159.6.10 212.159.13.49 212.159.13.50
Note for compiling on windows/cygwin:
- You will need the various build utilities installed in cygwin,
  including make/gcc/autoconf/etc[/tt]
Kelly
Hero
Posts: 5,497
Thanks: 380
Fixes: 9
Registered: ‎04-04-2007

Re: Ongoing DNS Issues? Timeouts....

Quote from: npr
Quote from: Kelly
Totally not seeing the same problems. Connected via ptn.


I'm on pcl-ag03

so, you're hitting the other half of the network. 
11110_110 > It might be worth you repeating your tests connected to a PCL gateway?  I'll try the same later too.
Kelly Dorset
Ex-Broadband Service Manager
npr
Pro
Posts: 1,898
Thanks: 119
Fixes: 9
Registered: ‎21-01-2013

Re: Ongoing DNS Issues? Timeouts....

Quote from: 11110_110
I would be interested in seeing what results you get with ns_bench npr http://pflog.net/ns_bench/

Here you go:
Quote
Nameserver              Response Time (ms)
                       min/avg/max/stdev/retries
127.0.0.1               0.00/0.00/0.00/0.00/0
4.2.2.1                 16.00/28.20/32.00/6.11/0
4.2.2.2                 47.00/50.00/62.00/6.00/0
4.2.2.3                 15.00/28.00/32.00/6.51/0
4.2.2.4                 31.00/53.00/78.00/18.84/0
4.2.2.5                 15.00/25.00/32.00/7.77/0
4.2.2.6                 47.00/67.00/78.00/11.51/0
194.72.6.51             16.00/28.20/32.00/6.11/0
194.72.6.57             15.00/28.00/32.00/6.51/0
194.73.82.242           16.00/28.20/32.00/6.11/0
208.67.220.123          16.00/25.00/31.00/7.35/0
208.67.220.220          15.00/28.00/32.00/6.51/0
208.67.220.222          15.00/28.20/32.00/6.62/0
208.67.222.123          31.00/31.20/32.00/0.40/0
208.67.222.220          15.00/28.00/32.00/6.51/0
208.67.222.222          15.00/28.20/47.00/11.82/0
209.244.0.3             16.00/25.20/32.00/7.52/0
209.244.0.4             16.00/57.00/94.00/33.91/0
212.159.6.9             31.00/31.20/32.00/0.40/0
212.159.6.10            15.00/28.00/32.00/6.51/0
212.159.13.49           16.00/25.80/32.00/6.85/0
212.159.13.50           15.00/28.00/32.00/6.51/0

No "retries" so I assume it's not showing any real problem.
Does that just show ping times or is it lookup times as well?
Also how many times does it try each resolver?
I suspect it's much less than DNS Benchmark, AFAIK that tests 50 different lookup for each resolver.
I suspect the problem I'm seeing here is udp packets being dropped (congestion?) on certain parts of the network.
Edit
Found the answer to some of my above questions:
NS_bench does 25 lookup (UDP) for each server, don't know it that's different or the same lookups.

30FTTC06
Pro
Posts: 2,286
Thanks: 108
Fixes: 4
Registered: ‎18-02-2013

Re: Ongoing DNS Issues? Timeouts....

Cheers npr, that looks a little rough in all honesty, but no, not any failures. However, I'm not sure what is the average for your connection.
But i would be looking for a problem if my connection was showing figures like that.
[tt]Nameserver              Response Time (ms)
                       min/avg/max/stdev/retries
127.0.0.1               0.00/0.00/0.00/0.00/0
4.2.2.1                 16.00/28.20/32.00/6.11/0
4.2.2.2                 47.00/50.00/62.00/6.00/0
4.2.2.3                 15.00/28.00/32.00/6.51/0
4.2.2.4                 31.00/53.00/78.00/18.84/0
4.2.2.5                 15.00/25.00/32.00/7.77/0
4.2.2.6                 47.00/67.00/78.00/11.51/0
194.72.6.51             16.00/28.20/32.00/6.11/0
194.72.6.57             15.00/28.00/32.00/6.51/0
194.73.82.242           16.00/28.20/32.00/6.11/0
208.67.220.123          16.00/25.00/31.00/7.35/0
208.67.220.220          15.00/28.00/32.00/6.51/0
208.67.220.222          15.00/28.20/32.00/6.62/0
208.67.222.123          31.00/31.20/32.00/0.40/0
208.67.222.220          15.00/28.00/32.00/6.51/0
208.67.222.222          15.00/28.20/47.00/11.82/0
209.244.0.3             16.00/25.20/32.00/7.52/0
209.244.0.4             16.00/57.00/94.00/33.91/0
212.159.6.9             31.00/31.20/32.00/0.40/0
212.159.6.10            15.00/28.00/32.00/6.51/0
212.159.13.49           16.00/25.80/32.00/6.85/0
212.159.13.50           15.00/28.00/32.00/6.51/0[/tt]

Edit: Added dnstop test showing the amount of times ns_bench is querying 212.159.6.9 for www.google.com
It appears to be 10 times.
[tt]Nameserver          Response Time (ms)
                    min/avg/max/stdev/retries
212.159.6.9        17.66/17.85/18.12/0.17/0

Queries: 0 new, 10 total                              Sat Mar  8 19:01:42 2014
Query Name        Count      %  cum%
-------------- --------- ------ ------
www.google.com ;       10  100.0  100.0[/tt]
Source Code: This should answer your questions, As far as i'm aware, it just looks up google.com
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>
#include <math.h>
#include <adns.h>
#ifdef __WIN32__
#include <windows.h>
#endif
/* performs the time diff */
#define TIMEFLOAT(tv)   ((tv)->tv_sec + ((tv)->tv_usec / 1000000.))
/* run the query a few times prior to the test to ensure
it's absolutely positively cached */
#define PRE_ITERATIONS 5
/* number of iterations to use in calculating the average
plus 1 for a throw-out run */
#define QUERY_ITERATIONS 5
#define RESOLV_TXT_PREFIX "nameserver "
typedef struct nsres {
double min;
double max;
double avg;
double sd;
int retries;
} nsres_t;
typedef struct qres {
double query_time;
int retries;
} qres_t;
/* function prototypes */
/* function to calculate query time */
double tv_diff(struct timeval * start, struct timeval *end);
/* wrapper to collect the dig run times */
nsres_t bench_ns(const char *ip);
/* function that performs the dns lookup */
qres_t query_ns(const char *ns);
/* to calc the standard deviation */
double standard_deviation(int nelements, double avg, double *data);
/* high resolution timing for windows */
#ifdef __WIN32__
int gettimeofday_hires(struct timeval *tv, struct timezone *tz);
LARGE_INTEGER getFILETIMEoffset(void);
#endif
/* main program */
int main(int argc, char *argv[]) {
int i;
nsres_t res;
if(argc < 2) {
printf("usage: %s <ip> <ip> <ip>\n", argv[0]);
return EXIT_SUCCESS;
}
printf("%-20s\t%s\n", "Nameserver", "Response Time (ms)");
printf("%-20s\t%-20s\n\n", "", "min/avg/max/stdev/retries");
for(i=1; i < argc; i++) {
res = bench_ns(argv);
if(res.avg < 0.0) {
printf("%-20s\tfailed\n", argv);
} else {
printf("%-20s\t%.2f/%.2f/%.2f/%.2f/%d\n", argv, res.min, res.avg,
res.max, res.sd, res.retries);
}
}
return EXIT_SUCCESS;
}
nsres_t bench_ns(const char *ip) {
qres_t q_res;
nsres_t results;
int run_num, i, skip_test = 0, retries = 0;
double query_sum = 0, q_time = 0;
double min = 9999.99, max = -1.0;
double data[QUERY_ITERATIONS];

/* do an initial set of queries to ensure NS has the record cached */
for(i=1; i<= PRE_ITERATIONS; i++) {
q_res = query_ns(ip);
if(q_res.query_time < 0.0) {
/* failure, don't bother doing the test or doing subsequent pre-query
lookups */
results.min = -1.0;
results.max = -1.0;
results.avg = -1.0;
skip_test = 1;
break;
}
}
if(! skip_test) {
for(run_num = 1; run_num <= QUERY_ITERATIONS; run_num++) {
q_res = query_ns(ip);
/* normalize to ms */
q_res.query_time *= 1000.0;
q_time = q_res.query_time;
if(q_res.retries > 0) {
retries += q_res.retries;
/* tell the standard deviation calulcation to ignore this data point,
this along with the count of GOOD data points (QUERY_ITERATIONS-retries)
will give us an accurate standard deviation */
data[run_num - 1] = -1.0;
continue;
}
data[run_num - 1] = q_time;
if(q_time < 0.0) {
break;
} else {
if(q_time < min)
min = q_time;
if(q_time > max)
max = q_time;
query_sum += q_time;
}
}
/* store results and normalize to milliseconds */
results.avg = (double)(query_sum/(QUERY_ITERATIONS-retries));
results.min = min;
results.max = max;
results.sd = standard_deviation(QUERY_ITERATIONS-retries, results.avg, data);
results.retries = retries;
}
return results;
}
double tv_diff(struct timeval * start, struct timeval *end) {
   end->tv_sec -= start->tv_sec;
   end->tv_usec -= start->tv_usec;
   /* normalize */
   while ( end->tv_usec < 0 ) {
       end->tv_usec += 1000000;
       end->tv_sec--;
   }
return TIMEFLOAT(end);
}
/* negative return values indicate failure type:
  -2 : timeout
  -1 : general error/failure
*/
qres_t query_ns(const char *ns) {
qres_t q_res, q_null = {-1.0, -1};
struct timeval start, end;
adns_query query;
adns_answer *answer;
adns_state adns;
adns_initflags flags = adns_if_debug;
int rv;
double query_time;
size_t resolv_len = 0;
char *resolv_txt;
/* prefix + space + nameserver + carriage return + null termination */
resolv_len = strlen(RESOLV_TXT_PREFIX) + strlen(ns) + 3;
resolv_txt = malloc(resolv_len);
snprintf(resolv_txt, resolv_len, "%s %s\n", RESOLV_TXT_PREFIX, ns);
   rv = adns_init_strcfg(&adns, flags|adns_if_debug, 0, resolv_txt);
if(rv) {
perror("adns_init");
free(resolv_txt);
return q_null;
}
#ifdef __WIN32__
gettimeofday_hires(&start, NULL);
#else
gettimeofday(&start, NULL);
#endif
rv = adns_submit(adns, "www.google.com", adns_r_a, 0, NULL, &query);
if(rv) {
perror("adns_submit");
adns_finish(adns);
free(resolv_txt);
return q_null;
}
rv = adns_wait(adns, &query, &answer, NULL);

#ifdef __WIN32__
gettimeofday_hires(&end, NULL);
#else
gettimeofday(&end, NULL);
#endif
if(rv) {
perror("adns_wait");
adns_finish(adns);
free(resolv_txt);
return q_null;
}
if(answer->status == adns_s_ok) {
query_time = tv_diff(&start, &end);
} else {
if(answer->status == adns_s_timeout) {
query_time = -2.0;
} else {
query_time = -1.0;
}
}
q_res.retries = adns_query_retries(query);
q_res.query_time = query_time;

adns_finish(adns);
free(resolv_txt);
return q_res;
}
double standard_deviation(int nelements, double avg, double *data) {
double square_sum = 0.0;
double diff;
int i;
for(i=0; i < nelements; i++) {
/* ignore data points of -1.0 which indicates a retry/retries were
necessary, and we're just reporting that as a "drop" */
if(data == -1.0) {
continue;
}
diff = data - avg;
square_sum += pow(diff, 2);
}
return sqrt(square_sum/nelements);
}
#ifdef __WIN32__
int gettimeofday_hires(struct timeval *tv, struct timezone *tz) {
LARGE_INTEGER   t;
FILETIME   f;
double     microseconds;
static LARGE_INTEGER offset;
static double   frequencyToMicroseconds;
static int    initialized = 0;
static BOOL    usePerformanceCounter = 0;
if (!initialized) {
LARGE_INTEGER performanceFrequency;
initialized = 1;
usePerformanceCounter = QueryPerformanceFrequency(&performanceFrequency);
if (usePerformanceCounter) {
QueryPerformanceCounter(&offset);
frequencyToMicroseconds = (double)performanceFrequency.QuadPart / 1000000.;
} else {
offset = getFILETIMEoffset();
frequencyToMicroseconds = 10.;
}
}
if (usePerformanceCounter) {
QueryPerformanceCounter(&t);
} else {
GetSystemTimeAsFileTime(&f);
t.QuadPart = f.dwHighDateTime;
t.QuadPart <<= 32;
t.QuadPart |= f.dwLowDateTime;
}
t.QuadPart -= offset.QuadPart;
microseconds = (double)t.QuadPart / frequencyToMicroseconds;
t.QuadPart = microseconds;
tv->tv_sec = t.QuadPart / 1000000;
tv->tv_usec = t.QuadPart % 1000000;
return (0);
}
LARGE_INTEGER getFILETIMEoffset(void) {
SYSTEMTIME s;
FILETIME f;
LARGE_INTEGER t;
s.wYear = 1970;
s.wMonth = 1;
s.wDay = 1;
s.wHour = 0;
s.wMinute = 0;
s.wSecond = 0;
s.wMilliseconds = 0;
SystemTimeToFileTime(&s, &f);
t.QuadPart = f.dwHighDateTime;
t.QuadPart <<= 32;
t.QuadPart |= f.dwLowDateTime;
return (t);
}
#endif

npr
Pro
Posts: 1,898
Thanks: 119
Fixes: 9
Registered: ‎21-01-2013

Re: Ongoing DNS Issues? Timeouts....

Best I can tell from the code:
It looks as though ns-bench queries www.google.com 5 times just to prime the resolver cache (PRE_ITERATIONS), these 5 queries are not taken in to account for the result.
It then queries www.google.com 5 more time (QUERY_ITERATIONS), it's only these 5 queries used to provide the result.
Is this consistent with your test showing 10 queries?
Think I'll stay with DNSBenchmark Wink
houlton23
Grafter
Posts: 268
Registered: ‎22-05-2011

Re: Ongoing DNS Issues? Timeouts....

I'd love to know what actually happened, unless I've already missed the explanation. (I have looked for one - couldn't find it)
Unless of course, you've been told to shush by Mr Lawyer... Smiley
30FTTC06
Pro
Posts: 2,286
Thanks: 108
Fixes: 4
Registered: ‎18-02-2013

Re: Ongoing DNS Issues? Timeouts....

I get your point npr, but i think ns_bench is a great tool for looking for a problem quicky.
I think these are the tests DNSBench runs by the way.
[tt]Queries: 0 new, 200 total                                                                          Sat Mar  8 22:01:53 2014
Replies: 0 new, 200 total
Query Name    Count      %  cum%
---------- --------- ------ ------
com              161  80.5  80.5
jp                6    3.0  83.5
uk                6    3.0  86.5
de                6    3.0  89.5
org                6    3.0  92.5
net                3    1.5  94.0
ca                3    1.5  95.5
it                3    1.5  97.0
in                3    1.5  98.5
fr                3    1.5  100.0
Queries: 0 new, 200 total                                                                          Sat Mar  8 22:04:13 2014
Replies: 0 new, 200 total
Source      Query Name                                    Count      %  cum%
------------ ------------------------------------------ --------- ------ ------
192.168.0.30 www.livejournal.com ;                               2    1.0    1.0
192.168.0.30 www.soso.com ;                                     2    1.0    2.0
192.168.0.30 www.ku6.com ;                                       2    1.0    3.0
192.168.0.30 www.mediafire.com ;                                 2    1.0    4.0
192.168.0.30 www.tagged.com ;                                   2    1.0    5.0
192.168.0.30 www.about.com ;                                     2    1.0    6.0
192.168.0.30 www.globo.com ;                                     2    1.0    7.0
192.168.0.30 www.apple.com ;                                     2    1.0    8.0
192.168.0.30 www.youku.com ;                                     2    1.0    9.0
192.168.0.30 www.naver.com ;                                     2    1.0  10.0
192.168.0.30 www.vmn.net ;                                       2    1.0  11.0
192.168.0.30 www.sohu.com ;                                     2    1.0  12.0
192.168.0.30 www.conduit.com ;                                   2    1.0  13.0
192.168.0.30 www.wordpress.com ;                                 2    1.0  14.0
192.168.0.30 www.flickr.com ;                                   2    1.0  15.0
192.168.0.30 www.dailymotion.com ;                               2    1.0  16.0
192.168.0.30 www.ebay.com ;                                     2    1.0  17.0
192.168.0.30 www.google.ca ;                                     2    1.0  18.0
192.168.0.30 www.google.co.uk ;                                 2    1.0  19.0
192.168.0.30 www.craigslist.org ;                               2    1.0  20.0
192.168.0.30 www.adobe.com ;                                     2    1.0  21.0
192.168.0.30 www.aol.com ;                                       2    1.0  22.0
192.168.0.30 www.microsoft.com ;                                 2    1.0  23.0
192.168.0.30 www.google.fr ;                                     2    1.0  24.0
192.168.0.30 www.ebay.de ;                                       2    1.0  25.0
192.168.0.30 www.friendster.com ;                               2    1.0  26.0
192.168.0.30 www.bbc.co.uk ;                                     2    1.0  27.0
192.168.0.30 www.msn.com ;                                       2    1.0  28.0
192.168.0.30 www.imdb.com ;                                     2    1.0  29.0
192.168.0.30 www.google.co.jp ;                                 2    1.0  30.0
192.168.0.30 www.blogger.com ;                                   2    1.0  31.0
192.168.0.30 www.go.com ;                                       2    1.0  32.0
192.168.0.30 www.amazon.com ;                                   2    1.0  33.0
192.168.0.30 www.photobucket.com ;                               2    1.0  34.0
192.168.0.30 www.ask.com ;                                       2    1.0  35.0
192.168.0.30 www.skyrock.com ;                                   2    1.0  36.0
192.168.0.30 www.myspace.com ;                                   2    1.0  37.0
192.168.0.30 www.youtube.com ;                                   2    1.0  38.0
192.168.0.30 www.google.de ;                                     2    1.0  39.0
192.168.0.30 www.baidu.com ;                                     2    1.0  40.0
192.168.0.30 www.yahoo.com ;                                     2    1.0  41.0
192.168.0.30 www.facebook.com ;                                 2    1.0  42.0
192.168.0.30 www.wikipedia.org ;                                 2    1.0  43.0
192.168.0.30 www.yahoo.co.jp ;                                   2    1.0  44.0
192.168.0.30 www.live.com ;                                     2    1.0  45.0
192.168.0.30 www.rapidshare.com ;                               2    1.0  46.0
192.168.0.30 www.google.it ;                                     2    1.0  47.0
192.168.0.30 www.google.co.in ;                                 2    1.0  48.0
192.168.0.30 www.google.com ;                                   2    1.0  49.0
192.168.0.30 www.cnn.com ;                                       2    1.0  50.0
192.168.0.30 idr5esqqfrgwxwjuj3skdzorpf.com                    1    0.5  50.5
192.168.0.30 snmknnjxidthy5ho02qsuzz23h.soso.com                1    0.5  51.0
192.168.0.30 ntny54eucr4exhmnq5sioev4mh.com                    1    0.5  51.5
192.168.0.30 i2cbuafwqr12lyrzhlseimgxye.ku6.com                1    0.5  52.0
192.168.0.30 x2bour5w2xv5vvdzzaqq25dkla.com                    1    0.5  52.5
192.168.0.30 lpvjhpnqe5yec1ijvitw0rl2kc.livejournal.com        1    0.5  53.0
192.168.0.30 ahyatf0qzqfabc15aftwdwolrf.com                    1    0.5  53.5
192.168.0.30 ygvumcgq0mfgnqvz22qgffs1ig.mediafire.com          1    0.5  54.0
192.168.0.30 pgd45f0uuyhpjeobo4qemps2eh.com                    1    0.5  54.5
192.168.0.30 3jwp1gjul2tadng2nptcujiarg.com                    1    0.5  55.0
192.168.0.30 ssfdvgoxlljvsm1v2vsw1zvzmb.com                    1    0.5  55.5
192.168.0.30 a0my0lxsgrdn2nvvkzr2ftkxkg.tagged.com              1    0.5  56.0
192.168.0.30 kimcqcgvmctwuk0skysgnk1qcd.about.com              1    0.5  56.5
192.168.0.30 ukmc1t2r4aaz4exgzxsojzccmc.globo.com              1    0.5  57.0
192.168.0.30 ymyuzrpvxnsp0cwymdt0bmgbih.com                    1    0.5  57.5
192.168.0.30 vs1ymg1rllciljxpryqax0jmbc.com                    1    0.5  58.0
192.168.0.30 x5v4gyst0c0c1q4gliq04rekmc.com                    1    0.5  58.5
192.168.0.30 hzdktiyrver2fmtsfstaqmdpmc.vmn.net                1    0.5  59.0
192.168.0.30 ctxgnhbsr0dzyhvisuswbsuo0c.apple.com              1    0.5  59.5
192.168.0.30 clrjuphwvm04faj3o4rmcinjih.com                    1    0.5  60.0
192.168.0.30 nmfh0vrvetzhqpe2ujqwsmqtgd.naver.com              1    0.5  60.5
192.168.0.30 fltqfxurym5gfdrgiescn0afta.com                    1    0.5  61.0
192.168.0.30 awpwhuvw0xmda34i3ps2flhrfa.sohu.com                1    0.5  61.5
192.168.0.30 o4yepwvx02kkstr5ultaudxlka.com                    1    0.5  62.0
192.168.0.30 y0vyqxatqy2jbzcfg1qinpndte.conduit.com            1    0.5  62.5
192.168.0.30 prfa5lprpcm2woht0vskqch1oa.com                    1    0.5  63.0
192.168.0.30 nsvrcskvvkmhxrm2gttisogpgc.com                    1    0.5  63.5
192.168.0.30 rkfultlrg2hdixq15mtgwonc1d.wordpress.com          1    0.5  64.0
192.168.0.30 wpuy0eix3kykw23tygse4bzlpd.google.it              1    0.5  64.5
192.168.0.30 snnukd4xo1xzs1skb3talbbt1b.aol.com                1    0.5  65.0
192.168.0.30 uprptcqtjyldj0ivt3sq0fd53g.com                    1    0.5  65.5
192.168.0.30 4kzgpa4xnt2e14zxu3rokwu0sa.com                    1    0.5  66.0
192.168.0.30 55hk241q00kwanv0snqinzt0uc.dailymotion.com        1    0.5  66.5
192.168.0.30 qcapylewiuzwlkbushsg2kqt0h.google.fr              1    0.5  67.0
192.168.0.30 a4ewqdoxyfdubocdk0qspmjh4b.com                    1    0.5  67.5
192.168.0.30 s33qe2qu4vx5qdox0rqccpflbd.com                    1    0.5  68.0
192.168.0.30 iuizfovtz41jcnv0bvsmpd1jac.com                    1    0.5  68.5
192.168.0.30 la52unbugduptn5xyxs4ytdmje.com                    1    0.5  69.0
192.168.0.30 2cr0h1pxin0rihoazcrookzyob.ebay.com                1    0.5  69.5
192.168.0.30 apbcvu0r1k0c2xngdvre1ueifg.com                    1    0.5  70.0
192.168.0.30 dxzspv2whh1e1ri5yarch35jie.craigslist.org          1    0.5  70.5
192.168.0.30 o5oaqqfwdfm33bm4m4rgfg5rsa.yahoo.co.jp            1    0.5  71.0
192.168.0.30 41xz1a4tffsgvgaltxt2ijuswb.com                    1    0.5  71.5
192.168.0.30 atcdrbqr5vklgizvinr2cwlonf.google.ca              1    0.5  72.0
192.168.0.30 hjzjx3oxrr4ph0tz5btusmipvc.com                    1    0.5  72.5
192.168.0.30 q04kdeftxc11m5og40qcrf45ec.adobe.com              1    0.5  73.0
192.168.0.30 q5e4ec2ul53kbq1jruqugai3fb.rapidshare.com          1    0.5  73.5
192.168.0.30 2tgefydq51qcxujj2irw4vd3he.com                    1    0.5  74.0
192.168.0.30 uuua0dbv0mu0xtveuutugvsfsh.com                    1    0.5  74.5
192.168.0.30 m2q4gk4q25bybjbpddq4naedda.friendster.com          1    0.5  75.0
192.168.0.30 ypkwnlstnjpuqi1wqhskm12yaa.ebay.de                1    0.5  75.5
192.168.0.30 ukny5yms2bsmifvyeptcjv3npg.go.com                  1    0.5  76.0
192.168.0.30 3pruyq0xuapltd0io0t0xecsqb.com                    1    0.5  76.5
192.168.0.30 amktcwsqmo0q0pzbmrqo45evnh.google.de              1    0.5  77.0
192.168.0.30 sjw2uzrubje1qgqz3wtydcmu3g.com                    1    0.5  77.5
192.168.0.30 5yvhayiw543ltj35oitq3jlajg.com                    1    0.5  78.0
192.168.0.30 4djucdbxbquluqdsyqraonxqbb.myspace.com            1    0.5  78.5
192.168.0.30 s3xo2rdv2rzhyb43hvsowyonsb.wikipedia.org          1    0.5  79.0
192.168.0.30 j12hmcix1z1zv4kmuwtwgvabec.msn.com                1    0.5  79.5
192.168.0.30 5p0zqvisrxyhi0cutuselg0z0f.com                    1    0.5  80.0
192.168.0.30 4bzmvr1xpf02kyicefqqgpsr1e.com                    1    0.5  80.5
192.168.0.30 odj5zv5whaqozq0z4wsoabpkde.com                    1    0.5  81.0
192.168.0.30 n034oeuvfooyxjeqvkr40o3uhh.com                    1    0.5  81.5
192.168.0.30 pdvvtsqxxqm5sgiv21twxy0ovf.google.co.jp            1    0.5  82.0
192.168.0.30 qkshunxqtbugdcovrtrcv1noxb.facebook.com            1    0.5  82.5
192.168.0.30 1fgychyrhfgrgevq24tsga5e2f.com                    1    0.5  83.0
192.168.0.30 4ntxso1xksw4hbrbo0rcwfqcba.google.co.in            1    0.5  83.5
192.168.0.30 hlfm5zaqmr2bx3k2fsswez1t5f.live.com                1    0.5  84.0
192.168.0.30 bh23x4wuiayjrsx1pzsih5c3ih.com                    1    0.5  84.5
192.168.0.30 w5xc4xbwfsuddxvgqaskllqilh.com                    1    0.5  85.0
192.168.0.30 vofipirvvd4kvg4hdhtsciyobf.com                    1    0.5  85.5
192.168.0.30 1gdi10hxrjeqy0j1sytedxmorc.blogger.com            1    0.5  86.0
192.168.0.30 n0eml32tn24cs4fpcequqbqrmd.com                    1    0.5  86.5
192.168.0.30 4rs1tx5wt42rwzys3gtkwazsxb.com                    1    0.5  87.0
192.168.0.30 wlennv3ulgv233husetcc4knyd.ask.com                1    0.5  87.5
192.168.0.30 5auydmfq1eghztym41tsjy3w2g.photobucket.com        1    0.5  88.0
192.168.0.30 kltbnmjqmbw4ljw1dnqcxsxnwa.com                    1    0.5  88.5
192.168.0.30 3oty4varxf2wu44ejar0jl34ub.baidu.com              1    0.5  89.0
192.168.0.30 r5i5kmwvdeswidum4ar2lsn55g.amazon.com              1    0.5  89.5
192.168.0.30 wpql1kaxzxkdlfeo12rybuq05c.skyrock.com            1    0.5  90.0
192.168.0.30 uh0cpaqwzyzs5temq3twe1zqcf.com                    1    0.5  90.5
192.168.0.30 oehkc0tsd2ednucmsaqiybrgse.com                    1    0.5  91.0
192.168.0.30 a4z4zpiv20pj2k4svtquqsl4qe.yahoo.com              1    0.5  91.5
192.168.0.30 xw0yhpvs5dvd13ozkuqofwlahc.google.com              1    0.5  92.0
192.168.0.30 cyxqy0xtsxppzn121esyp5rygb.com                    1    0.5  92.5
192.168.0.30 0lfsi2fxr2o2vwx0txtmbqht1c.com                    1    0.5  93.0
192.168.0.30 hlkmhsuqu0fhnynntmtqumlrse.com                    1    0.5  93.5
192.168.0.30 n41bqydvytmwljdlvqr0h3uylc.youtube.com            1    0.5  94.0
192.168.0.30 1tcbtdmqdny3r3wbx1tufhem5d.com                    1    0.5  94.5
192.168.0.30 cpvvbtvqlf1eu2i5kqskpon2dh.bbc.co.uk              1    0.5  95.0
192.168.0.30 hcmmthyw422hftptwfrerwq4wg.imdb.com                1    0.5  95.5
192.168.0.30 5glda4lrjbfi1w2jhxqg1bu0se.flickr.com              1    0.5  96.0
192.168.0.30 islce3ax1rddx12x02si1j4a4f.com                    1    0.5  96.5
192.168.0.30 pcxrxxwvzesbwzptgjq4yijl2c.com                    1    0.5  97.0
192.168.0.30 dmqxaydsolzxyjrqjmrwook2wd.youku.com              1    0.5  97.5
192.168.0.30 dxjgae0remkyceqbuxsobdtuid.com                    1    0.5  98.0
192.168.0.30 dcmizmgvtqt1zcps2ase4e2l2g.google.co.uk            1    0.5  98.5
192.168.0.30 dg022peq0hmjpyjj1mt0cjjqth.com                    1    0.5  99.0
192.168.0.30 nq4be0tvnl3vqllilqq21rasvd.microsoft.com          1    0.5  99.5
192.168.0.30 1rqooaevvg1qkpul1bqs0bdu3a.cnn.com                1    0.5  100.0
[/tt]
npr
Pro
Posts: 1,898
Thanks: 119
Fixes: 9
Registered: ‎21-01-2013

Re: Ongoing DNS Issues? Timeouts....

Thanks, the first 50 are something like I expected.
Haven't a clue what the next 100 are about, do you have any ideas?
Edit:
I'm guessing the second 100 are:-
a)
50 names with 26 randomly generated characters in front.
This will guarantee a name not in the cache.
b)
50 .com with 26 randomly generated characters in front.
This will be what Gibson calls the DotCom test.
ie querying the ?.gtld-servers.net resolvers.
PS
Just done another DNSbenchmark test and everything is now good.
jelv
Seasoned Hero
Posts: 26,785
Thanks: 971
Fixes: 10
Registered: ‎10-04-2007

Re: Ongoing DNS Issues? Timeouts....

I'm having a problem with DNSBench. I'm trying to configure it to test all the servers I'm currently using but when I try to add some of them the Add button stays disabled.
If this is a limitation of DNSBench, is there an alternative that does work?
jelv (a.k.a Spoon Whittler)
   Why I have left Plusnet (warning: long post!)   
Broadband: Andrews & Arnold Home::1 (FTTC 80/20)
Line rental: Pulse 8 Home Line Rental (£14.40/month)
Mobile: iD mobile (£4/month)
Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

Re: Ongoing DNS Issues? Timeouts....

kelly mentioned white pages http://www.southside.scot.nhs.uk/
to me currently looks like the attached on pcl-ag04
FTTP 500 regrade from Tues 28th November