[BALUG-Admin] Comcast Service Ticket CR144883981 ... nsx.sunnyside.com.

Fri Jun 7 04:17:31 UTC 2024

Yeah, looks like for whatever reason(s),
nsx.sunnyside.com.
Is still bit glitchy as secondary nameserver.
E.g. not picking up updates in timely manner, though NOTIFY is sent (whether or
not it properly gets there is another matter).
$ DNS_CK mpaoli.net
FQDN: mpaoli.net.:
authority:
mpaoli.net. 172800 IN NS ns0.balug.org.
mpaoli.net. 172800 IN NS ns0.mpaoli.net.
mpaoli.net. 172800 IN NS ns1.linuxmafia.com.
mpaoli.net. 172800 IN NS nsx.sunnyside.com.
mpaoli.net. 172800 IN NS nsy.sunnysidex.com.
mpaoli.net. 172800 IN SOA ns0.mpaoli.net.
Michael\.Paoli.cal.berkeley.edu. 1717733202 10800 3600 3600000 86400
@96.86.170.229 (ns0.balug.org.)
mpaoli.net. 172800 IN SOA ns0.mpaoli.net.
Michael\.Paoli.cal.berkeley.edu. 1717733202 10800 3600 3600000 86400
@2001:470:1f05:19e::2 (ns0.balug.org.)
mpaoli.net. 172800 IN SOA ns0.mpaoli.net.
Michael\.Paoli.cal.berkeley.edu. 1717733202 10800 3600 3600000 86400
@96.86.170.226 (ns0.mpaoli.net.)
mpaoli.net. 172800 IN SOA ns0.mpaoli.net.
Michael\.Paoli.cal.berkeley.edu. 1717733202 10800 3600 3600000 86400
@2001:470:67:76f::2 (ns0.mpaoli.net.)
mpaoli.net. 172800 IN SOA ns0.mpaoli.net.
Michael\.Paoli.cal.berkeley.edu. 1717733202 10800 3600 3600000 86400
@96.95.217.99 (ns1.linuxmafia.com.)
mpaoli.net. 172800 IN SOA ns0.mpaoli.net.
Michael\.Paoli.cal.berkeley.edu. 1717677638 10800 3600 3600000 86400
@50.242.105.52 (nsx.sunnyside.com.)
mpaoli.net. 172800 IN SOA ns0.mpaoli.net.
Michael\.Paoli.cal.berkeley.edu. 1717733202 10800 3600 3600000 86400
@50.18.139.240 (nsy.sunnysidex.com.)
mpaoli.net. 172800 IN SOA ns0.mpaoli.net.
Michael\.Paoli.cal.berkeley.edu. 1717733202 10800 3600 3600000 86400
@2600:1f1c:528:c500:5e0b:8a37:6598:356c (nsy.sunnysidex.com.)
$

