The nameserver be like: "I know a guy that knows a guy that can help you."

From the look of the thumbnail, i tought Mike would say "Dunno" and the video would end.

Every time you're troubleshooting: "It's not possible for DNS to be the cause, it's completely unrelated." Also every time you're troubleshooting: "It was DNS."

Takes me back 25 years when setting up the first DNS server for British Steel that would resolve internet and intranet queries

03:52 Actually, it's 13 ip addresses. This is a hard limit related to the size of DNS packets. These 13 addresses used to belong to 13 servers, but this was long ago expanded by the use of anycast routing to share those ip addresses among multiple servers. A packet sent to one of those addresses get routed to a server in the closest location. These days there are over a thousand root name servers.

Great explanation. One of the few people who explains computer concepts very simply. This is an art. Thank you very much.

When recommendations are faster than sub box

This channel is singlehandedly helping me pass my Network+ exam

Videos with Mike are always really interesting. I really appreciate this guy!

I love this man's explanations, Clean & Simple. So easy to understand and it helps me out alot!

Watched this video 2 years ago, didn't get much. After recent studying, it all makes sense. Great video, this channels is a very helpful reference for top level explanations.

It's so good to see you after a long time.

Finally a new video from Dr. Mike

he's by far my favorite on this format

title: how something works. thumbnail: who tf knows really!?

I needed this video in my life for work - perfect timing! I swear Computerphile installed an agent in my brain. Every time I need to RampUp on a concept, there is new computerphile vid on it...or maybe youtube be creepin...

Brilliant video, and straight to the point, thank you guys! This has been bugging me for a while....

I see Dr. Michael Pound, I click like.

Dr Mike on the mic, check 1 - 2. This guy is always interesting, i love his encryption videos :D

Incredibly well explained! Thank you!!!!

I was waiting for this for so long...

Please, don't stop on making videos, you really inspire me :)

This Guy is Gifted.. I am Enlightened 💡every time I watch his explanations... Thank you.

I used to explain it as like making a (land line) phone call to somebody in another town. You look up the town where the other person lives, dial the STD code for that place and then their number. The same code might cover several towns, just as several websites might be served from the same IP address. The name server does the same job as the code pages in the back of the phone book.

You should do a video on DNS records like MX, A, CNAME, TXT, etc.

good introductory video, hopefully to be followed up with more technical deep dives into the morass of dns

Very Well Explained !!! Thanks to Dr Mike Pound.

The DNS spoofing at the end is basically how the Big Firewall of China works in part. Because DNS has usually no encryption, they don't need to guess the request ID either, since they can just inspect it.

This is the best video thumbnail yet! :-P

Great video and explanation as usual! Now I need the DNS poisoning video!

What a coincidence! I was looking for information about DNS the whole day, I love computerphile.

This is actually quite useful since I'm in the process of creating my first own website

Thank you computer papi for consantly saving my studies

Amazing explanation, thank you!

Love these videos!

Give us more of this guy.

That's some really quality content

This guy deserves he own youtube channel

I'm so happy we finally got to see who lives in that vivarium!

Would love to see Dr. Mike Pound do a video on JSON Web Tokens!!

Even though i know what dns is still watched whole video. I like both computer as well as number phile vids :)

I’d love if these vids were more technical

I like the awkward humor of this man. Would be nice to hang out with this dude for a bit.

05:30 About to say "it could be" 10.0.1.2 and then checks himself when he realises it definitely couldn't be!

Can you please come to my university and teach computer networks for the new first semestlers? Damn I needed this channel and especially you back then... Thank you for this video, great work. Enjoying your way of describing things very much. ;)

good day! what timing! i just had a DSN issue with my laptop wifi and instead on trying to figure out what it was, i just connected it via cable! And this video shows up!

MORE MIKE POUND!!!

Paylastiginiz icin bu faydalı bilgiler icin tesekkürler zil açık 👉🔔👉👏👍🏾

I love your videos ❤️ wished I've done my bachelor degree in nottingham :)

I really love the idea of the waking up in the morning and going "OH NO is Google where I left it???"

2:16 "Or it could be your ISP, if you live at home probably" Well, where do you live mate, we can send help

wow,incredible video,explained it like an absloute pro.

Would be cool if you could do i video on how DNS is changing, DoH : DNS Over HTTPS and DNS over TLS. How unencypted DNS queries are typically stored by ISP to build internet connection records ICRs

0:33 just bogo search through ips

Worth contrasting the telephone system, based on 19th century technology where you have to remember someone’s telephone number (or maintain a directory on your phone), versus the Internet, developed in the 20th century, where the network itself takes care of finding the numbers for you, you just have to remember their names. The mobile phone in your pocket is such an advanced piece of technology, yet when you make a call or send an SMS to someone, it still falls back to this 19th-century way of finding them through the network--by a number instead of a name.

Just set up my website, this stuff is really fun to code for :D

Just recently been having to learn a ton about the DNS, so this vid comes at a perfect time for me. Would love, love, love some vids that go deeper and talk about DNS zones, DNS records, glue records, EDNS, etc. Maybe also some stuff about the registrars/registries and how they're different. Did a project w/ a mail server recently and not understanding DNS set me back probably like two months, lol. Anyway thanks for the vid, Computerphile!

