wdym? by popular do you mean used alot? but im the only one who uses it wtf

it's not a public DNS domain tho

localhost is not resolved with DNS. It is kind of an alias for an ip address. Fun fact: you can define your own names in /etc/hosts (c:\windows\system32\drivers\etc\hosts for windows)

@@youdontknowme5969 No but it does bring up the topic of a computer's local hostname resolver found in the locations mentioned by @Vladislav Kalmyikov, which would be another fun techquickie all in it's own. Setting up local hostnames to get to private in-network services from say a local server.

@@BulbaWarrior every domain is an alias for an ip yk. besides localhost is in fact a local domain and local domains are never resolved by a dns but instead specified on a local network level which what the video and this comment were referring to.

pro-tip: you can also put "" before it to tell the web browser that this is a url and not a search term

@@mysteryboyee yeah, I kind of realized that after writing this comment

@@mysteryboyee yay! save the dot, use a :

@@toptierdiscordmod7806 part of the issue of using a domain-less hostname is for things like routers and embedded devices, so they may not support https (or as is often the case I see, ship with self-signed certs).

Or use a separate search box like Firefox has (default disabled).

Google always abuses their position.

@@nclsDesign doesn't literally every big company lol

@@IceBro That's why they are a big company

Just don't Google Google it will break the internet

from abusing*

thank you kindly :)

If I had a dollar for every time a web form that said my email address can't have a + in it...

@@mareviq They're usually doing that intentionally, because they don't want you to abuse their system by signing up for a million accounts using trivial mailbox aliases.

just remember: the easiest way to validate an email address is to hand it to an MTA and see if it bounces.

Thanks! Was about to ask already. Everybody who wrote a email validation regex knows the pain.

Exactly, there's always a dot at the end!

isn't that still the same stuff as in the video, with normal dotless domains? just provider-only.

google still owns that. if i type into my url bar i get search. most people google google, and it works 99% of the time, i get exactly what i want without knowing the domain.

I vagely remember my ISP doing something similar.

​@@teebu nope that's not how this works. the "URL bar" of today's browsers is called the omnibar which can handle either URLs or if the input can't be resolved to an URL a preconfigured search engine will get the input instead and delivers a search result page.

@@CathrineMacNiel *omnibox.

Unfortunately even if they wanted to, it wouldn't work. Your operating system automatically resolves localhost to 127.0.0.1, which is the loopback address so the traffic never actually exits your computer's network card.

@@gsck5499 not fully automatically, it's defined by /etc/hosts file

@@gsck5499 in linux you could redefine localhost and localhost could used for domains but it shouldn't and may break some network software. I don't know if localhost is still in the windows .hosts file but it may by as local .hosts ist still supported as name resolution. I'm happy that network 44 moved on from the local .hostfile in 2008? after they sold a /16 block to Amazon.

Yes! he's the best!!

Literally my favorite person at LMG. Seems like a fun guy tbh

.coffee is my favorite

So do I!! He’s simply the best next to Linus. Not throwing shade, but he’s even better than Andrew, who I honestly think is grossly overrated.

theres enough uploaded it run 24/7 and you would never see it all. Not to mention each new channel every day .

Dns is a hierarchy, every dot represents the next leaf node, the root starts with the dot at the end which can be omitted. I suppose if you could link an A record to . Instead of the root servers resolving all tld's you could have a site just being "." Which will be the mother off all sites.

@@olafbuitelaar I think it would be more of an empty string "" then ".", since the last dot is still a separator like all other dots.

Without the trailing dot, intranets (local networks) could append the rest of your domain to whatever you typed. It's much like "relative paths" vs "absolute paths", for those who know what those are.

you recall correctly it is a dot (and this is just about the worst video i have ever seen on domain names)

This video is so bad and full of bad information. LTT do better!

DNS still supports CHAOS. But virtually everything uses the IN class now.

"Imagine having to download a text file listing ALL the internet sites" - welcome to FidoNet, where you'd regularly download an updated 'node list', basically a BBS phone book, containing not only name and phone number, but also their max speed, compression standards, and the like. But, yeah, prior to DNS, it's all been local and shared /etc/hosts files basically, helping you with not having to remember all those IP addresses. (DNS, basically, is but a networked database of a massive /etc/hosts )

The UK was on JANET. Someone managed to find a gateway to the internet (supposedly it was 'stolen' but I always suspected it was leaked for experimental purposes) but the gateway didn't have a hosts file so you needed to find a source for that to get anywhere. That's how I found Nyx.

As a brit, it was terrible

@@giraffes19 you brits have so many weird and disgusting local dialects, that no matter how poor an accent is acted, it still fits

@@giraffes19 as a Brit, you are terrible

@@giraffes19 meh not worse than most tries on yt

bri'ish yes i just did type that

🤘😎🤘

That was a browser-specific feature. As long as you didn't use AOL browser (e.g. you used IE or Netscape), you didn't have this feature. If your ISP wasn't AOL, you could still use AOL keywords by using the AOL browser or typing them into AOL's search engine.

