ฝัง
- เผยแพร่เมื่อ 18 ธ.ค. 2013
- This tutorial explains how DNS (Domain Name System) works. We take a look at #DNS on a Windows 2012 R2 Server, how to add host records, and working with NSLookup & IPConfig command line tools to test and troubleshoot DNS.
Topics include: DNS Resolution, Fully Qualified Domain Names (FQDNs), The Domain Namespace, Forward & Reverse Lookups, Root, Top Level & Second Level Domain Name Servers and Zones & Zone Transfers. #WindowsServer
Say hi on social:
Twitter: / it_taster
Instagram: / it_taster
Facebook: / ittaster - วิทยาศาสตร์และเทคโนโลยี
![คบซ้อน - วงL.กฮ. [ Official MV ]](http://i.ytimg.com/vi/5MtesqJ0I1c/mqdefault.jpg)
If you want to understand DNS Essentials, this is a good one. Concise and to the point covering DNS essentials. Thank You.
this is actually the best video for explaining DNS and the related topics in an easiest way. Precise and to the point.
It's 2034 and this is still the best DNS explanation video ever!
Excellent - Simple and crisp! Thank you !
Bro, I wish I could thank you for how easy and simple to understand you make it seems.
Being having issues setting up my own hosting for some websites and this has finally cleared my mind into understanding the whole DNS process.
Regardless that I was using Linux, I was able to replicate pretty much everything.
Thanks again.
Thank you taking the time to comment. I really appreciate your feedback! I'm glad the video was helpful.
Thank you John! I was curious about DNS and this lesson is certainly a foundation in DNS. I was more interested in how a web hosting company, can host multiple other, unrelated domains. To understand what I wanted, I needed to grasp the concepts in your video. Great work, good pace, easy to understand. I would definitely watch another video created by you.
Thanks Wilson, if you're interested in how companies host multiple sites take a look at Apache and 'name-based virtual hosts', this extra bit
of resolution is taken care of by the web server config.
Finally a good tutorial well explained and easy to understand. Thanks !
Thanks very much! Great feedback!
Great work, i am extremely thankful for this material, as i have been struggling since 1 week to point my domains to my server.
many thanks, hope you are able to sort out your domains.
I have never seen such an amazing video... It has all the details needed to understand dns ... thanks a lot
I'm glad you found the video helpful. Thank you for your kinds comments and great feedback :)
God bless. Your teaching skills are excellent. Its so easy for me to grasp an understanding of the topic. Thank you very much John.
Thank you so much for your kind comments. I'm glad you enjoyed the video!
Sorry to be offtopic but does any of you know of a method to log back into an instagram account??
I was stupid lost my account password. I love any tips you can give me.
@@paytonnova1603 try account recovery with your account's registered email.
This video in a nutshell touches most of the concepts and terminologies..thank you
great feedback! thanks for your comment.
best tutorial explaining DNS....Thank you
This is very good tutorial. I did not understand it after I watched it for the first time. But after reading theory about DNS structure everything is on its places. Great work! Thanks a lot!
You're very welcome! Thanks for your kind comments! I'm glad you found the video helpful.
Excellent dive into DNS ... A great brush up for me on how DNS works. I had a look at DNS on Server 2016 after following your Active Directory video. I wondered why it didn't do Reverse-DNS by default.
Great stuff, good to hear you're putting it into practice in Windows Server 2016!
Great job, best DNS tutorial I've seen.
Joe Curtis Great feed back, thanks very much for your comment.
Excellent video. Concise, informative and very well presented.
thanks
Very Informative infomation. Best i've found . Thanks mate
AussieBattler46 Thanks very much my friend!
Broken into bits, from the host file, the resolver cache, local dns, dot all the way down to the www, great video!!!!
Detailed and helpful. Thank you
Very informative video to understand DNS basics in a simple manner. Thanks.
+Aniket Alashe Thanks for your kind comments and feedback, I'm glad you liked the video.
Simply to the point, very beautiful :)
upraj singh Thanks very much!
Great practical content. Thank you
Thank very much your video tutorial on DNS was very helpful and easy to understand. 👍
I'm glad you found the video helpful and thanks for the great feedback!
by far the best explanation of DNS !!!! Thankyou
Many thanks! I'm glad you enjoyed the video👍
Thank you! Very Clear with step by step explaination!
Thank you! Glad you liked the video!
Very good explanation Sir, crisp and clear.
thanks
Very informative. Excellent work
***** Thanks very much for the great feedback!
I never comment but this video really deserved a kudos. Thank you for such a succinct introduction to DNS!
Many thanks! I'm glad you enjoyed the video👍
so far the best one.... thankyou
Very very helpful. Thank you!!
Very informative and useful, explanation was very good. Conceptual and fundamental.
many thanks!
Subscribed and liked, thanks please do more in depth. Like building a hyper v servers network for multiple locations and zones, more like a lab environment for testing.
Very well done! Thank you for this tutorial.
thanks very much!
That was awesome thank you so much!)
thanks for this training. much appreciated!
thanks Philip.
Simple and Perfect .
very helpful and it was in my today`s lesson. thank you so much, i really appreciate for this.
thanks
Having an exam about this next Thursday. your video helped me a lot. Thanks!
+MrMarty77 Good luck with the exam! thanks for your comment.
+ittaster Thank you! Amazing that you actually take the time to reply to all these comments!
Thank you, that was very helpful.
Great video Sir. Thank you for sharing .
thanks for your comment. I glad you like the tutorial.
Very helpful. Thank you.
Very helpful video! Thank you very much from the other side of the pond... ;-)
Many thanks Dusty, I'm glad the video was helpful to you.
Thanks IT Tester Tutorials
+Ziyaul Siddiqui thanks
This was gold, cheers mate
thanks!
Very good explanations! Thanks a lot!
Many thanks for your kind comments and great feedback!
Great video.. very simple, informative
many thanks.
Super. You are best. Please please continue making my life easier
Hi, great feedback!! thanks very much! I'm glad you liked the video and it helped you out.
Excellent - Thank you for making this tutorial :)
thanks.
Great explanation
Thank you Sir. Your video is very clear and didactic.
Great feedback! thanks very much.
excellent vid. Clear and concise. Thnx.
great feedback, many thanks!
so comprehensive n complete
Thankss
+abhijeet negi Great feedback, thanks.
excellent delivery!
Rico Kehl Thanks very much for your kind comments!
Excellent...easy to understand...please make a video on DHCP also..
Magnificent, Thank you v.much
Mohammed Yousif thanks.
Great help! Appreciate the video :)
thanks, I'm glad you found the video helpful.
Well presented. Thanks very much.
Great feedback, thanks!
Great video!!!
Thanks a lot.....for make me better understood of DNS
Thanks, I'm glad the tutorial was helpful.
very useful - I learned a lot. Thank you very much!
Souper309d many thanks for the great feedback!
Crystal clear .thanks
Bharath Kumar Thanks.
Thank you for this great tutorial.
I got a bit confused in what the difference is between a name server and a DNS. Or what is the Name Server in general. Especially here 14:40. Is the name server just this window with records you have open there and DNS is the entire thing? And since you updated the host there does that mean this is the Primary Name Server and the NS record has the value of the server you are on right now?
Good video...Thank you Sir : )
Thanks
Thanks for the video
Thanks for this!
thanks Ken
Great Stuff
excellent tutor
That was great. Could you do a similar tutorial on Mac OS X? There are some finnicky things with dns on a mac such as .local being used by Bonjour
Anthony Vipond Thanks very much. You raise a very important point regarding Microsoft DDNS. Using .local as the internal domain name causes issues with Mac DNS resolution. Microsoft recommend using a different internal domain name such as .lan to avoid the issue.
There is also a workaround which involves configuring search domains on the Macs. Good suggestion! and thanks for your comment.
good explanation !
Thanks
Great video,
thank you!
Thank you!!
I have reviewed the video - still as good as ever. A couple of questions on second viewing.
1) During the explanation of the workstation iterative query, you say the DNS server looks in its local cache and zone database file for the IP address. Is the zone database file the equivalent of the hosts file that the workstations has? Just a different name because it's on the DNS server? Or can the server also have a hosts file in addition?
2) You mention the SOA record as indicating the server is Authoritave. And then you mention the Name Server record as being a pointer to the DNS server. The distinction is a bit foggy for me. Can you elaborate a bit on the differences between these two records. I think the use of server for both is confusing. Can you give an example of where the two would be different?
3) In your NSlookup examples you query at one point without specifying the name server and you say that the client - I am assuming the resolver on the workstation - then uses the default name server? Where does this default come from? In the hosts file of the client?
Thanks in advance for further clarification.
Hi Thanks for your comments about the video.
1. No, a server has a hosts file too, just like a workstation, it allows you to enter static FQDNs to IP address mappings, providing simple manual resolution. They are different things, a Zone Database file is more sophisticated and contains more information related to the DNS zone.
2. The SOA record specifies the primary server for the domain and other config information such as domain refresh interval etc. NS records specify the authoritative name server/s for a domain (primary and secondary DNS servers). Authoritative name servers hold the actual DNS records for the domain.
3.Yes, if no server ip address is specified when using nslookup the default DNS server will be used (as configured in IP settings).
hope this helps.
best DNS video on youtube. Hopefully you can make one with more detail, such as creating zones and doing more in windows server 2012. I'm also a little unclear on how you use the CNAME records. If you just type ftp in the address bar, will that take you to server3.ittaster.com directly?
Thanks for clearing my DNS doubts, I have a question in my mind, does DNS go every time to root server to lookup the IP/s?
Also does every time the communication between Zone Transfer happens on TCP 53 or it depends on what configuration did on the DNS server for communication TCP/UDP 53?
Hi, in a real world situation an internal DNS server or client, would typically be configured to forward to/point to, an ISP's DNS server or other reliable public DNS server as this is more efficient. However where DNS servers are unable to resolve an public FQDN, ultimately that's where the resolution is directed. The DNS server will listen on port 53 TCP/UDP.
@@ittaster true. Thanks
Great video. One question. In your zone file you have 4 A records. The last three are associated with servers in the first column. However the first one has no name in the first column and a time stamp in the last column. It seems to point to .200 which is the same as Server 1. What is its purpose? Thanks in advance.
Hi, glad you liked the video. DNS entries 'same as parent folder' refer to the zone, they're default records created automatically and used by AD services.
Thanks for the quick reply. So if I understand you correctly when I first setup AD/DNS during the install I get all the 'same as parent folder' lines. Again thanks in advance.
yes, but others will also be created automatically afterwards, for example, server 2 and the MX record, because it's an active directory integrated domain.
So all the ones starting with "same as parent folder' were created when the DC/AD/DNS was initially installed? And all the others were auto-created when they were created in AD?
yes, that's right.
DNS Essentials - Understanding & Working With DNS
This tutorial explains how DNS (Domain Name System) works. We take a look at DNS on a Windows 2012 R2 Server, how to add host records, and working with NSLookup & IPConfig command line tools, to test and troubleshoot DNS.
Topics include: DNS Resolution, Fully Qualified Domain Names (FQDNs), The Domain Namespace, Forward & Reverse Lookups, Root, Top Level & Second Level Domain Name Servers and Zones & Zone Transfers.
ittaster I might have missed it, but what are Serial Numbers for?
Ive been having a lot of connection issues with my home network running server 2012 r2 with DNS and AD. When I tried to add a computer into the domain it was failing to found the server multiple times, until eventually it did for some unknown reason. Could you do a more in-depth DNS tutorial? a part 2 perhaps? Thank you.
ralmslb Hi, Windows server runs as an eval for a limited period only, which could be the reason for some of the issues you are experiencing? For a client PC to join a domain it is important it is configured with the AD/DNS server IP as the DNS server. Take a look at my videos covering joining a computer to a domain and DHCP on the channel if you haven't already. Hope this helps.
Jon
ittaster Hi there, Im running a genuine and activated copy of Windows Server Standard 2012 R2. So that wouldnt be the reason of my instability on my network. I wonder if its because of my Asus RT-AC66U router running DD-WRT. I can always ping my server, but network discovery or stuff related to DNS or AD always seem unstable. I watched your video and I joined the domain from the workstation only without creating it on the AD first. It was weird since I would choose my domain, he would ask my Admin account, accept it and then time out saying he couldnt find the server or something like that. After trying like 10 times it eventually accepted it. Another detail was that in "Windows explorer -> Network" the server wouldnt show up prior to joining the domain.
ralmslb Hi, it's worth checking the router config, it will almost certainly be running DHCP and likely to direct client PCs to the router as the DNS server, which is needed for
Internet access. Try setting a client PC with a static IP, and DNS to point to your AD server. Also check the firewall config on the Windows server, make sure there isn't any issue there.
ittaster Hi there, thank you for your reply. Atm the main DNS is the router as you said. And I noticed that some stuff isnt right. Such as if I do nslooup on mydomain.com (an example) and it will return domain non existent. You think if I route all traffic to the server DNS it will solve some of the problems? Another question, I want to connect 2 home networks via VPN in the near future using 2 servers so they become like 1 in practice. 1 will be my server 2012 r2 and the other will be a ubuntu server. Is it ok to use the routers DHCPs spliting the IP pools such as: Home1: 192.168.1.2 -> 192.168.1.50 and Home2: 192.168.1.51 -> 192.168.1.100 ?? Or should I just run a DHCP on the server it self? is there a way setup a failover DHCP?
tysm
Hello! And once I set up the DNS role, as a must, together with the Domain Controller role, it is necessary to give the newly created DNS, DC server IP as DNS IP for all the client PCs (to be) registered within the domain. Is that correct? Thanks.
Yes, it's very important client devices know about the internal DNS server/s.
@@ittaster Dear John. For nslookup I receive: Server: localhost, Address: loopback: 127.0.0.1 AND the server: server1.mylab.local and the server static IP. Why do I receive the loopback as well? Is that normal? I saw that you also used the loopback during the DNS setting so it may be OK. Why do I receive both? Thanks.
thanks
this is the simplest way of explanation.
hi can you explain how dns rebinding works in depth ?
Very useful Thank u sir..
govinda nanda thanks
I want to map my subdomain eg.cloud.abc.com to my file server which is public ip so what record I should add in my DNS server
Hi, may i know what will happen if the forward lookup zone was not configured?
The forward lookup zone is where the hostname records are stored. Without forward lookup zone/s DNS wouldn't be able to resolve hostnames to IP addresses. Which would be a serious issue.
The local DNS Server first queries in its database and then in its cache?
Shouldn't it be the opposite since cache is easier to access?
The local DNS server first checks to see if it is able to resolve the query authoritatively based on local zone records, if it cannot, then it will refer to local cache next.
how would you let other dns servers like 1.1.1.1 or google nns see your dns record and check if you have the rigth path to follow if it dossent have a record like that in its database?
Hi, DNS resolution is hierarchical. Other DNS servers, for example ISPs or Google's will follow the same sort of process described in the video. If they do not have a cached record of a DNS mapping, they would query top level DNS servers. The DNS query would work it's way through the hierarchy until a DNS server that has authority for the domain name is found. An organisation that hosts the domain name will typically handle the DNS record.
@@ittaster ok, thanks for reply:)
nice :)
thanks
please bring new videos on Azure AD and O365. Also other Microsoft cloud concepts.
Very good choice of topics!
I am in fog with that example .local, that lead me in abiss :) . U could use a real fqdn server as an example.
Btw most of ppl are interrested to make small projects at home for web servers or other aplications and like 90% of them use dynamic ip.s.
When we add dns records with cname to point ddns where exactly place the record? I am not sure how to point that cname record . The ddns is basic fqdn ? for example ddns.com is a fqdn domain and offers dynamic domains by adding "subdomain" at mai domain so we get like nameserver1.ddns.com ? Is that right? So now that name define our connection. And on a webserver when we create websites at those website we add cname records with nameserver1.ddns.com?
Hi, the video is intended to give an explanation of how DNS works, the '.local' domain is an internal Microsoft Active Directory integrated DNS domain, but the principles are the same. However there are lots of DNS server software
packages out there and the Linux OS is widely used.
For a small home web server project, the ISP hosting your FQDN will normally provide a portal to point your registered FQDN to your public IP address. Having a static public IP is important, because a dynamic IP can change and thus DNS resolved incorrectly.
It's equally important to carefully consider how your are going to implement security, such firewalls etc. Also check your ISP's Terms & conditions and legal implications.
Thanks for reply, i did not knew that dynamic ip public is so pain in the ass, i've made today a request to my isp to give me a business pack with static ip public. I use also a router in my opinion with many settings, but that can misslead me. Asus router, so everytime i create a nameserver with a public ip dynamic , every time my connection change i have to wait the new ip public to be propagated over the internet?
Hi, yes that's correct. A dynamic IP isn't really suitable for servers, as they can change, and that causes issues. Unless you are specifically wanting to experiment and learn about setting up an actual web server, going for a web hosting package for your website is the best option, because all of the server, security & infrastructure etc. is taken care of for you. Good luck with your project.
Windows give me to the nerves with their complex settings .