Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Why utilize an FQDN in the stead of a domain (and/or TLD), relative to the root domain?
Until recently, I'd yet to come across a situation in which I'd had any reason to qualify a DNS namespace further than its TLD.
Then, I authored softwareengineering.stackexchange.com/revisions/456302/10, which includes a section about TLDs that are connectable to via a standard internet browser:
http://uz./is a country code TLD, but DNS as a technology does support "dotless" domains.
The aforementioned can be connected to without specifying the root domain (it returns a blank .HTML file regardless).
However, in every example I've seen online, http://uz./ has been preferred in the stead of the valid relative alternative (http://uz/). I've connected to both to verify this.
This has caused me to wonder whether I should be utilizing FQDNs more, because there are evidently situations in which relying upon the standard relative root nameserver resolution process is undesirable.
Consequently, is there any common advantage and disadvantage to leaving the TLD relative to the root domain (example.com), rather than explicitly specifying it (example.com.)?
0 answers
0 comment threads