Anyone Else Had A DNS Faff This Weekend?

GunJack

As per the title, had a couple of DNS servers stop working this weekend, caused ructions with the Mini-Guns and online gaming :mad: At least 3 went offline, one OpenDNS and a couple of TT ones... TT I can understand, but OpenDNS normally rock solid.....

Fightsback

Fine here GJ, exchange or backbone issue ?

What's traceroute telling you ?

traceroute to 8.8.8.8 (8.8.8.8), 10 hops max, 60 byte packets
 1  router.asus.com (192.168.0.1)  0.767 ms  0.761 ms  1.059 ms
 2  host-89-241-200-1.as13285.net (89.241.200.1)  6.247 ms  6.957 ms  7.769 ms
 3  host-78-151-226-51.as13285.net (78.151.226.51)  9.141 ms  9.922 ms  10.867 ms
 4  host-78-151-225-100.static.as13285.net (78.151.225.100)  12.142 ms host-78-151-225-76.static.as13285.net (78.151.225.76)  13.187 ms host-78-151-226-232.as13285.net (78.151.226.232)  14.131 ms
 5  host-78-144-9-63.as13285.net (78.144.9.63)  21.742 ms host-78-144-9-75.as13285.net (78.144.9.75)  21.733 ms host-78-144-12-177.as13285.net (78.144.12.177)  24.071 ms
 6  host-78-144-10-117.as13285.net (78.144.10.117)  23.430 ms 74.125.48.13 (74.125.48.13)  25.091 ms host-78-144-10-115.as13285.net (78.144.10.115)  24.430 ms
 7  216.239.56.195 (216.239.56.195)  26.801 ms 64.233.175.223 (64.233.175.223)  21.599 ms 72.14.242.127 (72.14.242.127)  26.846 ms
 8  216.239.57.105 (216.239.57.105)  23.542 ms 216.239.54.215 (216.239.54.215)  21.927 ms 216.239.58.63 (216.239.58.63)  24.618 ms
 9  216.239.57.153 (216.239.57.153)  23.084 ms 216.239.57.109 (216.239.57.109)  12.349 ms google-public-dns-a.google.com (8.8.8.8)  14.099 ms

bod1467

Given the use of the word "had", I suspect the issue is now resolved so running a traceroute now may be of little benefit.

PS - if you try to use trace rt (without the space) in a reply the forum throws a "security error".

Fightsback

bod1467 wrote: »

Given the use of the word "had", I suspect the issue is now resolved so running a traceroute now may be of little benefit.

PS - if you try to use trace rt (without the space) in a reply the forum throws a "security error".

Ah the advantages of using 'nix commands

kwikbreaks

As it happens I was playing around with an old Pi and Runeaudio which was giving my ageing NAS a hammering. I was getting a mix of problems some of which looked like possible DNS problems but could have been my network.

After at least two reflashes of the Rune SD card and going through the finicky WiFi and NAS share setup, one (newish) router reboot as that was also suspect, then remembering that in the past that NAS has shown a strange fault where I think it floods the (Gigabit) network with junk to the point where things become pretty much unusable so rebooting that a couple of times too I finally blamed my woes on a recurrence of the BT problems from a week back.

As everything with Runeaudio and the NAS now seem stable I'm now guessing I too had DNS issues although maybe with other things going wrong too.

GunJack

thanks guys, yes I did resolve it by switching servers, re-ran becnchmarking and now on one Opal and one OpenDNS (different to the ones that went over the weekend) and all was good again... it's just annoying when they go

Robisere

Had several very quick dropouts and immediate recoveries, over Saturday and Sunday. I have recently had problems with my service from Plusnet, but these I thought were finally resolved last week. Nothing today, so I am hoping I will not have to nag them again! Plusnet, I have to say, always respond positively if I do have a problem. They carry out line tests, email me to check results in their "Member Centre" site and fully explain everything. In the last year, I have had 3 engineer visits from BT in search of solutions, cost me nothing.

My problem is that I live in a rural location and our line is at the end of the FTTC service. 7 Mbps Down, 0.55 Up.

Fightsback

GunJack wrote: »

thanks guys, yes I did resolve it by switching servers, re-ran becnchmarking and now on one Opal and one OpenDNS (different to the ones that went over the weekend) and all was good again... it's just annoying when they go

Hmm did notice an update today to libidn (Support for Internationalized Domain Names) in Suse, don't know if 'nix DNS servers make use of this library and perhaps they had downtime for patching.

* bnc#990189 CVE-2015-8948 CVE-2016-6262
* bnc#990190 CVE-2016-6261
* bnc#990191 CVE-2016-6263
* libidn: Fix out-of-bounds stack read in idna_to_ascii_4i.
* idn: Solve out-of-bounds-read when reading one zero byte as input.
* libidn: stringprep_utf8_nfkc_normalize reject invalid UTF-8.

http://www.usinglinux.org/dns/libidn.html