They probably asked copilot to manage their DNS servers
"help us bring Microsoft to every home's network"
Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
111–120 of 148 posts
Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
#112Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
#113Wait... Can DNS resolvers be configured so that RFC1918 is respected? I mean: I don't expect anything less from Microsoft than doing stuff like that and it cannot affect me for I nullroute microsoft.com from my unbound server ( unboud takes wildcard when nullrouting or NXDOMAINing crap domains like microsoft.com or meta.com etc., which is sweet). However I'd expect my trusty DNS resolver to also prevent me from anyon…
I wouldn't expect it to. I have plenty of RFC-1918 addresses in a subdomain of my public DNS zone for my home network. It's been that way for decades. (Perhaps I should use split DNS, but...)
Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
#114Earlier quoted context omitted.
A fairly prominent update service already runs from the domain microsoft.com Many machines come with it preinstalled.
The erroneous DNS change wouldn't help that sort of exploit. It just redirects attempts to contact microsoft.com to a local address, probably a router.
That's exactly what I said in the first post.
Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
#115Wait wait wait wait. Bunny.net accidentally changed their DNS to 127.0.0.1 and took a bunch of their CDN users down today too. Coincidence? Weird day.
Employees mixing up SSH consoles while setting up their smart home Christmas lights over weekend.
Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
#116Earlier 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.
That's just a sentence. Not who you are.
https://en.wikipedia.org/wiki/Self-enquiry_(Ramana_Maharshi)
Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
#117Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
#118I'm trying to figure out how this could have happened, but I control so few IP addresses that many of my DNS entries are manually assigned. And you'd have to be incompetent if you have access to set DNS records and you set them to RFC 1918 addresses. Anyone have any theories on how this could happen?
I'll go with Joseph Conrad on this one. "It's only those who do nothing that make no mistakes, I suppose." Now the persons that did it have some proof that they did something. They will surely put some check in place because there should be another adage somewhere that says that you only learn to use the handrails after you fell in the stairs.
erro ergo sum
Re: Tell HN: Microsoft.com added 192.168.1.1 to their DNS record
#119I'm trying to figure out how this could have happened, but I control so few IP addresses that many of my DNS entries are manually assigned. And you'd have to be incompetent if you have access to set DNS records and you set them to RFC 1918 addresses. Anyone have any theories on how this could happen?
My guess is that someone at MS was testing Windows Updates or other changes from a local source. They also had some other DNS updates in their config they were testing. They took all of their config and pushed it out, when they should only have taken the other changes.
I hope that's not their workflow, but few people I've ever worked with have know how to create operating procedures that had half a chance of succeeding, usually it's based on "oh, don't worry, i would never do that"