1–10 of 148 posts
$ nslookup microsoft.com
Non-authoritative answer:
Name: microsoft.com Address: 192.168.1.0
Name: microsoft.com Address: 20.112.250.133
Name: microsoft.com Address: 20.231.239.246
Name: microsoft.com Address: 20.76.201.171
Name: microsoft.com Address: 20.70.246.20
Name: microsoft.com Address: 20.236.44.162
Name: microsoft.com Address: 192.168.1.1
Name: microsoft.com
Address: 192.168.1.1
Name: microsoft.com
Address: 192.168.1.0
https://who.is/dns/microsoft.com
What are the potential ramifications of this?
Interesting https://who.is/dns/microsoft.com What are the potential ramifications of this?
Which entry is picked for use is generally random depending on the client.
Most systems will retry using another entry though on issues connecting through. That said, if you are on a network that is 192.168 based, trying to get to Microsoft.com may just send you to your local router!
Anyone have any theories on how this could happen?
I'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?
* Copilot told me
* Sabotage (internal or external)