News for hackers. Stuff that matters.

A comment on Tell HN: Microsoft.com added 192.168.1.1 to their DNS record. Parent comment

Re:Tell HN: Microsoft.com added 192.168.1.1 to their DNS record by adolph on Tuesday December 19, 2023 @08:23PM (#38704381)
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
[ Parent | on HN ]
Re:Tell HN: Microsoft.com added 192.168.1.1 to their DNS record by zenexer on Tuesday December 19, 2023 @08:28PM (#38704418)
Only one of those is authoritative. All of the authoritative servers have dropped it. Microsoft has fixed the issue.
[ Parent | on HN ]
Re:Tell HN: Microsoft.com added 192.168.1.1 to their DNS record by awill on Wednesday December 20, 2023 @02:26PM (#38712542)
Yea, 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.

[ Parent | on HN ]
Re:Tell HN: Microsoft.com added 192.168.1.1 to their DNS record by zenexer on Monday December 25, 2023 @06:16PM (#38767259)
First 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.

[ Parent | on HN ]