It's probably worth mentioning the hosts file as a potential first point of resolution before DNS

Thumbnail = perfection

I don't know if you made a video about it already, but maybe you could make a video about DNSSEC and DNS over HTTPS and what problems they solve. Amazing thumbnail BTW

Oh a video about cache poisoning would be super cool. I know it is sometimes used for redirecting to login pages and the like but of course it is more often used as an attack vector.

Nice as always! What about IRC?

Pleasantly surprised about the amount of information in an 8 min vid. Couldn't have explained it much better myself without going into Radix trees, resolvers, DDNS, BIND views & ACLs and DNSSEC. BTW, not sure there are many (if any) DNS implementations left that aren't patched against Cache poisoning since Dan Kaminsky released the research ~9 years ago.

I love the thumbnail.

Mike just can't stop fixing his sleeve 🤣 🤣

I see mike Pound, I click the video.

Can't wait for the DNS cache hacking video! It should be pretty fun!

Great video thanks. You didn't talk much about cache invalidation, you just mention a TTL (how is it define, what happen if the IP changes before TTL expire, ...). And when the IP is resolved, how route name server are updated to be able to redirect faster/closer the next time a computer asks? Thanks a lot for your videos

I'm ready for the DNS cache poisoning video!

One drawback with DNS A records, in particular, is that they only give you an IP address, not a port number. So they are not sufficient to identify a service, only a machine which might provide that service. This was remedied later with the introduction of SRV records, but they are not heavily used.

Okay this is a bit freaky... A few years ago, I had a corn snake. In a terrarium exactly like that one (except white), with that exact water bowl, that exact "cave", that exact log, and nearly the same 'vegetation'. A man after my own heart.

Well I'll be damned, I always thought DNS stood for Domain name server, not domain name system. Thanks!

Three seconds in and he's giving us the finger. Noice way to treat your audience mate.

Love the fact that at 07:19, the view count for the displayed video is digits of pi

You are not illustrating the recursive method but the iterative method . In recursive approach , the root server will directly ask the TLD server which in turn will ask the Authoritative server and then the response will get back to the client in similar fashion but in reverse order.

Ooh, looking forward to the video on DNS cache poisoning!

Love the thumbnail

Recently setup Pihole which has worked phenomenally as a DNS server. Highly recommend everyone to look into it!

Thanks Mike

Cool topic!

every once in awhile, i forgot that Computerphile is a double entendre and i get re-excited when i notice it again, lol. computerphile/computer_phile. [brain bMyBrain[] = Mind.Blown();

Have wired and wireless communication exam on monday, what a coincidence! :,)

Would love a video on DNS cache poisoning!

I was hoping for a more thorough explanation of DNS. Who gets the money when I register a domain? How does an "A" record work? If I test if a domain is free by typing it in my browser, do I run a risk of someone registering it before I do?

Your computer will query its host file before making a query to the computers default gateway. The host file was the method of resolving IP address to domain names before the existence of the Domain Name System. It sill exist so that small networks can be setup a way to resolve host names on their networks without setting up and administrating a domain name server. I use mine as an add blocker by resolving domain that host advertising to 127.0.0.1 .

Lovely Andrew Marr impression here!!

7:20: there are PI times 100,000 views. is that a numberphile video?

Ill try to give you a day in the life of a DNS query to better understand the technical lifecycle of DNS. DNS starts with your computer becoming aware of a DNS name server which is typically done through DHCP and is given by your ISP or sometimes is overriden on your router or computer to something like OpenDNS. You will interact with a name server called a cached resolver that might use recursuve lookups or distribute large chunks of updated records around. Those servers will follow up a hierarchy first through resolvers then up through domain levels up to the domain root TLDs. However when they do that they arent looking for an awnser to the DNS query like its IP instead its searching for the start of authority. At this point the query will be given a name server that can provide an authorative awnser to the query. This will be the domain registrars name servers and these servers generally are not recursive so they can only awnser for specific domain names. Among these servers arecones that actually store the original and most upbto date record which will be reference in the Start of Authority record. With that said queries will generally not go this deep ever. Instead youll be relying on a cache or mirror of a name server.

It would be interesting to know what happens if the domain name doesn't exist. Is it number of bounces related, timeout related? Also what if the server IP does change. How does it work so this domain name is updated, or do you have to wait say 24 hours till the cache in all DNS servers get invalidated?

This morning I’ve just read about DNS. Now, KZfaq recommend me this video.

Now you should do a video on DNSSEC.

Waiting for the video about dns poisoning now!

do u do any security vids

Computerphile feat. Cornsnake video confirmed?

Can you please explain the new encrypted DNS (over https)? It's so confusing when you look at how many settings and server adresses you have to plug in to get it to work with windows.

“...if you live at home...” where the f should I live ?? lololol 😇

Mike for president!!!

What's that video with the snake on the left at the end?

Where does the hosts file come into picture?

So name servers are recursive (?) DNS servers. Is that the same name servers configured when registering a domain as well?