Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tell HN: Microsoft.com added 192.168.1.1 to their DNS record

news.ycombinator.com

Post reply on HN
Print view View original

131–140 of 148 posts

Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record

#132

Post by varun_ch »

nullbytes wrote: post #89
rasengan wrote: post #38

Earlier quoted context omitted.

This isn’t something that I think should be diluted. If it’s that simple for a stray record to be included in the dns round robin it could have been bad if it was an external ip with a machine setup by a phisherman especially since control of a domain is all you need to get an ssl cert now. Couple this with the fact that it’s Microsoft, one of the most relied on companies in our computer world, this is pretty darn ho…

Microsoft also has some of the phishiest looking domains when you are redirected around the O365 cloud.

Absolutely, I am so glad I'm not the only person who feels this way. Microsoft does not understand domain names.

They use 1drv.ms as the domain in OneDrive emails, and sometimes it almost looks like the .ms ccTLD belongs to them - it very much doesn't, anyone can register a .ms domain.

windows.net being an Azure domain that third parties can have content under is fitting.

It sometimes looks like they want their users to be phished.

Microsoft is a smart company though, I really hope they can sort this out.

Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record

#133

Post by gorlilla »

abound wrote: post #112
rand1239 wrote: post #110

Earlier quoted context omitted.

If you know yourself through a series of connection then that's a false you.

Not necessarily, in the same sense that I'm my neighbor's neighbor.

You're also an alien's alien.

Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record

#134

Post by mschuster91 »

nullbytes wrote: post #89
rasengan wrote: post #38

Earlier quoted context omitted.

This isn’t something that I think should be diluted. If it’s that simple for a stray record to be included in the dns round robin it could have been bad if it was an external ip with a machine setup by a phisherman especially since control of a domain is all you need to get an ssl cert now. Couple this with the fact that it’s Microsoft, one of the most relied on companies in our computer world, this is pretty darn ho…

Microsoft also has some of the phishiest looking domains when you are redirected around the O365 cloud.

Yeah. Easy to spot when your session expires - first they're still using login.live.com, just to redirect you to login.microsoftonline.com.

Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record

#135

Post by notakio »

Cpoll wrote: post #94
statictype wrote: post #55

Earlier quoted context omitted.

For all this to work you need to control the domain. Is that easier than simply breaking into their systems and owning their servers?

That's exactly what they're saying. > it could have been bad if it was an external ip with a machine setup by a phisherman I.e. one of the IPs for microsoft.com belongs to $phisher, which means they control (a subset of the traffic going to) the domain. They can't add CNAME records for certificate validation, but LetsEncrypt for example offers HTTP-based validation. Not sure how Microsoft sets up their certificate pi…

For the Microsoft.com domain, proper, there seem to be no existing CAA rules, allowing each and every CA on earth to issue certificates based on whatever criteria the CA requires. What could possibly go wrong with that approach?

Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record

#138

Post by jgoodknight »

rubyfan wrote: post #27
kotaKat wrote: post #15

Through a series of connections I know a guy that knows a guy that works at Microsoft that was made aware and the changes have been reverted. Give 'er 30 minutes TTL ;)

This is my favorite HN comment of 2023.

This is my second favorite HN comment of 2023

Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record

#139

Post by awill »

zenexer wrote: post #82
adolph wrote: post #80

Earlier quoted context omitted.

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 microsof…

Only one of those is authoritative. All of the authoritative servers have dropped it. Microsoft has fixed the issue.

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.

Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record

#140

Post by awill »

workfromspace wrote: post #136
kotaKat wrote: post #15

Through a series of connections I know a guy that knows a guy that works at Microsoft that was made aware and the changes have been reverted. Give 'er 30 minutes TTL ;)

Do we need to restart our Windows machines? :)

that's the solution to all Windows problems, so yes :)
Post reply on HN