Well, of course it's all improper. I try to figure out what flavor of improper because Comcast seems to need help thinking. I admit I have had no success in telling them anything, however. I just wonder if they are doing something with MDNS/Zero-config that might have been part of a new s/w release, and they got it all wrong. Or maybe they're changing policies and products, and somehow that leaked in to a legacy config and was of course broken. Enquiring (ala Natl Enquirer) minds wanna know.
On 6/4/2024 18:14, Rick Moen wrote:
Quoting Al (awbalug@sunnyside.com):
Actually I take it back, 73.189.65.18 must be the WAN address of Michael's modem. That won't appear on a message from Michael, unless somehow NAT got involved in the modem? Not sure if that's quite right. I think NAT would come from the last of the assigned static IPv4 addresses, but IIRC I have also seen messages from a modem's WAN address.
Interest, if so -- but nonetheless completely improper. NOTIFY should only ever come from the domain master nameserver's IP.
BALUG-Admin mailing list BALUG-Admin@lists.balug.org https://lists.balug.org/cgi-bin/mailman/listinfo/balug-admin