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.
From: "Rick Moen" rick@linuxmafia.com Subject: Re: [BALUG-Admin] (forw) AXFR failures from 198.144.194.238 Date: Wed, 24 Aug 2016 01:19:28 -0700
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 $
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.
Your option on balug.org., to be or not be slave at this time. I explained the situation earlier. Notably it's part of migration strategy off of DreamHost.Com. - but we're not there yet (still have to get the dang lists migrated). See the earlier explanation again here (now for the 3rd time ;-)) ... note particularly the bit that starts with "If you'd prefer, for balug.org, could also" ...
From: "Michael Paoli" Michael.Paoli@cal.berkeley.edu To: "Rick Moen" rick@linuxmafia.com Cc: balug-admin@lists.balug.org Subject: Re: AXFR failures from 198.144.194.238 Date: Mon, 22 Aug 2016 18:26:04 -0700
And also, more info for your notes (e.g. /etc/named.conf.local comments) further below.
references/excerpts:
From: "Rick Moen" rick@linuxmafia.com Subject: Re: AXFR failures from 198.144.194.238 Date: Mon, 22 Aug 2016 16:05:26 -0700
Quoting Michael Paoli (Michael.Paoli@cal.berkeley.edu):
Try again, and please reenable.
Done, and successful.
So, is 198.144.194.238 a 'hidden master' for domains balug.org, sf-lug.org, and sf-lug.com (providing AXFR to slave nameservers but not declared publicly authoritative)?
Let me know if so, and I'll annotate that in my /etc/named.conf.local file.
Well, yes, 198.144.194.238 is (partially?) "hidden master". I believe it is, however, well listed in the SOA origin, though ... to at least provide some clue(s): $ dig -t SOA sf-lug.org. +short ns1.sf-lug.org. jim.well.com. 1463887991 10800 3600 1209600 3600 $ dig -t SOA sf-lug.com. +short ns1.sf-lug.com. jim.well.com. 1463887991 10800 3600 1209600 10800 $ dig +short ns1.sf-lug.org. A ns1.sf-lug.org. AAAA 198.144.194.238 2001:470:1f04:19e::2 $ dig +short ns1.sf-lug.com. A ns1.sf-lug.com. AAAA 198.144.194.238 2001:470:1f04:19e::2 $ ... of course those IPv6 addreses would've been likely also unresponsive (on same host that was wedged as is also 198.144.194.238)
A reminder on the balug.org situation, as it's wee bit more complex, bit of expert - more fully context further below:
Do note, however, that at present time, balug.org is NOT (yet) Internet delegated to those IPs - I don't expect that to happen until we extricate ourselves from DreamHost.com
Also, prefer if/whenever there might be issue contacting master, that slaves don't drop merely, or quickly on account of just that, and nothing else having changed ... as that semi-defeats one of the purposes of having slaves, and also a fairly long expire time (e.g. if disaster strikes and it takes some fair while to get things in operation again - at least if DNS slaves are still operating, the situation is a bit more clear for those entities trying to figure out what's going on).
Thanks.
More full background on balug.org, from earlier:
From: "Michael Paoli" Michael.Paoli@cal.berkeley.edu To: "Rick Moen" rick@linuxmafia.com Cc: BALUG-Admin balug-admin@lists.balug.org Subject: [BALUG-Admin] DNS slaves for BALUG? :-) Date: Fri, 19 Feb 2016 03:16:35 -0800
Rick,
If you could please, and would be willing, could you cover DNS slave services for BALUG, notably these zones: e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa balug.org master(s) (all for each of the above): 198.144.194.238 2001:470:1f04:19e::2 Do note, however, that at present time, balug.org is NOT (yet) Internet delegated to those IPs - I don't expect that to happen until we extricate ourselves from DreamHost.com - however in the meantime it is maintained quite highly alike to the balug.org. DNS data on DreamHost.com - I check periodically, and only differences I'm aware of are SOA MNAME, RNAME, and often the REFRESH (I don't know where they get their REFRESH number from - it seems to vary some fair bit, with no particular discernible pattern) and I tend to keep the serial # one ahead of DreamHost.com (at least most of the time when I check/notice it). If you'd prefer, for balug.org, could also just set up as "warm standby" - verify (to-be) slaves can do AXFR pull, and put most of the configuration in place, but just don't actually activate it until DNS is fully and properly Internet delegated (or we're free from DreamHost.com and about to so delegate).
I'm presuming you could do/offer this on both ns1.linuxmafia.com. and also ns1.svlug.org.? That would be great, if you're able to.
I'm also presuming the various IP information and out-of-band communication information is still the same as when we set up slaves for sf-lug.org (plus any relevant updates received since then).
Just let me know, thanks (can also email just me directly for any bits that ought not get publicly archived, etc.).
Quoting Michael Paoli (Michael.Paoli@cal.berkeley.edu):
Your option on balug.org., to be or not be slave at this time. I explained the situation earlier. Notably it's part of migration strategy off of DreamHost.Com. - but we're not there yet (still have to get the dang lists migrated). See the earlier explanation again here (now for the 3rd time ;-)) ... note particularly the bit that starts with "If you'd prefer, for balug.org, could also" ...
OK, thanks.
What I failed to do before was add a note about that to the named.conf.local entry. I've now fixed that omission. Thank you for your indulgence.
(There's been a heck of a lot going on, and I evidently failed to read those couple'a paragraphs in your explanation on Aug. 22nd.)
Ah, good ... glad you caught that bit. :-) Yeah, I can understand heck of a lot going on. (Mom, stroke, whole bunch 'o stuff precipitated out from that ... still recovering from my 2 week anti-vacation + similar rather recently before that ... still playing catch-up and handling of miscellaneous gunk ... e.g. have a car to sell off too - and in the meantime nothin' but street parking for it - which is yet another annoying inconvenience and thing to do and keep an eye on).
From: "Rick Moen" rick@linuxmafia.com Subject: Re: [BALUG-Admin] Why_ should ns1.linuxmafia.com be doing secondary nameservice (for balug.org.), given that you aren't including it in the authoritative list? Date: Thu, 25 Aug 2016 21:55:43 -0700
Quoting Michael Paoli (Michael.Paoli@cal.berkeley.edu):
Your option on balug.org., to be or not be slave at this time. I explained the situation earlier. Notably it's part of migration strategy off of DreamHost.Com. - but we're not there yet (still have to get the dang lists migrated). See the earlier explanation again here (now for the 3rd time ;-)) ... note particularly the bit that starts with "If you'd prefer, for balug.org, could also" ...
OK, thanks.
What I failed to do before was add a note about that to the named.conf.local entry. I've now fixed that omission. Thank you for your indulgence.
(There's been a heck of a lot going on, and I evidently failed to read those couple'a paragraphs in your explanation on Aug. 22nd.)
Can also see that they're rather well maintained, in parallel, in preparation for (eventual) cutover. Except for the few explicit differences mentioned earlier: http://lists.balug.org/pipermail/balug-admin-balug.org/2016-February/002998.... The data is quite maintained in parallel: $ dig -t NS balug.org. +trace | tail -n 6
balug.org. 14400 IN NS ns2.dreamhost.com. balug.org. 14400 IN NS ns1.dreamhost.com. balug.org. 14400 IN NS ns3.dreamhost.com. ;; Received 153 bytes from 66.33.206.206#53(ns1.dreamhost.com) in 25 ms
$ dig @ns1.dreamhost.com. -t A ns1.dreamhost.com. +short 66.33.206.206 $ dig +noall +answer @ns1.balug.org. balug.org. AXFR | while read -r data; do set -- $data; echo "#$data"; [ "$3" = "IN" ] && if [ "$4" != NS ] || [ "$1" = balug.org. ]; then a=answer; else a=authority; fi; dig +noall +"$a" +norecurse @66.33.206.206 "$1" "$4"; done #balug.org. 14400 IN SOA ns1.balug.org. hostmaster.balug.org. 2016052104 20881 1800 1814400 14400 balug.org. 14400 IN SOA ns1.dreamhost.com. hostmaster.dreamhost.com. 2016052200 14596 1800 1814400 14400 #balug.org. 14400 IN A 208.97.176.67 balug.org. 14400 IN A 208.97.176.67 #balug.org. 14400 IN MX 0 mx1.sub5.homie.mail.dreamhost.com. balug.org. 14400 IN MX 0 mx1.sub5.homie.mail.dreamhost.com. balug.org. 14400 IN MX 0 mx2.sub5.homie.mail.dreamhost.com. #balug.org. 14400 IN MX 0 mx2.sub5.homie.mail.dreamhost.com. balug.org. 14400 IN MX 0 mx1.sub5.homie.mail.dreamhost.com. balug.org. 14400 IN MX 0 mx2.sub5.homie.mail.dreamhost.com. #balug.org. 14400 IN NS ns1.balug.org. balug.org. 14400 IN NS ns2.dreamhost.com. balug.org. 14400 IN NS ns1.dreamhost.com. balug.org. 14400 IN NS ns3.dreamhost.com. #balug.org. 14400 IN NS ns1.svlug.org. balug.org. 14400 IN NS ns2.dreamhost.com. balug.org. 14400 IN NS ns1.dreamhost.com. balug.org. 14400 IN NS ns3.dreamhost.com. #balug.org. 14400 IN NS ns1.dreamhost.com. balug.org. 14400 IN NS ns2.dreamhost.com. balug.org. 14400 IN NS ns1.dreamhost.com. balug.org. 14400 IN NS ns3.dreamhost.com. #balug.org. 14400 IN NS ns1.linuxmafia.com. balug.org. 14400 IN NS ns2.dreamhost.com. balug.org. 14400 IN NS ns1.dreamhost.com. balug.org. 14400 IN NS ns3.dreamhost.com. #balug.org. 14400 IN NS ns2.dreamhost.com. balug.org. 14400 IN NS ns2.dreamhost.com. balug.org. 14400 IN NS ns1.dreamhost.com. balug.org. 14400 IN NS ns3.dreamhost.com. #balug.org. 14400 IN NS ns3.dreamhost.com. balug.org. 14400 IN NS ns2.dreamhost.com. balug.org. 14400 IN NS ns1.dreamhost.com. balug.org. 14400 IN NS ns3.dreamhost.com. #_domainkey.balug.org. 14400 IN TXT "o=~; r=postmaster@balug.org" _domainkey.balug.org. 14400 IN TXT "o=~; r=postmaster@balug.org" #balug.org._domainkey.balug.org. 14400 IN TXT "k=rsa; t=y; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDR8B6uBDHCSGh2L7Z+EbboAKrkehI9vKn1Wp47w3K2H2tYBatBLVKyg9kOwFfZoAmiT04jY9U5nYpwnd7UlUxIvyZiO/TuyXu0lMn4QmLUR8YUZNcoiIHu5EOgf8TgB9sbMun+Ye/5LzKpMtsfNmOnot916yZOpUgd6aJpLp6tHQIDAQAB" balug.org._domainkey.balug.org. 14400 IN TXT "k=rsa; t=y; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDR8B6uBDHCSGh2L7Z+EbboAKrkehI9vKn1Wp47w3K2H2tYBatBLVKyg9kOwFfZoAmiT04jY9U5nYpwnd7UlUxIvyZiO/TuyXu0lMn4QmLUR8YUZNcoiIHu5EOgf8TgB9sbMun+Ye/5LzKpMtsfNmOnot916yZOpUgd6aJpLp6tHQIDAQAB" #archive.balug.org. 14400 IN A 198.144.194.238 archive.balug.org. 14400 IN A 198.144.194.238 #archive.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 archive.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #www.archive.balug.org. 14400 IN A 198.144.194.238 www.archive.balug.org. 14400 IN A 198.144.194.238 #www.archive.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 www.archive.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #balug-dreamhost.balug.org. 14400 IN CNAME charles-carroll.dreamhost.com. balug-dreamhost.balug.org. 14400 IN CNAME charles-carroll.dreamhost.com. #balug-sf-lug-v1.balug.org. 14400 IN A 198.144.194.238 balug-sf-lug-v1.balug.org. 14400 IN A 198.144.194.238 #balug-sf-lug-v1.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 balug-sf-lug-v1.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #balug-sf-lug-v2.balug.org. 14400 IN A 198.144.194.238 balug-sf-lug-v2.balug.org. 14400 IN A 198.144.194.238 #balug-sf-lug-v2.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 balug-sf-lug-v2.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #balug-untangle.balug.org. 14400 IN A 64.2.3.203 balug-untangle.balug.org. 14400 IN A 64.2.3.203 #beta.balug.org. 14400 IN NS ns1.balug.org. beta.balug.org. 14400 IN NS ns1.balug.org. #balug-sf-lug-v1.console.balug.org. 14400 IN A 208.96.15.250 balug-sf-lug-v1.console.balug.org. 14400 IN A 208.96.15.250 #balug-sf-lug-v2.console.balug.org. 14400 IN A 208.96.15.250 balug-sf-lug-v2.console.balug.org. 14400 IN A 208.96.15.250 #balug-untangle.console.balug.org. 14400 IN A 64.2.3.195 balug-untangle.console.balug.org. 14400 IN A 64.2.3.195 #sf-lug-v1.console.balug.org. 14400 IN A 208.96.15.250 sf-lug-v1.console.balug.org. 14400 IN A 208.96.15.250 #sf-lug-v2.console.balug.org. 14400 IN A 208.96.15.250 sf-lug-v2.console.balug.org. 14400 IN A 208.96.15.250 #untangle.console.balug.org. 14400 IN A 64.2.3.195 untangle.console.balug.org. 14400 IN A 64.2.3.195 #ftp.balug.org. 14400 IN A 208.97.176.67 ftp.balug.org. 14400 IN A 208.97.176.67 #ipv6.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 ipv6.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #www.ipv6.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 www.ipv6.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #lists.balug.org. 14400 IN A 66.33.216.72 lists.balug.org. 14400 IN A 66.33.216.72 #mail.balug.org. 14400 IN A 208.113.200.129 mail.balug.org. 14400 IN A 208.113.200.129 #mail.balug.org. 14400 IN MX 0 mx1.sub5.homie.mail.dreamhost.com. mail.balug.org. 14400 IN MX 0 mx2.sub5.homie.mail.dreamhost.com. mail.balug.org. 14400 IN MX 0 mx1.sub5.homie.mail.dreamhost.com. #mail.balug.org. 14400 IN MX 0 mx2.sub5.homie.mail.dreamhost.com. mail.balug.org. 14400 IN MX 0 mx1.sub5.homie.mail.dreamhost.com. mail.balug.org. 14400 IN MX 0 mx2.sub5.homie.mail.dreamhost.com. #mailboxes.balug.org. 14400 IN A 208.97.187.203 mailboxes.balug.org. 14400 IN A 208.97.187.203 #www.mailboxes.balug.org. 14400 IN A 208.97.187.203 www.mailboxes.balug.org. 14400 IN A 208.97.187.203 #mysql.balug.org. 14400 IN A 208.97.161.83 mysql.balug.org. 14400 IN A 208.97.161.83 #new.balug.org. 14400 IN NS ns1.balug.org. new.balug.org. 14400 IN NS ns1.balug.org. #ns1.balug.org. 14400 IN A 198.144.194.238 ns1.balug.org. 14400 IN A 198.144.194.238 #ns1.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 ns1.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #rsvp.balug.org. 14400 IN A 198.144.194.238 rsvp.balug.org. 14400 IN A 198.144.194.238 #rsvp.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 rsvp.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #secure.balug.org. 14400 IN A 198.144.194.238 secure.balug.org. 14400 IN A 198.144.194.238 #secure.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 secure.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #www.secure.balug.org. 14400 IN A 198.144.194.238 www.secure.balug.org. 14400 IN A 198.144.194.238 #www.secure.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 www.secure.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #sf-lug.balug.org. 14400 IN A 208.96.15.252 sf-lug.balug.org. 14400 IN A 208.96.15.252 #www.sf-lug.balug.org. 14400 IN A 208.96.15.252 www.sf-lug.balug.org. 14400 IN A 208.96.15.252 #sf-lug-v1.balug.org. 14400 IN A 208.96.15.252 sf-lug-v1.balug.org. 14400 IN A 208.96.15.252 #sf-lug-v2.balug.org. 14400 IN A 208.96.15.252 sf-lug-v2.balug.org. 14400 IN A 208.96.15.252 #ssh.balug.org. 14400 IN A 208.97.176.67 ssh.balug.org. 14400 IN A 208.97.176.67 #test.balug.org. 14400 IN NS ns1.balug.org. test.balug.org. 14400 IN NS ns1.balug.org. #untangle.balug.org. 14400 IN A 64.2.3.203 untangle.balug.org. 14400 IN A 64.2.3.203 #vicki.balug.org. 14400 IN A 208.96.15.250 vicki.balug.org. 14400 IN A 208.96.15.250 #webmail.balug.org. 14400 IN A 208.97.187.139 webmail.balug.org. 14400 IN A 208.97.187.139 #www.webmail.balug.org. 14400 IN A 208.97.187.139 www.webmail.balug.org. 14400 IN A 208.97.187.139 #webmaster.balug.org. 14400 IN A 198.144.194.238 webmaster.balug.org. 14400 IN A 198.144.194.238 #webmaster.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 webmaster.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #wiki.balug.org. 14400 IN A 198.144.194.238 wiki.balug.org. 14400 IN A 198.144.194.238 #wiki.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 wiki.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #www.wiki.balug.org. 14400 IN A 198.144.194.238 www.wiki.balug.org. 14400 IN A 198.144.194.238 #www.wiki.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 www.wiki.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #www.balug.org. 14400 IN A 208.97.176.67 www.balug.org. 14400 IN A 208.97.176.67 #www0.balug.org. 14400 IN A 208.97.176.67 www0.balug.org. 14400 IN A 208.97.176.67 #www1.balug.org. 14400 IN A 198.144.194.238 www1.balug.org. 14400 IN A 198.144.194.238 #www1.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 www1.balug.org. 14400 IN AAAA 2001:470:1f04:19e::2 #www2.balug.org. 14400 IN A 64.2.3.203 www2.balug.org. 14400 IN A 64.2.3.203 #balug.org. 14400 IN SOA ns1.balug.org. hostmaster.balug.org. 2016052104 20881 1800 1814400 14400 balug.org. 14400 IN SOA ns1.dreamhost.com. hostmaster.dreamhost.com. 2016052200 14596 1800 1814400 14400
So, in the above, the records preceded by # are those from our AXFR from ns1.balug.org., whereas those without leading # are those looked up on ns1.dreamhost.com., without recursion - and just asking for answers, except in the case of NS records other than balug.org. itself (notably subdomains thereof), we instead look for authority rather than answer.
"Of course" we can't do an AXFR from ns[123].dreamhost.com., unfortunately. So, that doesn't tell us any records that may be there and not found for balug.org. under ns1.balug.org. However, I can check that under DreamHost.Com's eweey GUI web interface thingy - and I do, most notably when I see their zone serial number change for balug.org. or otherwise see any data changes in their hosting of the zone.
It's also a bit more clear in master zone file for balug.org. on ns1.balug.org., as commenting clearly breaks out what mandatory included DreamHost.Com provided stuff we can't change (at least so long as it's hosted by DreamHost.Com), what bits we've added and do control (possibly excepting TTLs), and also notes those that are explicitly different for some necessary or other darn good reason.
From: "Michael Paoli" Michael.Paoli@cal.berkeley.edu Subject: Re: [BALUG-Admin] Why_ should ns1.linuxmafia.com be doing secondary nameservice (for balug.org.), given that you aren't including it in the authoritative list? Date: Fri, 26 Aug 2016 00:53:58 -0700
Ah, good ... glad you caught that bit. :-) Yeah, I can understand heck of a lot going on. (Mom, stroke, whole bunch 'o stuff precipitated out from that ... still recovering from my 2 week anti-vacation + similar rather recently before that ... still playing catch-up and handling of miscellaneous gunk ... e.g. have a car to sell off too - and in the meantime nothin' but street parking for it - which is yet another annoying inconvenience and thing to do and keep an eye on).
From: "Rick Moen" rick@linuxmafia.com Subject: Re: [BALUG-Admin] Why_ should ns1.linuxmafia.com be doing secondary nameservice (for balug.org.), given that you aren't including it in the authoritative list? Date: Thu, 25 Aug 2016 21:55:43 -0700
Quoting Michael Paoli (Michael.Paoli@cal.berkeley.edu):
Your option on balug.org., to be or not be slave at this time. I explained the situation earlier. Notably it's part of migration strategy off of DreamHost.Com. - but we're not there yet (still have to get the dang lists migrated). See the earlier explanation again here (now for the 3rd time ;-)) ... note particularly the bit that starts with "If you'd prefer, for balug.org, could also" ...
OK, thanks.
What I failed to do before was add a note about that to the named.conf.local entry. I've now fixed that omission. Thank you for your indulgence.
(There's been a heck of a lot going on, and I evidently failed to read those couple'a paragraphs in your explanation on Aug. 22nd.)
Quoting Michael Paoli (Michael.Paoli@cal.berkeley.edu):
Ah, good ... glad you caught that bit. :-)
Yeah, I kinda owe you an apology for the pessimistic assumption that you moved a master nameserver to a new IP and didn't tell me. It's happened to me multiple times with other people I do secondary for, though, so the cynicism has a foundation. Anyway, excuses aside: Sorry about that!
I have to remember that my /etc/bind/named.conf.local's comment lines are a _really_ critical place to not _anything_ about the status of domains, e.g., everything I ought to know that's surprising, plus contact information fo everyone relevant.
Yeah, I can understand heck of a lot going on. (Mom, stroke, whole bunch 'o stuff precipitated out from that ... still recovering from my 2 week anti-vacation + similar rather recently before that ... still playing catch-up and handling of miscellaneous gunk ... e.g. have a car to sell off too - and in the meantime nothin' but street parking for it - which is yet another annoying inconvenience and thing to do and keep an eye on).
Personally, I've found that chopping some wood with a two-bladed Viking-style axe helps. It doesn't solve a thing, but you feel better. ;->