DNS is like a post office or delivery company. They all have databases of who lives where so they can match a home address to a name.
DNS isn’t required per se, you can “deliver” traffic directly or through another delivery service… If “https://website.com/” has a domain address of 111.222.33.44, you could also just type that into your browser URL bar like https://111.222.33.44/ and DNS isn’t (or at least shouldn’t be) touched.
Huh, you’re right! Guess I haven’t done that in a long while lol. I tested to Google.com IP address and the http request redirects to https so it did work technically, but I’m guessing not many sites will handle that correctly or all the time.
I know. You can add host and ip to os host file and bypass dns.
But instead of go to person actually responsible for dns entry, domain registrar, they go to dns resolver? And also not go to server host or reverse proxy (cloudflare) which actual cause distribute?
DNS is like a post office or delivery company. They all have databases of who lives where so they can match a home address to a name.
DNS isn’t required per se, you can “deliver” traffic directly or through another delivery service… If “https://website.com/” has a domain address of 111.222.33.44, you could also just type that into your browser URL bar like https://111.222.33.44/ and DNS isn’t (or at least shouldn’t be) touched.
Nah https needs a domain name
Huh, you’re right! Guess I haven’t done that in a long while lol. I tested to Google.com IP address and the http request redirects to https so it did work technically, but I’m guessing not many sites will handle that correctly or all the time.
I know. You can add host and ip to os host file and bypass dns.
But instead of go to person actually responsible for dns entry, domain registrar, they go to dns resolver? And also not go to server host or reverse proxy (cloudflare) which actual cause distribute?