Jesus i feel old...

How ironic.. you have a spam reply

haha the winner was the spambot's keyword

irs/

@@tomikun8057 HAhahahhaha

Based on what I know, yeah, dotless domain names can be used for emails (an example I see quite often is example@localhost) but I think Gmail and probably other web-based email clients are the ones that don't work with dotless domain names.

Yeah, that bit was guff. In the wild west days of the early enterprise I worked with a number of internal single word domains, and we had internal email setup for, uh, internal things! Very uncommon now for a myriad of other reasons, but SMTP isn't one

@@hermand was the internal internet for internal things about things happening internally and handled by intern?

Only one of the things which made my brain itch due to being technically incorrect in this videos 😅

Yes, if it doesn't work with a certain piece of software or service, it's most likely an issue with implying a certain domain format restriction which isn't in the RFC / spec. Just look up how people recommend RegEx expressions to verify email addresses. This may actually be the source of the issue that the software actively refuses the address for no other reason. Since I've written my own DNS server (in C# which is running on my raspberry pi with mono) just for fun, I actually was knee deep in the DNS RFCs and I almost went nuts^^. There are so many extensions nowadays that it's almost impossible to include them all. Though the funny thing is that DNS doesn't have any "dots" at all in the protocol itself :) The protocol transmits hierarchical labels. In the protocol labels have a byte prefix that contains the length of the label. There are no dots transmitted in a request or response. The label system is even smart enough to allow references to other labels in the same request / response to save some space. This is actually pretty neat. So if a response includes something like ns1.my.awesome.domain.com, ns2.my.awesome.domain.com, ns3.my.awesome.domain.com it may be encoded as [3]ns1[2]my[7]awesome[6]domain[3]com[0] The other domains would be encoded like this: [3]ns2[0xC0][offset to the "my" label] and [3]ns3[0xC0][offset to the "my" label]. Technically a single label can't be longer than 63 characters. Any "length" value greater than 63 indicates a reference to any other point in the whole message. Reading / resolving a name means you just follow the chain until you reach a 0 length label which indicates the end. Note that an offset contains the lower 8 bits in the second byte and an additional 6 bits in the first byte. So an offset can be 16k instead of only 255. Usually DNS is served over UDP so you're naturally limited to about 512 bytes per message (request / response). Though DNS also works over TCP where the "packets" can be as long as necessary. Most commonly used DNS config files that use the bind syntax actually include the "root dot" to the right of the TLD. Most browsers or software which do DNS lookups would not use / interpret that correctly, but in the config it's common to see that extra dot to distinguish a sub domain namespace from a top level domain. Those config files are also build hierarchical. So a zone file could just define records within the zone they belong to without the need to write out the full domain name.

Haha. I second this!

If it helps, most system administrators don't even know everything about DNS. There's a lot.

@@robspiess tbf dotless domains is a pretty stupid idea

Of course they wanted to register w/o the trailing slash. That slash is not part of the domain name. DNs even *must not* contain slashes. It's just one part of the URI. It's just that modern Browsers let you use incomplete URIs and try to figure out the rest for your covienence. Is it even a incomplete URI or a search term, is it http or https, on which port etc. But sometimes (especially on dotless domains) the Browser just guesses wrong. The trailing slash just gives the Browser a hint that you meant an incomplete URI instead of a search term and may or may not work on different browsers (and settings). The better and more correct part to give as a hint would be the protocol part i.e. or

@@Biergartenparadoxon For sure, you can even see this by adding the protocol, typing pn for instance, so that it doesn't get confused. Big problem though is that it does otherwise get confused and I really see no way to differentiate between a single word search term or a single word URL in the same field unless you include some special characters like that; so why on earth Google, who's known for search and for the Chrome browser, wanted to make this more confusing is beyond me

@@Jamiered18 Of course I agree that it was a dumb idea for those reasons in the first place. Just disagree with "Odd that Google wanted to do that, with no trailing slash" since the trailing slash is not part of what you can register but a detail about how to use it afterwards.

Registering "search" for Google also seems like a very monopolistic thing to do.

@@Crux161 oh ok

@@Crux161 what

@@Crux161 a broken bot it seems.

What you don't know is that ICAN already gave them a TLD! They own ".google" and you too can own one for about 200K (+ ongoing yearly costs)

Nope. Not all of them are stored with a tail dot

@@harryjohnson7714 the top (root) level "." is implied if left off. So while a dns management tool or system may not display it, it is treated as present. I shall also point out that the root dot is in the spec. RFC 1034: Domain names - concepts and facilities section 3.1 Name space specifications and terminology "Since a complete domain name ends with the root label, this leads to a printed form which ends in a dot."

@@harryjohnson7714haha, you can’t go against RFC

Firefox has an option in the settings to split up search and address bar

Those are probably just hostnames, not dotless domains. The work computers are typically all part of the same corporate intranet so they behave the same as a local network.

no it doesn't because localhost is not a domain (dotless or otherwise) it is a hostname - this video is wrong and misleading in many respects

@@scytob Par for the course with these, they always miss some of the finer details of the topic. Like for clarity they should surely have mentioned things like .local which AFAIK is most often used on a LAN rather than dotless domains.

@@alexatkin unfortunately with this video they missed it completely, from the main topic down to the details

@@scytob well tell me why my googling verified it is a top level domain, but one that can't appear in a public dns because it is reserved and has a few other oddities based around conventions formed around how it is treated There are 3 other reserved tlds they are 'test', 'example' and 'invalid' and this is all documented in rfc2606 I've given you enough to get you going now its on you because you spouted off without anything to support your argument

@@alexatkin i agree .local is interesting, it also isn't actually DNS, it is mDNS - which is an entirely different resolver system and technology with a confusingly similar name :-) - what people don't seem to realize is any hostname used in a URI is not implicitly a DNS name, it could be an mDNS, DNS, netbios, widows broadcast or one of another number of name resolution protocols !

that's evil genius haha

Worked when I typed the full address: ai/

This is a good idea. Someone should make this. I know the answers to this though.

GoDaddy is a company that is accredited by ICANN (2:23) to register addresses for people, and they host content on their special computers that serve the content to the viewer from the network.

@@davidparke8896 ummm does godaddy have ip ranges to allocate to customers? Did you mean to say register (domain) names?

@@dekeonus Yeah, they register domain names for people, yeah. I’ve heard of URLs being called “web addresses” for some reason.

In the current world where everyone has a single address/search combination bar with their default browser set to Google anyway, I think it would make more sense for Google to be against it, for the same reasons. It's hard to imagine more people search for "search" than they do external websites without the tld.

That additional profitability of .search .app .docs .eat .meme (and others) is exactly what google wanted (they also, likely, wouldn't bother paying other browser makers to have google as the default search provider).

I remember Opera from long ago..

ai./ (with dot) works for me in Windows. pn. works on iOS with Safari (it redirects to government.pn)

except this one was really bad. Just plain wrong from the top level down to the details

I will add the dotless domain is required to work - because the local delivery agent would then be expecting that to be a hostname of a system on the local network

don't forget that you can have ipv6 instead of a hostname even with partial numbers. or user:password in front of the @. also you can use the user:password for regular websites that have htaccess as well to authenticate yourself directly. URLs are fascinating.

For me they didn't worked at all... For such a channel with quite a big team it's incredible how bad examples they gave :(

that's prob because a CA can't issue a certificate for it

Harry Podcast?

Must be nice, but why is there a little dix next to cauls bottom?

@@jr2904 mann idk lool

Most SMTP servers even support IP-addresses, etc.

I do

@Octeract-[SG]: I still use it :-)

In firefox, even if you have the dedicated search bar enabled, searching is still performed from address bar (there might be about:config items to turn address bar search off, but I've not investigated).

@@dekeonus Yeah, I seem to recall the address bar working anyway.

ai./ (with dot) works. pn. only on iOS (redirects to government.pn).

No it isn’t…but it is funny.

Tell me you're not a brit

@@Dudae_ I can’t tell you I am not a Brit.

@@ILoveMyBikes [I meant the other guy]

I can reassure you, your wrongness is top notch.

Did for me on android

It does, simply ignore the security warning and press, "continue to site"

Don't use wi-fi, use mobile data, i think he should've explained Properly

lol thats soooo hilarious

Your browser is probably trying to access an intranet site as suggested in the latter half of the video.

Browsers generally just assume you are trying to search for something

pn/ doesn't works? It's because your browser probably doesn't treat it as a URL so it just googles it. *Try typing: http:/pn/* Edit: same with the other site, *http:/ai/* works.

ai./ (with dot) works for me in Windows (Firefox requires the slash, Edge doesn’t). pn. (with dot) works on iOS (it redirects to government.pn) but not on Windows.

No

Nothing you wrote is correct outside of your limited environment and experience. And you should use .internal for your lan dns suffix. It’s what Google uses and is generally agreed that it will never be used as a public top level domain. Your firewall may run a dns server. Your operating system does not force you to use it. You may have configured your firewall to capture dns traffic and redirect them to the local dns server it runs, but I’d wager a guess that you have not done this, as it would be implemented in an enterprise network for security, etc. That said, I can’t stand this Linus guy and his channels. I thought I had blocked them all. I’ve become stupider by wasting my time here. It as if I have attempted to bail water out of a sinking boat with a tablespoon.

👆👆congratulations🎊you have been randomly selected among my shortlisted winners you just won a prize🎁🎁🎁...

what?

ty

Within a minute buddy

Got it

shhhh. shut up, no one cares!

Ok

👆👆congratulations🎊you have been randomly selected among my shortlisted winners you just won a prize🎁🎁🎁...

Yea DNS_PROBE_FINISHED_NXDOMAIN with Chrome on Win10. Both work on Chrome for Android.