These are all domain names and DNS servers are used to resolve these to different IPs. Always has done that job and still does it today. But microsoft.com is a single domain name and DNS can only resolve it to a single address (or set of addresses). So cannot be used to tell different services apart.
DNS does not know anything about http or https or any other protocal like that. It just resolves the domain name to an IP/set of IPs. The only thing it can do is point www.microsoft.com and microsoft.com to the same location so that you can use either to get to the webservers.
The person you responded to did say that DNS will get to the correct place, and then other servers will route the traffic using ports and other information. They were a little too strong in that first sentence that now DNS does it, but they did clarify some.
DNS doesn’t do the full thing, but it does do the first step.
These are all domain names and DNS servers are used to resolve these to different IPs.
These are all subdomain names. And subdomains can point to a different IP, or they can point to the same IP. They can also use a CNAME record to point to another [sub]domain name, and it’s probably most common to have an A record on the main domain with the IP and just use a CNAME on the www subdomain so that it always points to the same place the main domain points.
DNS does not know anything about http or https or any other protocal like that. It just resolves the domain name to an IP/set of IPs. The only thing it can do is point www.microsoft.com and microsoft.com to the same location so that you can use either to get to the webservers.
CNAME is the record that is used to point e.g. www.microsoft.com to microsoft.com. They could use an A record for www.microsoft.com and use the same IP as the A record for microsoft.com, which would accomplish the same thing, but would have to be updated when the IP for microsoft.com changes.
Um, that does not really make sense.
These are all domain names and DNS servers are used to resolve these to different IPs. Always has done that job and still does it today. But
microsoft.comis a single domain name and DNS can only resolve it to a single address (or set of addresses). So cannot be used to tell different services apart.DNS does not know anything about
httporhttpsor any other protocal like that. It just resolves the domain name to an IP/set of IPs. The only thing it can do is pointwww.microsoft.comandmicrosoft.comto the same location so that you can use either to get to the webservers.The person you responded to did say that DNS will get to the correct place, and then other servers will route the traffic using ports and other information. They were a little too strong in that first sentence that now DNS does it, but they did clarify some.
DNS doesn’t do the full thing, but it does do the first step.
It was also meant to be a simple answer rather than a deeply technical one.
These are all subdomain names. And subdomains can point to a different IP, or they can point to the same IP. They can also use a CNAME record to point to another [sub]domain name, and it’s probably most common to have an A record on the main domain with the IP and just use a CNAME on the www subdomain so that it always points to the same place the main domain points.
CNAME is the record that is used to point e.g. www.microsoft.com to microsoft.com. They could use an A record for www.microsoft.com and use the same IP as the A record for microsoft.com, which would accomplish the same thing, but would have to be updated when the IP for microsoft.com changes.
The goal was simplicity, not accuracy. To give the “gist” of it to someone who does not know much about technology.