Have removed the port 5353 workaround. It's been over a year since bumping into this issue with Comcast Business. Rick - I did also check on the [ns1.]linuxmafia.com. side, and the 5353 workaround there was commented out long ago, as I'd seemed to recall it having been disabled much earlier there. references/excerpts: $ fgrep 5353 ~/calendar 2025-06-25 if Comcast Business hasn't screwed up DNS with linuxmafia.com for more than a year, probably time to remove the port 5353 work-arounds. $ On Mon, Sep 23, 2024 at 3:35 AM Michael Paoli <michael.paoli@berkeley.edu> wrote:

So,

I'd much earlier noted on my calendar: 2024-09-24 >= 10:56AM US/Pacific PST8PDT -07:00, if Comcast Business hasn't screwed up DNS with linuxmafia.com for more than a year, probably time to remove the port 5353 work-arounds. But, I don't think (year earlier) was necessarily the last of those Comcast DNS issues. So, last I see that hints of that is chatter/discussions that tapered off around 2024-06-04 https://lists.balug.org/mailman3/hyperkitty/list/balug-admin@lists.balug.org... So, as earlier, since wasn't our first go-round, I'll push the end date of that work-around to

...

~=2025-06-05 and if it's by then had no more such glitches, will then drop that work-around. In the meantime, doesn't really hurt hardly anything, and easier to already have that workaround in place, should it be needed at all before then. So, calendar updated: 2025-06-25 if Comcast Business hasn't screwed up DNS with linuxmafia.com for more than a year, probably time to remove the port 5353 work-arounds.