a little questionn.
- Thread starter ka0zstyle
- Start date
Solution
Lessaire
Omniscient Hypervisor
1.) Buy from Hover or Namecheap. Do not buy from GoDaddy because if your payment for renewal ever lapses they will register it themselves and try to sell you back the domain for $$$.
2.) Domain registrar and server host are not inherently relevant to each other, so no it does not matter. Your registrar could be in Mongolia, and your server in Bolivia, does not mean anything.
Computer networks no do speak domain names, they only speak IP addresses. Say you were connetcing to OTLand. Your router does not know what otland.net is, so it communicates with DNS server, "Domain Name System", and DNS server sends back info on where to send packets to. DNS servers are also know as nameservers. In most cases your local ISP will be the nameserver you use . ISP nameserver will probably not know the record you want, so it will query one of the root servers for that TLD. The root nameserver will tell your ISP nameserver the appropriate nameserver to ask. Your ISPs nameserver then makes another query to the nameserver responsible for the TLD+IP block. The machine gets a response like this:
This can cause a very small amount of lag the first time. After that that, your local nameserver with cache the query. Subsequent requests well give the result much faster for a good wile before the cache expires again. So the lag is not a concern to consider. Your browser then gets the response and knows how to proceed, it connects to the computer exposing port 80 on the IP 104.28.2.119. And you finally see the website, about 20ms later.
2.) Domain registrar and server host are not inherently relevant to each other, so no it does not matter. Your registrar could be in Mongolia, and your server in Bolivia, does not mean anything.
Computer networks no do speak domain names, they only speak IP addresses. Say you were connetcing to OTLand. Your router does not know what otland.net is, so it communicates with DNS server, "Domain Name System", and DNS server sends back info on where to send packets to. DNS servers are also know as nameservers. In most cases your local ISP will be the nameserver you use . ISP nameserver will probably not know the record you want, so it will query one of the root servers for that TLD. The root nameserver will tell your ISP nameserver the appropriate nameserver to ask. Your ISPs nameserver then makes another query to the nameserver responsible for the TLD+IP block. The machine gets a response like this:
Bash:
dig otland.net
; <<>> DiG 9.16.1 <<>> otland.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14692
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;otland.net. IN A
;; ANSWER SECTION:
otland.net. 299 IN A 104.28.2.119
otland.net. 299 IN A 104.28.3.119
;; Query time: 26 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sat Apr 04 02:20:08 PDT 2020
;; MSG SIZE rcvd: 71This can cause a very small amount of lag the first time. After that that, your local nameserver with cache the query. Subsequent requests well give the result much faster for a good wile before the cache expires again. So the lag is not a concern to consider. Your browser then gets the response and knows how to proceed, it connects to the computer exposing port 80 on the IP 104.28.2.119. And you finally see the website, about 20ms later.
