How is a URL like this is possible? Wikipedia says ".om

>>60808719
VIRUS, DO NOT CLICK

>>60808719
The global internet DNS may enforce the name.tld convention, but a local DNS server does not need to.

Ever seen "localhost"? If you were testing a webserver on your machine you might do "http://localhost/1.js" which is the same thing.

>>60809018
does a non local dns need to enforce it? say i set up my own, i could do what what i want with it even if it was commercial?

>>60809244
You could make whatever names you want point to wherever you want on your own DNS server. But if you need clients to be able to resolve those names, they need to know to look them up on your server.

When you register a domain you're essentially registering it with a DNS server that everyone already knows to look up names on, and the owners of this system say "You must use a name in the form of name.tld to be registered on our system".

On your own system though, you get to make up the rules.

Yes, but to prevent local suffix resolution which will be tried first (i.e. search for a host which is om.[localdomain]) really the URI should be hxxp://om./etc with a dot after the TLD (which stands for the global root).

This works for any TLD, including the ccTLDs and the new TLDs, providing they have the correct records at the root - which of course very, very few of them do.

Incidentally, the // also stands for a global root in the path (as opposed to the local root /), but DNS is ass-backwards and it's way too late to fix that in the namespace now.

>>60809768
This.
You need the dot at the end for it to properly work. At least, by standards. Some browsers might support dotless root.

I remember there was a list of them posted on /g/ years back, but fuck knows what they were again.
Too lazy to go through TLDs to find them.