A tip. Use the command getent(1) to look up what programs will search for looking up different databases on your machine, like hosts, passwd, groups etc etc. That will just resolve the names, not doing any real connections. I use it all the time. :-)
I can access my localhost by its "pseudo name" using the lynx command, but when typing in the same URL in the webbrowser i get the: This site can't be reached error message - how could that be?
Simple DNS understanding by etc/hosts and etc/resolv.conf that work locally, I like it. How would the file system work in case of remote centralized dns server?
When the computer is going to try to connect to a machine through its name, it will usually use the file /etc/hosts first, and then ask a DNS server if it can't find the name there. As he said in the video. So the DNS is not used at all when you change the /e/hosts. How it will resolve a name, is decided in /etc/nsswitch.conf. So you can configure where and how it will resolve a name to an IP address. You can test this with the command getent(1). Like "getent hosts www.google.com", you can also do in the other direction, like "getent hosts 192.168.1.1". You can also use other names instead of "hosts", like "ahosts", "passwd", "groups", etc etc.
He is using a web browser, the lynx(1) web browser. You could see what programs, like web browsers will resolve the host name part of an URL with the command getent(1). Please look up the man page for more information.
![[TH]FFWS SEA 2024 Fall - Knockout Stage Day 1](http://i.ytimg.com/vi/nsDmUQdWVtg/mqdefault.jpg)
came for the tutorial , stayed for the subtle asmr
That’s what I needed to boost my understanding of my local setup
A tip. Use the command getent(1) to look up what programs will search for looking up different databases on your machine, like hosts, passwd, groups etc etc. That will just resolve the names, not doing any real connections. I use it all the time. :-)
Really a great explanation..
what a clarity ....Thank you so much
Great explanation of the files and all! 100 likes for you. Thanks a lot!
with your 100, +1 for me, in 4 years it only got 99 likes? it's 200 now! 🥺
good one.. great explanation.. thank you
pretty good explanation of the host file. only thing missing was more custom config but still good vid...
I can access my localhost by its "pseudo name" using the lynx command, but when typing in the same URL in the webbrowser i get the: This site can't be reached error message - how could that be?
This guy is a real Hacker
Thank you, really helped.
Simple DNS understanding by etc/hosts and etc/resolv.conf that work locally, I like it. How would the file system work in case of remote centralized dns server?
When the computer is going to try to connect to a machine through its name, it will usually use the file /etc/hosts first, and then ask a DNS server if it can't find the name there. As he said in the video. So the DNS is not used at all when you change the /e/hosts.
How it will resolve a name, is decided in /etc/nsswitch.conf. So you can configure where and how it will resolve a name to an IP address.
You can test this with the command getent(1). Like "getent hosts www.google.com", you can also do in the other direction, like "getent hosts 192.168.1.1". You can also use other names instead of "hosts", like "ahosts", "passwd", "groups", etc etc.
Thanks a lot steven.
Why do we use Virtual boxes for webservers?
Haha. Ive been watching guys like you for hours about server configs... where do you patch your ethernet cables in your virtual machine?
Shut up
Great tut, thx!
great... want to know how do i set domain name young.com and its reached address be 192.168.10.10 with the primary dns server 172.16.0.10
What if i try accessing it on the browser?
He is using a web browser, the lynx(1) web browser.
You could see what programs, like web browsers will resolve the host name part of an URL with the command getent(1). Please look up the man page for more information.