Nameserver ns0.balug.org responds to ping, responds to DNS queries,
_but_ refuses AXFR request for zone balug.org from slave nameserver
ns1.linuxmafia.com. (Below mail from logcheck shows the first
appearance of refusal in the logs; this behaviour is still ongoing.)
[rick@linuxmafia]
~ $ dig -t axfr balug.org @96.86.170.229
;; Connection to 96.86.170.229#53(96.86.170.229) for balug.org failed:
connection refused.
[rick@linuxmafia]
~ $
----- Forwarded message from logcheck system account <logcheck(a)linuxmafia.com> -----
Date: Thu, 16 Jan 2020 12:02:01 -0800
From: logcheck system account <logcheck(a)linuxmafia.com>
To: root(a)linuxmafia.com
Subject: linuxmafia.com 2020-01-16 12:02 System Events
System Events
=-=-=-=-=-=-=
Jan 16 11:33:15 linuxmafia named[4620]: client 96.86.170.229#6229: received notify for zone 'balug.org'
Jan 16 11:33:15 linuxmafia named[4620]: zone balug.org/IN: Transfer started.
Jan 16 11:33:15 linuxmafia named[4620]: transfer of 'balug.org/IN' from 96.86.170.229#53: failed to connect: connection refused
Jan 16 11:33:15 linuxmafia named[4620]: transfer of 'balug.org/IN' from 96.86.170.229#53: Transfer completed: 0 messages, 0 records, 0 bytes, 0.028 secs (0 bytes/sec)
----- End forwarded message -----
So, I'll be changing ISP (at least for IPv4) ...
that'll mean new IPs for IPv4 ... most notably for these [L]UG domains
(and in general subdomains thereof):
balug.orgsf-lug.orgsflug.orgsflug.comsflug.netsf-lug.netsf-lug.comberkeleylug.comberkeleylug.org
A bit more generally:
By not later than end of 2019-12-19, these IPv4 IPs (range) will be
"going away"/changing:
198.144.194.232/29 198.144.194.232 - 198.144.194.239
198.144.194.232
198.144.194.233
198.144.194.234
198.144.194.235
198.144.194.236
198.144.194.237
198.144.194.238
198.144.194.239
At present, my IPv6 is provided from another ISP (tunneled via IPv4),
so I'm expecting the IPv6 IPs will remain the same (at least through
this transition anyway).
Anyway, hopefully all these changes will happen rather to quite smoothly
... but a bit early to say. E.g., as I transition ISPs, there may be
brief(ish) period between, when temporarily neither is available.
We shall see. I'll update relevant contatct(s)/lists as/when
relevant and appropriate and I'm reasonably able to do so.
Hopefully I can minimize any "user facing" impact ... if I'm
reasonably lucky, may be able to do it quite seamlessly, with
essentially no impact to "users" ... we shall see.
references/excerpts:
http://linuxmafia.com/pipermail/conspire/2019-November/009966.html
The BALUG Wiki is "temporarily" (mostly) down for a bit.
I'm integrating WordPress (not for BALUG, but for BerkeleyLUG)
on same host & server ... that required web server to use newer
php version to work with WordPress ... which has "temporarily"
(mostly) broken the BALUG Wiki.
Index pages themselves still appear to work, e.g.:
https://www.wiki.balug.org/wiki/doku.php?do=index&idx=balug
but contents pages, e.g.:
https://www.wiki.balug.org/wiki/doku.php?id=balug:cds_and_images_etc
presently fail.
I'm hoping/presuming it's just some config bit(s) I need to track down
and correct/adjust, then all should be fine again.