BALUG-Admin August 2016

balug-admin@lists.balug.org

2 participants
3 discussions

Re: [BALUG-Admin] (forw) AXFR failures from 198.144.194.238
by Rick Moen 26 Aug '16

26 Aug '16

Two days ago, I wrote: > I notice ns1.linuxmafia.com is still in the authoritative roster for > domain balug.org. > > I notice ns1.linuxmafia.com is NOT any longer in the authoritative > roster for domain sf-lug.org. It was the other way around (sorry, edit error). ns1.linuxmafia.com is NOT in the authoritative roster for domain balug.org. Specifics were in the same message: > $ whois balug.org | grep '^Name Server' > Name Server: NS1.DREAMHOST.COM > Name Server: NS2.DREAMHOST.COM > Name Server: NS3.DREAMHOST.COM > $ whois sf-lug.org | grep '^Name Server' > Name Server: NS2.HE.NET > Name Server: NS3.HE.NET > Name Server: NS1.LINUXMAFIA.COM > Name Server: NS4.HE.NET > Name Server: NS.PRIMATE.NET > Name Server: NS5.HE.NET > $ whois sf-lug.com | grep '^Name Server' > Name Server: ns2.he.net > Name Server: ns3.he.net > Name Server: ns.primate.net > Name Server: ns4.he.net > Name Server: ns5.he.net > Name Server: ns1.linuxmafia.com > $ Which is still the case today. So, getting back to my point (now that I'm back from Kansas City): _Why_ should ns1.linuxmafia.com be doing secondary nameservice, given that you aren't including it in the authoritative list? That's kind of pointless. Please advise. Thanks.

2 5

Master nameserver offline again?
by Rick Moen 25 Aug '16

25 Aug '16

----- Forwarded message from logcheck system account <logcheck(a)linuxmafia.com> ----- Date: Thu, 25 Aug 2016 00:02:02 -0700 From: logcheck system account <logcheck(a)linuxmafia.com> To: root(a)linuxmafia.com Subject: linuxmafia.com 2016-08-25 00:02 System Events System Events =-=-=-=-=-=-= Aug 24 23:12:07 linuxmafia named[1064]: zone balug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) Aug 24 23:12:07 linuxmafia named[1064]: zone balug.org/IN: Transfer started. Aug 24 23:12:28 linuxmafia named[1064]: transfer of 'balug.org/IN' from 198.144.194.238#53: failed to connect: timed out Aug 24 23:12:28 linuxmafia named[1064]: transfer of 'balug.org/IN' from 198.144.194.238#53: Transfer completed: 0 messages, 0 records, 0 bytes, 21.000 secs (0 bytes/sec) Aug 24 23:14:03 linuxmafia named[1064]: zone sf-lug.com/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) Aug 24 23:16:12 linuxmafia named[1064]: zone sf-lug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) Aug 24 23:39:12 linuxmafia named[1064]: zone e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) Aug 24 23:39:12 linuxmafia named[1064]: zone e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN: Transfer started. Aug 24 23:39:33 linuxmafia named[1064]: transfer of 'e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN' from 198.144.194.238#53: failed to connect: timed out Aug 24 23:39:33 linuxmafia named[1064]: transfer of 'e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN' from 198.144.194.238#53: Transfer completed: 0 messages, 0 records, 0 bytes, 21.000 secs (0 bytes/sec) Aug 24 23:39:41 linuxmafia named[1064]: zone balug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) ----- End forwarded message -----

2 3

AXFR failures from 198.144.194.238
by Rick Moen 23 Aug '16

23 Aug '16

(Greetings from MidAmeriCon II in Kansas City.) IP address 198.144.194.238 appears to be (or have been) the master nameserver for several domains... zone balug.org zone e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa zone sf-lug.org ...for which ns1.linuxmafia.com has been doing slave nameservice at your request. Today, I notice I'm getting AXFR problems: Aug 22 11:15:19 linuxmafia named[11693]: zone balug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) Aug 22 11:15:19 linuxmafia named[11693]: zone balug.org/IN: Transfer started. Aug 22 11:15:40 linuxmafia named[11693]: transfer of 'balug.org/IN' from 198.144.194.238#53: failed to connect: timed out Aug 22 11:15:40 linuxmafia named[11693]: transfer of 'balug.org/IN' from 198.144.194.238#53: Transfer completed: 0 messages, 0 records, 0 bytes, 21.000 secs (0 bytes/sec) Aug 22 11:21:30 linuxmafia named[11693]: zone e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) Aug 22 11:40:34 linuxmafia named[11693]: zone balug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) Aug 22 11:40:34 linuxmafia named[11693]: zone balug.org/IN: Transfer started. Aug 22 11:40:55 linuxmafia named[11693]: transfer of 'balug.org/IN' from 198.144.194.238#53: failed to connect: timed out Aug 22 11:40:55 linuxmafia named[11693]: transfer of 'balug.org/IN' from 198.144.194.238#53: Transfer completed: 0 messages, 0 records, 0 bytes, 20.999 secs (0 bytes/sec) Aug 22 11:45:53 linuxmafia named[11693]: zone sf-lug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0) I notice that 198.144.194.238 no longer responds to ping. I notice that auth namservers for the three domains no longer include one that resolves to IP 198.144.194.238. I notice ns1.linuxmafia.com is still in the authoritative roster for domain balug.org. I notice ns1.linuxmafia.com is NOT any longer in the authoritative roster for domain sf-lug.org. Accordingly, I am switching off slave nameservice for the three cited domains at this time. Please advise if you'd like me to resume slave nameservice for any of them, and from what master nameserver IP for each.

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

BALUG-Admin August 2016