cancel
Showing results for 
Search instead for 
Did you mean: 

DNS

VileReynard
All Star
Posts: 11,175
Thanks: 303
Fixes: 11
Registered: ‎01-09-2007

DNS

88 REPLIES
shalom2010
Grafter
Posts: 977
Registered: ‎28-12-2012

Re: DNS

Well I'm not sure what happened at 10 am, but look at my graph & table! (No disconnections here at that time)
VileReynard
All Star
Posts: 11,175
Thanks: 303
Fixes: 11
Registered: ‎01-09-2007

Re: DNS

I can beat some of those numbers!

Community Veteran
Posts: 1,841
Thanks: 103
Fixes: 6
Registered: ‎21-01-2013

Re: DNS

At present DNS Benchmark is reporting plusnet's DNS resolver as "not replying to DNS queries".
https://www.grc.com/dns/benchmark.htm
Strangely dig and nslookup are using plusnet's DNS ok, or at least ok for the lookups I've tested.
I assume DNS Benchmark is failing to get a reply for it's first test lookup and then labeling plusnet's DNS as not replying.
Community Veteran
Posts: 5,210
Thanks: 493
Fixes: 22
Registered: ‎10-06-2010

Re: DNS

I was just going to start another thread about DNS, after I tried to use the whois command, but Plusnet's DNS server's failed to resolve whois.ripe.net.
[tt]$ whois 212.159.6.9
[Querying whois.ripe.net]
[whois.ripe.net: Name or service not known]
[Unable to connect to remote host][/tt]
[tt]$ dig @212.159.6.9 whois.ripe.net
; <<>> DiG 9.9.2-rl.028.23-P2-RedHat-9.9.2-10.P2.fc18 <<>> @212.159.6.9 whois.ripe.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15098
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;whois.ripe.net. IN A
;; Query time: 24 msec
;; SERVER: 212.159.6.9#53(212.159.6.9)
;; WHEN: Fri May 17 22:09:29 2013
;; MSG SIZE  rcvd: 32
[/tt]
A dig command with +trace manages to find the IP address of whois.ripe.net
[tt]$ dig @212.159.6.9 whois.ripe.net +trace
; <<>> DiG 9.9.2-rl.028.23-P2-RedHat-9.9.2-10.P2.fc18 <<>> @212.159.6.9 whois.ripe.net +trace
; (1 server found)
;; global options: +cmd
. 85366 IN NS f.root-servers.net.
. 85366 IN NS l.root-servers.net.
. 85366 IN NS m.root-servers.net.
. 85366 IN NS k.root-servers.net.
. 85366 IN NS a.root-servers.net.
. 85366 IN NS b.root-servers.net.
. 85366 IN NS j.root-servers.net.
. 85366 IN NS g.root-servers.net.
. 85366 IN NS e.root-servers.net.
. 85366 IN NS h.root-servers.net.
. 85366 IN NS c.root-servers.net.
. 85366 IN NS d.root-servers.net.
. 85366 IN NS i.root-servers.net.
;; Received 449 bytes from 212.159.6.9#53(212.159.6.9) in 534 ms
net. 172800 IN NS i.gtld-servers.net.
net. 172800 IN NS l.gtld-servers.net.
net. 172800 IN NS j.gtld-servers.net.
net. 172800 IN NS m.gtld-servers.net.
net. 172800 IN NS d.gtld-servers.net.
net. 172800 IN NS a.gtld-servers.net.
net. 172800 IN NS c.gtld-servers.net.
net. 172800 IN NS k.gtld-servers.net.
net. 172800 IN NS f.gtld-servers.net.
net. 172800 IN NS e.gtld-servers.net.
net. 172800 IN NS h.gtld-servers.net.
net. 172800 IN NS g.gtld-servers.net.
net. 172800 IN NS b.gtld-servers.net.
net. 86400 IN DS 35886 8 2 7862B27F5F516EBE19680444D4CE5E762981931842C465F00236401D 8BD973EE
net. 86400 IN RRSIG DS 8 1 86400 20130524000000 20130516230000 20580 . mBqID80i7D2YWSt7alUDzYKsv3JIYs5aWMpfmVUIQcM57OZB1DnK2K97 zv+DUbYG3kfKlru9nsJMgh/1zRNiFxRGO3WGPiNUNaJFnpFRKMck0z1g 22o2AUjwjfROMRsbRVO6KZwujd7Hftj5XJgVTvvheGInmMP8n/11hjUm C4s=
;; Received 735 bytes from 192.112.36.4#53(192.112.36.4) in 1449 ms
ripe.net. 172800 IN NS ns3.nic.fr.
ripe.net. 172800 IN NS sec1.apnic.net.
ripe.net. 172800 IN NS sec3.apnic.net.
ripe.net. 172800 IN NS tinnie.arin.net.
ripe.net. 172800 IN NS sns-pb.isc.org.
ripe.net. 172800 IN NS pri.authdns.ripe.net.
ripe.net. 86400 IN DS 60338 5 2 61D99D98D0C374C1157F73282DB3E29E61E365DD9EBA435802D27A69 847C24FC
ripe.net. 86400 IN DS 60338 5 1 1CB13971FC7D4DF7CB3C6EB82DF0868687FE6371
ripe.net. 86400 IN RRSIG DS 8 2 86400 20130522041735 20130515030735 3317 net. K//DC//AS5ARtV7JjBnvfOlxqHDtzGJEwAP2qMxY5pRVcXXe2HKJS52G goJkTGMLXAgSZXBOAPdij7u93hAMgfD1ylyWUXE3q/jBWzK2cRuEo/gX rOWhAPFLeebWtSnbzvdtIozva8zYaSRCIXkZglwXKJlOk+1DFCSo6LNQ WJ0=
;; Received 614 bytes from 192.26.92.30#53(192.26.92.30) in 20144 ms
whois.ripe.net. 21600 IN A 193.0.6.135
whois.ripe.net. 21600 IN RRSIG A 5 3 21600 20130616100309 20130517090309 36246 ripe.net. GghuArQud+5X8nkAwLKQ8F6WeXI5UMcg3fWNa0gCXi1g83LCjVfdo1P/ bnPyBsTtur+nZ274ndmCWcP0joh9Pp6dIQQ4YQziqM9plP2g5K2ZknMU NhweqUudclUiWy3Vbreb78fj6+p+09jVePAP++vfvSNmE/g0PigLiaMC 69s=
;; Received 227 bytes from 202.12.28.140#53(202.12.28.140) in 278 ms
[/tt]
Community Veteran
Posts: 5,210
Thanks: 493
Fixes: 22
Registered: ‎10-06-2010

