Re: .US Harbors Prolific Malicious Link Shortening Service

2023-11-07 Thread John Levine
It appears that Eric Kuhnke said: >-=-=-=-=-=- > >I've seen a US based ISP do its internal management network reverse DNS >using '.us' as a suffix, where the hierarchy is like POP name, then >city/airport code, then state (eg: CA, NJ, FL), then .us for geographical >location of equipment in USA.

Am I the only one who thinks this is disconcerting?

2023-11-07 Thread Owen DeLong via NANOG
https://dnsviz.net/d/10.159.192.in-addr.arpa/dnssec/ Seems to report a bunch of errors in the DS records for 192.in-addr.arpa held in the in-addr.arpa zone. I figured I’d wait a few days and try again the first few times I encountered this, but it’s persisted for more than two weeks now. Owe

Re: Am I the only one who thinks this is disconcerting?

2023-11-07 Thread Mark Andrews
It’s one broken server or firewall dropping fragmented responses In front of it. Just open a ticket. -- Mark Andrews > On 8 Nov 2023, at 07:29, Owen DeLong via NANOG wrote: > >  > 10.159.192.in-addr.arpa > dnsviz.net > > > > Seems to report a bunch of errors in the DS records for 192.in

Re: Am I the only one who thinks this is disconcerting?

2023-11-07 Thread Bryan Fields
On 11/8/23 1:29 AM, Owen DeLong via NANOG wrote: https://dnsviz.net/d/10.159.192.in-addr.arpa/dnssec/ Seems to report a bunch of errors in the DS records for 192.in-addr.arpa held in the in-addr.arpa zone. I figured I’d wait a few days and try again the first few times I encountered this, b