(no title)
stardek | 6 years ago
I'm on the University of Waterloo network and I get sent to [1], rather than what I get when I add the period for: http://ai./
stardek | 6 years ago
I'm on the University of Waterloo network and I get sent to [1], rather than what I get when I add the period for: http://ai./
the_pwner224|6 years ago
# Generated by NetworkManager
search my-university.edu
nameserver their-dns-server-ip
nameserver their-other-dns-server-ip
nameserver their-third-dns-server-ip
DNS queries get sent to the nameserver, but the search domain is what's important here. The search domain is used to resolve non-fully-qualified domain names. So if I just type in http://cs, that's not a FQDN since there are no .s - with cs.my-university.edu, it goes edu->my-university->cs, but just cs is not fully qualified. So since the search domain is 'my-unversity.edu', if I just type in http://cs into the browser, it will look up cs.my-university.edu.
In your case, going to the URL ai.uwaterloo.ca redirects to the URL you linked. Adding the trailing . to ai makes it fully qualified, so going to "http://ai." makes your DNS lookup just 'ai' instead of 'ai.uwaterloo.ca'.
The search domain stuff is mostly useful for addressing other devices on the network. My home router sets the search domain to 'lan' when configuring DHCP devices, so I can use my-server as a hostname and it will resolve to my home server's IP. E.g. "ssh my-server" will turn into "ssh my-server.lan" which gets resolved by the router's DNS server to the correct IP.
JdeBP|6 years ago
* http://jdebp.uk./FGA/web-fully-qualified-domain-name.html