Re: DNS

Also, Plusnet's DNS servers are not replying at all (timing out) to a query for isc.org.
VileReynard
All Star
Posts: 11,175
Thanks: 303
Fixes: 11
Registered: ‎01-09-2007

Re: DNS

Works for me.
My DNS settings are 212.159.6.9 and 8.8.8.8

Community Veteran
Posts: 2,286
Thanks: 109
Fixes: 4
Registered: ‎18-02-2013

Re: DNS

Community Veteran
Posts: 6,319
Thanks: 86
Fixes: 3
Registered: ‎08-01-2008

Re: DNS

Looks like something happened at 10AM
Call me 'w23'
At any given moment in the universe many things happen. Coincidence is a matter of how close these events are in space, time and relationship.
Opinions expressed in forum posts are those of the poster, others may have different views.
Community Veteran
Posts: 5,472
Thanks: 292
Fixes: 4
Registered: ‎11-08-2007

Re: DNS

Community Veteran
Posts: 1,841
Thanks: 103
Fixes: 6
Registered: ‎21-01-2013

Re: DNS

@ejs,
Well spotted.
Plusnet's DNS is still failing to find ripe.net yet the root servers resolve it OK.
DNS Benchmark is still reporting PN's DNS as "not replying to dns queries".
There's something not right with the dns resolvers. Being new here I'll be interested to see how long before PN acknowledge this and fix the problem. At my previous ISP it would not have been quick, hoping they do better here Wink
pwatson
Rising Star
Posts: 2,468
Thanks: 8
Fixes: 1
Registered: ‎26-11-2012

Re: DNS

Quote from: npr
DNS Benchmark is still reporting PN's DNS as "not replying to dns queries".

Perhaps they're set to only answer lookups from PlusNet IP ranges?
Community Veteran
Posts: 1,841
Thanks: 103
Fixes: 6
Registered: ‎21-01-2013

Re: DNS

After a bit of digging, DNS Benchmark uses the lookup for ics.org to check if a resolver is responding.
It would appear plusnets DNS is not resolving ics.org which is why DNS Benchmark says their DNS is not working.
eg:
Using PN's DNS
nslookup isc.org 212.159.6.9
Server:  UnKnown
Address:  212.159.6.9
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out
Using Google DNS
nslookup isc.org 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8
Non-authoritative answer:
Name:    isc.org
Addresses:  2001:4f8:0:2::d
          149.20.64.42
That together with ejs find of ripe.net not being found by PN's DNS looks conclusive proof some thing is wrong..
h_milsom
Grafter
Posts: 49
Registered: ‎04-08-2007

Re: DNS

Guys - which DNS do you suggest for me as a newcomer to PN? At present I'm using OpenDNS
208.67.222.222
208.67.222.220
Should I be using the PN recommended?
Kind Regards
Hugh
Community Veteran
Posts: 5,472
Thanks: 292
Fixes: 4
Registered: ‎11-08-2007

Re: DNS

@'h_milsom' -
If you are using OpenDNS for URL/content filtering then stick with OpenDNS, or maybe use Norton DNS as a backup.
If you just want fast and reliable DNSes then I would keep one of your existing OpenDNS settings, and use Google DNS (8.8.8.8 or 8.8.4.4) as the other.  That way if there is a temporary problem with OpenDNS then your system will use Google DNS as a backup, and you will still be able to use the internet.