4 ms·

WTF! So "ai" is a sub domain of nothing!?

by walid 13y ago

chewxy 13y ago
DNS root domains have no names. That makes http://ai/ http://ai/ a fully qualified domain name. But apparently ICANN has now banned such things. Gods know why. My eyes glazed over after the 10th "whereas". That document reads like a legal document. Ugh
- nknighthb 13y ago
  > That document reads like a legal document. That's because it is.
randomdata 13y ago
http://news.ycombinator.com./ http://news.ycombinator.com./
desas 13y ago
A trailing period just represents the top of the domain hierarchy. http://reddit.com./ http://reddit.com./ will work just fine.
Dylan16807 13y ago
news.ycombinator.com is actually news.ycombinator.com. with a period at the end. http://ai./ http://ai./ is basically the same as http://com./ http://com./, except that com doesn't have any IPs configured.
- MichaelGG 13y ago
  But as far as TLS name matching goes, it's different. Can something with the dot at the end have a different IP?
  - marcosdumay 13y ago
    Nope. If you don't have a "com" domain at your local network, "example.com" and "example.com." point to the same machine. The TLS domain is matched by the web server, it has no relation to DNS, except that both use the same domains.
  - nivla 13y ago
    > Can something with the dot at the end have a different IP? I guess or maybe you can do a hostname match. However, I remember back in the days Microsoft used to use http://microsoft.com http://microsoft.com. as their test site. Now it just yields an error.
    - jasomill 13y ago
      That's because Microsoft uses hostname-based virtual hosting in IIS, and IIS happens to not recognize HTTP Host headers with trailing dots. This has nothing to do with IP addressing or DNS. In the absence of a resolver search list — which conventionally only applies to names without trailing dot — "microsoft.com" and "microsoft.com." result in the same DNS query, and therefore the same set of IP addresses. Whether this behavior is an obscure bug, a security feature, or both, is left as an exercise.
kintamanimatt 13y ago
FQDNs have periods at the end. It's just convention that dictates they're not included.

WTF! So "ai" is a sub domain of nothing!?

by walid 13y ago

WTF! So "ai" is a sub domain of nothing!?

DNS root domains have no names. That makes http://ai/ http://ai/ a fully qualified domain name. But apparently ICANN has now banned such things. Gods know why. My eyes glazed over after the 10th "whereas". That document reads like a legal document. Ugh

nknighthb 13y ago
> That document reads like a legal document. That's because it is.

randomdata 13y ago

http://news.ycombinator.com./ http://news.ycombinator.com./

desas 13y ago

A trailing period just represents the top of the domain hierarchy. http://reddit.com./ http://reddit.com./ will work just fine.

Dylan16807 13y ago

news.ycombinator.com is actually news.ycombinator.com. with a period at the end. http://ai./ http://ai./ is basically the same as http://com./ http://com./, except that com doesn't have any IPs configured.

MichaelGG 13y ago
But as far as TLS name matching goes, it's different. Can something with the dot at the end have a different IP?
- marcosdumay 13y ago
  Nope. If you don't have a "com" domain at your local network, "example.com" and "example.com." point to the same machine. The TLS domain is matched by the web server, it has no relation to DNS, except that both use the same domains.
- nivla 13y ago
  > Can something with the dot at the end have a different IP? I guess or maybe you can do a hostname match. However, I remember back in the days Microsoft used to use http://microsoft.com http://microsoft.com. as their test site. Now it just yields an error.
  - jasomill 13y ago
    That's because Microsoft uses hostname-based virtual hosting in IIS, and IIS happens to not recognize HTTP Host headers with trailing dots. This has nothing to do with IP addressing or DNS. In the absence of a resolver search list — which conventionally only applies to names without trailing dot — "microsoft.com" and "microsoft.com." result in the same DNS query, and therefore the same set of IP addresses. Whether this behavior is an obscure bug, a security feature, or both, is left as an exercise.

kintamanimatt 13y ago

FQDNs have periods at the end. It's just convention that dictates they're not included.