[sf-lug] DNS: sf-lug.com. "down": NS 208.96.15.252 "broken"

[Michael Paoli]

also BCCed to out-of-band SF-LUG admin alias; some
earlier communications on the problem also sent to those folks and
Rick Moen

Would appear 208.96.15.252 is quite broken as NS for sf-lug.com.,
and apparently
(http://linuxmafia.com/pipermail/sf-lug/2009q1/006426.html)
the other NS for sf-lug.com. - 198.144.195.186 - is
slave for sf-lug.com. of only master 208.96.15.252,
thus once 208.96.15.252 fails, sooner or later (based upon
zone expire, if nothing else) 198.144.195.186
will also in turn "fail" (properly refuse to stop providing
answers) for sf-lug.com.

Note that clearly 208.96.15.252 also refuses TCP - both TCP and
UDP need to be working properly on port 53 for DNS to function
properly.

$ dig @208.96.15.252 -t A sf-lug.com. +short

; <<>> DiG 9.2.4 <<>> @208.96.15.252 -t A sf-lug.com. +short
;; global options:  printcmd
;; connection timed out; no servers could be reached
$ dig @208.96.15.252 -t A sf-lug.com. +short +tcp
;; Connection to 208.96.15.252#53(208.96.15.252) for sf-lug.com.  
failed: connection refused.
$ tcptraceroute -n 208.96.15.252 53
Selected device eth0, address 198.144.194.236, port 40463 for outgoing packets
Tracing the path to 208.96.15.252 on TCP port 53 (domain), 30 hops max
  1  198.144.194.233  10.334 ms  11.012 ms  9.709 ms
  2  209.237.228.169  11.087 ms  10.834 ms  12.342 ms
  3  209.237.224.25  13.214 ms  10.333 ms  10.593 ms
  4  207.7.129.73  10.590 ms  11.085 ms  10.695 ms
  5  207.7.159.54  11.966 ms  11.831 ms  14.590 ms
  6  206.223.116.86  12.579 ms  12.205 ms  11.843 ms
  7  64.125.27.90  12.216 ms  12.334 ms  12.216 ms
  8  64.124.196.6  13.088 ms  12.707 ms  13.091 ms
  9  208.96.31.6  14.465 ms  13.708 ms  12.841 ms
10  208.96.15.252 [closed]  13.837 ms  13.704 ms  13.842 ms
$