Matthew Young35 said:I’ve been following this casually, but did someone here mix up the domain and the hosting?
What exactly is the connection between a domain and an IP address?
(I mean, obviously they're linked, but you know what I'm getting at... a domain and an IP address aren't the same thing.)
They were pointing to the IP address that the TLD resolves to, which happens to be located at the NATO headquarters in Brussels.
Even though that's technically wrong, since the links on the page actually point to a subdomain that our buddy mentioned above, which is also hosted on Cloudflare and resolves to a completely different IP.
It's all connected because those DNS records have to point you toward the specific IP where the IIS (the actual site) lives, or to the load balancer sitting in front of the server farm...
(I guess they just gave out the wrong info, kind of like if someone gave me the wrong IP for a major US site like Yahoo or something)
Edit: actually, let me try a better example to make it click..
Take McDonald's, for instance—they have their own zone for mcd.com. For that zone, the SoA DNS servers live right there within McDonald's infrastructure. There are hundreds of web apps out there that belong to McDonald's, but most of them are built by various third-party vendors or services and are hosted externally, even though the records themselves are kept in that specific zone inside McDonald's.
If you run an nslookup on
app.mcd.com, you're going to get the IP address of where that application or website is actually being hosted.
But if you run an nslookup for
mcd.com, you'll get the IP addresses of the McDonald's DNS servers where that entire zone is managed.
Hopefully, I didn't make that sound way more complicated than it needs to be. 😬