3 ms·
A few are dropping 192.168.1.0 now: as of 1703035296: ns1-39.azure-dns.com no longer has 192.168.1.0 for microsoft.com 1.1.1.1 still has 192.168.1.0 for
by adolph 3y ago
A few are dropping 192.168.1.0 now:
as of 1703035296:
ns1-39.azure-dns.com no longer has 192.168.1.0 for microsoft.com
1.1.1.1 still has 192.168.1.0 for microsoft.com
8.8.8.8 still has 192.168.1.0 for microsoft.com
76.76.2.0 no longer has 192.168.1.0 for microsoft.com
9.9.9.9 still has 192.168.1.0 for microsoft.com
208.67.222.222 still has 192.168.1.0 for microsoft.com
185.228.168.9 still has 192.168.1.0 for microsoft.com
76.76.19.19 still has 192.168.1.0 for microsoft.com
94.140.14.14 still has 192.168.1.0 for microsoft.com
- zenexer 3y agoOnly one of those is authoritative. All of the authoritative servers have dropped it. Microsoft has fixed the issue.
- awill 3y agoYea, sure, but that's like saying "company X stopped selling poison, it's Shop Y's fault that they're still selling it". Nope. This is still Microsoft's fault while non-auth servers update.
- zenexer 3y agoFirst we wanted to see Microsoft update the authoritative nameservers, then move on to monitoring propagation. Conflating the two makes it difficult to monitor whether Microsoft actually fixed it correctly this time, as they appear to have screwed up their first attempt. I wasn't attempting to address blame since I figured that was obvious enough.