On Thu, Jun 6, 2024 at 6:12 PM Michael Paoli <michael.paoli@berkeley.edu> wrote:
>
> Uhm, well ...
> I still don't see AAAA record back yet for nsx.sunnyside.com.:
> $ eval dig @ns0.sunnysidex.com. +noall +answer +norecurse
> nsx.sunnyside.com.\ A{,AAA}
> nsx.sunnyside.com.      600     IN      A       50.242.105.52
> $
> But it is answering again now:
> $ dig @2603:3024:180d:f100:50:242:105:34 +noall +answer +norecurse
> balug.org. SOA
> balug.org.              3600    IN      SOA     ns0.balug.org.
> hostmaster.balug.org. 1717666105 10800 3600 3600000 86400
> $
> But I (or at least dnsviz.net)
> am seeing some glitches with 50.242.105.52 (nsx.sunnyside.com.), see, e.g.:
> https://dnsviz.net/d/balug.org/ZmJbcA/dnssec/
> That weren't present several hours earlier, see, e.g.:
> https://dnsviz.net/d/balug.org/ZmHuow/dnssec/
>
> Anyway, you can probably also run many of those checks easily enough with
> https://dnsviz.net/ ... it's even quite excellent at picking up many
> (at least potential)
> issues that would be difficult/challenging to fully check for manually.
>
> So, anyway, the IPv6, yes, looking better, but still lacking restoration of
> that AAAA record and ... that IPv4 - maybe just some transient glitch -
> but looked better several hours ago.
>
> On Thu, Jun 6, 2024 at 2:45 PM Al <awbalug@sunnyside.com> wrote:
> >
> > was out this morning...
> > I think nsx now has had the IPv6 Comcast address re-included.
> > Also several servers that were (due to Murphy's law) trying to originate
> > outgoing connections on that particular IPv6 net (even though mutliple
> > IPv6 addrs were configured) have now had their addrs added back, so
> > servers should all be reachable.
> > I think things are working but I will monitor the monitoring system
> > output,  which hasn't quite simmered down yet, and please let me know if
> > you see anything.
> >
> > On 6/6/2024 10:45, Michael Paoli via BALUG-Admin wrote:
> > > Ah ... sounds good.
> > > So ... I'm guessing soon...ish, you'll have
> > > 2603:3024:180d:f100:50:242:105:34 (nsx.sunnyside.com.)
> > > operational again (no extreme rush) ... or at least nsx.sunnyside.com.
> > > regaining an operational AAAA that also works for DNS.
> > > I noticed earlier it wasn't working ... then subsequently
> > > you apparently dropped the AAAA record for it
> > > (perfectly fine thing to do while it's not working!)
> > > ... I did try the IP directly - still no DNS response,
> > > but I note also that that AAAA record hasn't been
> > > restored yet either ... or any AAAA record for that domain.
> > > $ eval dig @ns0.sunnysidex.com. +noall +answer +norecurse
> > > nsx.sunnyside.com.\ A{,AAA}
> > > nsx.sunnyside.com.      600     IN      A       50.242.105.52
> > > $
> > > https://dnsviz.net/d/balug.org/Zl6vNw/responses/
> > > https://dnsviz.net/d/balug.org/ZmGAnw/responses/
> > > https://dnsviz.net/d/balug.org/ZmHuow/responses/
> > >
> > >> 19 tickets closed almost immediately without comment
> > > Let's see, if we have a ticketing system, and highly
> > > incentivized folks to close tickets quickly, we get ...
> > > lots of tickets closed quickly ... doesn't mean anything
> > > gets fixed.  And yes, have seen this before ... alas, even
> > > in some departments/areas at some employers I've
> > > worked at.
> > > "Be careful what you measure."  (And how one uses it).
> > > Same employer, a much more astute manager with a
> > > much better functioning department ... how did they
> > > do it?  They surveyed the customers, and used that
> > > as a large measure of determining how well the technicians were
> > > doing at getting issues solved ... not how quickly
> > > the techs closed tickets.  Alas, that highly well
> > > performing department stuck out like a sore
> > > thumb ... so ... eventually management "fixed"
> > > that issue ... by subsuming that department into
> > > the other, thus ensuring there wouldn't be such
> > > a good standout to embarrass the rest.
> > >
> > > Anyway, glad your Comcast issue finally got resolved.
> > >
> > > < From: Michael Paoli <michael.paoli@berkeley.edu>
> > > < Date: Tue, Jun 4, 2024 at 4:21\xe2\x80\xafPM
> > > < Subject: Re: [BALUG-Admin] (forw) linuxmafia.com 2024-06-04 02:02
> > > System Events
> > > < To: Rick Moen <rick@linuxmafia.com>
> > > < Cc: BALUG-Admin <balug-admin@lists.balug.org>, Al <aw009@sunnyside.com>
> > > <
> > > < And thirdly - relatively minor issue.  Al's got
> > > < (at least last I checked, yesterday or so) issues with
> > > < 2603:3024:180d:f100:50:242:105:34 (nsx.sunnyside.com.)
> > > < not responding.
> > >
> > > On Thu, Jun 6, 2024 at 7:45 AM Al <aw009@sunnyside.com> wrote:
> > >> The manager that took one of my tickets and refused to let it be closed has helped me to finally get my case resolved.
> > >> I have tested access from AWS successfully, and the modem does in fact seem to have my /56 back in it instead of what
> > >> looked very much like a dynamic /64.
> > >> It's also amazing that anyone talked to me at all.  I had 19 tickets closed almost immediately without comment.
> > >>
> > >>
> > >> -------- Forwarded Message --------
> > >> Subject: Comcast Service Ticket CR144883981
> > >> Date: Thu, 6 Jun 2024 14:12:18 +0000
> > >> From:
> > >> To: awcomcast@sunnyside.com <awcomcast@sunnyside.com>
> > >>
> > >>
> > >> Good morning,
> > >>
> > >>
> > >>
> > >> I am reaching out to you in regards to ticket CR144883981. This was in regards to reclaiming your original IPv6 prefix. I worked with our device support, and we were able to reclaim 2603:3024:180d:f100 for you. As of this morning, the IPv6 has been restored onto your modem.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Thank you for using Comcast,
> > >>
> > >>
> > >>
> > >> Shana Rich
> > >>
> > >> Tech 4, CSSA (ABS)
> > >>
> > >> Complex & Strategic Service Assurance
> > >>
> > >> Avail Hours Mon-Fri, 8:00am – 4:30pm MST
> > >>
> > >> Comcast Business Services
> > > _______________________________________________
> > > BALUG-Admin mailing list
> > > BALUG-Admin@lists.balug.org
> > > https://lists.balug.org/cgi-bin/mailman/listinfo/balug-admin
> >
> >
> > _______________________________________________
> > BALUG-Admin mailing list
> > BALUG-Admin@lists.balug.org
> > https://lists.balug.org/cgi-bin/mailman/listinfo/balug-admin