Yeah, he is best by FAR. The others tend to fall into the trap of starting off by using too many SIMPLE analogies and then when the topic goes deeper, it gets harder for them to find perfectly equivalent concepts in the analogy, to keep using that analogy in a manner that is STILL relevant/meaningful to the topic 😁
Good presentation - clearly miked and clearly delivered, good plain English explanations. I feel as if I understand SOA and NS records much better now. Thanks!
This is a good and very well presented video and I'm very grateful for You making and sharing it. That said I think it could have been even better if it had used more "graphical slides", if the type You used when explaining (clarifying) the "MX record". Showing an "over view" of where (in the network) the different records would be "held".And how they would "querried and answer" to fulfill their function is something I believe would facilitate learning and grasping the context of, and relation between the different records. Again many thanks for making and sharing this excellent content Best regards.
DNS MX (Mail Exchanger) Record: MX records are DNS records that specify the mail servers responsible for receiving email messages on behalf of a domain. MX records help route email messages to the correct destination by pointing to the mail servers' hostnames or IP addresses. MX records are essential for email delivery, as they determine where incoming email messages should be delivered within a domain. POP3 (Post Office Protocol version 3): POP3 is an email retrieval protocol used by email clients to retrieve email messages from a mail server. POP3 typically downloads email messages to the client's device, removing them from the server. This means that emails are stored locally, and changes made on the client do not affect the server's copy. POP3 is commonly used for downloading emails to a single device, like a computer. IMAP4 (Internet Message Access Protocol version 4): IMAP4 is another email retrieval protocol used by email clients to access email messages stored on a mail server. Unlike POP3, IMAP4 allows multiple devices to access the same mailbox simultaneously and keeps emails synchronized across all devices. Changes made on one device are reflected on the server and other devices. IMAP4 is suitable for users who want to access their emails from multiple devices and keep them synchronized. SNMP (Simple Network Management Protocol): SNMP is a network management protocol used for monitoring and managing network devices like routers, switches, and servers. SNMP allows network administrators to collect data and manage devices remotely by querying and configuring settings on network equipment. It is not directly related to email or DNS but is essential for network management and monitoring. SMTP (Simple Mail Transfer Protocol): SMTP is an email sending protocol used to send outgoing email messages from a client to a mail server or from one mail server to another. SMTP is responsible for routing and delivering email messages to their intended recipients. It works together with MX records and other email protocols. SMTP is essential for the delivery of email messages across the internet. In summary, DNS MX records help route email messages, while POP3 and IMAP4 are email retrieval protocols for accessing email messages stored on mail servers. SNMP is a network management protocol, and SMTP is an email sending protocol responsible for delivering email messages. These protocols serve different roles in the email and network communication process.
For CNAME Record where does it maintain ip for web1, cname stors alias but how is actual ip is obtained for web1, is another call made to another dns server which maintains a A record or same server maintains both CNAME and A record.
The resolver sees that it's a CNAME and begins its search over again at the root domain level. For example, if there is a DNS zone as follows: NAME TYPE VALUE -------------------------------------------------- bar.example.com. CNAME foo.example.com. foo.example.com. A 192.0.2.23 when an A record lookup for bar.example.com is carried out, the resolver will see a CNAME record and restart the checking at foo.example.com and will then return 192.0.2.23.
CName are like a shortcut like that used in the file system. For example, if you had www.itfreetraining.com and itfreetraining.com you could create a CName to like one to the other. This way you only have one A record making it easier to manage.
i have a live scenario.. Windows 2012 installed with AD and Dns. Standard configuration. noticed if i nslookup ip and hostname . all good if i use the fqdn there is 2 request time out and a reply. if i use fqdn with dot at the end its good. please help Thanks in advanc
Sri Rama I am not sure what the problem is here. Windows will normally add the dot at the end so you don't need to worry about it. It is strange that it requires it to be there. Have you configured your own root servers or are you forwarding the requests to your ISP?
It is a little confusing. So essentially lets say that an e-mail server wants to send an e-mail to example.com. In order to do this, it needs to send the e-mail to the example.com mail server. So it performs a look up to find out where example.com mail server is. Essentially gets the MX record for example.com. The mail server then contacts the example.com mail server and transfers the mail to it.
The A record maps a name to one or more IP addresses, when the IP are known and stable. The CNAME record maps a name to another name. It should only be used when there are no other records on that name. The A name must resolve to an IP, the CNAME and ALIAS record must point to a name. To answer your question: No, PTRs are not the opposite of CNAMEs. CNAMEs are similar to aliases and point to another hostname vs an A record which points to an IP.
How do I set up my server when I have it on a subnet? Say my external ip is 84.22.1.331 but my local ip is 192.168.1.2. How would I set up my www.website.com to be sendt to the server with the local ip of 192.168.1.2 ?
+Ragatokk Your server is using a private IP Address. So you need to configure your home router to forward web traffic to that server. So in your router, forward port 80 to 192.168.1.2
+Ragatokk Multiple web sites can share the same IP Address. The web server should use the incoming DNS to work out what web site it is. However, you will not be able to have to servers using the same port unless you have two different public IP Addresses.
I'm studying computer networking for few weeks using web pages and youtube and I mostly encountered courses with indians (I hope that's how you call people from india) so I'm not sure if they even need teacher, since they are teacher itself :D Kidding, but sometimes they really are "know-it-all". Great video and explanations :) Peace
i dont know the use of this stupid service record .. its allways spam filessrv like this ::::::: Firefox Setup 16.0.1SrvSrvSrv .. and i dont know how to stop it .. it creat about 50 - 74 file when i start any program or click any icon :S any one can help me in this ?
Mohamed Abas I have not heard of this before. If you know which computer it is coming from I would do a check for the computer to see what software is installed. perhaps run a packet sniffer on the computer to work out which software is creating them. Perhaps it is Malware so I would do a check for that as well.
This is a pretty old video now. It helps if you watch the other DNS videos as well. We generally make the videos now so they can be watched by themselves. Is there anything in particularly you are having trouble understanding.
Thanks, glad to hear that you like the videos.
No problem at all. Thanks for watching.
huh ?
Its just due to your videos i am able to understand windows servers. May God bless you guys.
Farukh Shaikh Thanks very much, glad we could help you
Thanks Adam! Good Luck taking them
Thank you for this explanation. I understood it much better than Google IT Training's explanation.
You are welcome!
Competent video with brilliant rhetoric.
Thanks very much.
You got the art of explaining, you are the best
Yeah, he is best by FAR. The others tend to fall into the trap of starting off by using too many SIMPLE analogies and then when the topic goes deeper, it gets harder for them to find perfectly equivalent concepts in the analogy, to keep using that analogy in a manner that is STILL relevant/meaningful to the topic 😁
@@TebogoMotlhale exactly, some times calling things by their real names works much better then exaustive analogies
Good presentation - clearly miked and clearly delivered, good plain English explanations. I feel as if
I understand SOA and NS records much better now. Thanks!
You're most welcome! Thank you for your kind feedback. :)
So helpful!
Glad it was helpful!
I am so glad that you made available this information and video.* Also the narration and manner used.
Thanks very much. Glad to hear that you like the video.
Great video on common resource records!
Thanks!
nice clear explanation with examples and with easy english
Thanks!
Thanks guys this is brilliant your going to help me get me through my exams for 70-410 :-)
Much appreciated the graphics and explanation. Keep up the amazing work!
Much appreciated!
Thanks Sir! I have been looking for somthing that can help me with my mail server but finally! I didnt know that i was using the wrong record...
very good ,this lesson explain the knowledge very well. thanks
Thanks very much. Glad we could help.
This is a good and very well presented video and I'm very grateful for You making and sharing it.
That said I think it could have been even better if it had used more "graphical slides", if the type You used when explaining (clarifying) the "MX record". Showing an "over view" of where (in the network) the different records would be "held".And how they would "querried and answer" to fulfill their function is something I believe would facilitate learning and grasping the context of, and relation between the different records.
Again many thanks for making and sharing this excellent content
Best regards.
You have a collection of great videos. Very informative!
Thanks for the great feedback! We appreciate you choosing ITFreeTraining!
Thanks to explain DNS record in easy to understand
It's my pleasure
Really helped me. Thanks for that.
You're welcome!
Thank you.
Very good videos with full clarity.Well done sir but no videos on AD DS backup and restore.pls upload sir.
Sorry about that, will get those videos done when we can.
Thank you. Very simple and informative way.
Glad it was helpful!
Excellent right to the point explanations. Thanks a lot!
Glad it was helpful!
Amazing..Nice
I love your presentations.
i still watch ur awesome expalnations, and it is jus so good.
Very clear explanations. Keep up the good work !
Thanks for watching.
Great Knowledge Video of DNS records I ever see
Thank you for the clear and concise lesson! So helpful!
You are truly amazing. THANK YOU.
You're welcome! Thanks for the amazing feedback. :)
Can you make a video on different types of http error codes in the same whey.your videos are simple and easy to understand
Finally found this
Thank you sir
Thanks for watching.
Wow, I liked it. Thanks for sharing this with us.
Thanks for watching.
Very clear explanations. Keep up the good work !
thx
Thanks very much. More videos to come.
Helpful indeed, clear explanation
Thanks for the great feedback and for watching!
Congratulations! Nice video!
+Vinicius Thank you very much, we're glad to hear your feedback.
Great job.. a value added would have been to show Dns configuration but maybe you did it on another video
thanks for the video! Learned a lot from it
Glad it was helpful!
Thanks very much.
I am so confused.. what are the differences between the MX, pop3, Imap4, snmp, smtp?
DNS MX (Mail Exchanger) Record:
MX records are DNS records that specify the mail servers responsible for receiving email messages on behalf of a domain.
MX records help route email messages to the correct destination by pointing to the mail servers' hostnames or IP addresses.
MX records are essential for email delivery, as they determine where incoming email messages should be delivered within a domain.
POP3 (Post Office Protocol version 3):
POP3 is an email retrieval protocol used by email clients to retrieve email messages from a mail server.
POP3 typically downloads email messages to the client's device, removing them from the server. This means that emails are stored locally, and changes made on the client do not affect the server's copy.
POP3 is commonly used for downloading emails to a single device, like a computer.
IMAP4 (Internet Message Access Protocol version 4):
IMAP4 is another email retrieval protocol used by email clients to access email messages stored on a mail server.
Unlike POP3, IMAP4 allows multiple devices to access the same mailbox simultaneously and keeps emails synchronized across all devices. Changes made on one device are reflected on the server and other devices.
IMAP4 is suitable for users who want to access their emails from multiple devices and keep them synchronized.
SNMP (Simple Network Management Protocol):
SNMP is a network management protocol used for monitoring and managing network devices like routers, switches, and servers.
SNMP allows network administrators to collect data and manage devices remotely by querying and configuring settings on network equipment.
It is not directly related to email or DNS but is essential for network management and monitoring.
SMTP (Simple Mail Transfer Protocol):
SMTP is an email sending protocol used to send outgoing email messages from a client to a mail server or from one mail server to another.
SMTP is responsible for routing and delivering email messages to their intended recipients. It works together with MX records and other email protocols.
SMTP is essential for the delivery of email messages across the internet.
In summary, DNS MX records help route email messages, while POP3 and IMAP4 are email retrieval protocols for accessing email messages stored on mail servers. SNMP is a network management protocol, and SMTP is an email sending protocol responsible for delivering email messages. These protocols serve different roles in the email and network communication process.
I do everything right but the SPF record can't be verified so frustrating!
Nicely done 👏👏
Thanks!
Thank you. Excellent tutorial!
Thank you for your great feedback!
superb,its really useful to me to understand
thanks a lot
+Balaji Raina You're most welcome.
Thank you very much ,,it is very helpful.
Thanks, glad we could help.
Thanks.
Great Video, helped explain a lot. Thanks :)
Thanks...It's been very very informative..!!
You're very welcome!
great it will help me on how to recognize those records in DNS
Glad we could help.
For CNAME Record where does it maintain ip for web1, cname stors alias but how is actual ip is obtained for web1, is another call made to another dns server which maintains a A record or same server maintains both CNAME and A record.
The resolver sees that it's a CNAME and begins its search over again at the root domain level. For example, if there is a DNS zone as follows:
NAME TYPE VALUE
--------------------------------------------------
bar.example.com. CNAME foo.example.com.
foo.example.com. A 192.0.2.23
when an A record lookup for bar.example.com is carried out, the resolver will see a CNAME record and restart the checking at foo.example.com and will then return 192.0.2.23.
there's a difference between A Records and CName, CName can't be used for naked domain names.
CName are like a shortcut like that used in the file system. For example, if you had www.itfreetraining.com and itfreetraining.com you could create a CName to like one to the other. This way you only have one A record making it easier to manage.
Great Video very well Expained Thx
Thanks very much and thanks for watching.
Excellent! Thank you
+shubham joshi We're glad you think so! You're welcome and thank YOU for watching!
excuse me sir
i have a doubt
what do you mean by resource records?(my exam question)
ca i write your explanation for that question
thank u sir
i have a live scenario..
Windows 2012 installed with AD and Dns. Standard configuration.
noticed
if i nslookup ip and hostname . all good
if i use the fqdn there is 2 request time out and a reply.
if i use fqdn with dot at the end its good.
please help
Thanks in advanc
Sri Rama I am not sure what the problem is here. Windows will normally add the dot at the end so you don't need to worry about it. It is strange that it requires it to be there. Have you configured your own root servers or are you forwarding the requests to your ISP?
4:10 did you mean when a DNS server has an email it needs to end it needs to locate a mail server
It is a little confusing. So essentially lets say that an e-mail server wants to send an e-mail to example.com. In order to do this, it needs to send the e-mail to the example.com mail server. So it performs a look up to find out where example.com mail server is. Essentially gets the MX record for example.com. The mail server then contacts the example.com mail server and transfers the mail to it.
When you said "another A record", did you mean another Alias Record?
That's correct.
Thank you. Also, since PTR works the opposite of A records essentially, does that mean it also works the opposite of CNAME records?
The A record maps a name to one or more IP addresses, when the IP are known and stable.
The CNAME record maps a name to another name. It should only be used when there are no other records on that name.
The A name must resolve to an IP, the CNAME and ALIAS record must point to a name.
To answer your question: No, PTRs are not the opposite of CNAMEs. CNAMEs are similar to aliases and point to another hostname vs an A record which points to an IP.
it is valid 100% for the 70-411.
+LEF ISOS Excellent, we're always excited to confirm our content lines up with the Microsoft exams.
I am unable to ping Server 2K8r2 to win 7 host. I have created DNS forward and reverse records and allow ICMP also.
What happens when you try to ping the IP address directly?
thank you very much it really help me
Thanks for watching.
thanks again .. great video
You're welcome!
How do I set up my server when I have it on a subnet? Say my external ip is 84.22.1.331 but my local ip is 192.168.1.2. How would I set up my www.website.com to be sendt to the server with the local ip of 192.168.1.2 ?
+Ragatokk Your server is using a private IP Address. So you need to configure your home router to forward web traffic to that server. So in your router, forward port 80 to 192.168.1.2
Thanks, but how do I do it when I have two servers on the same network?
+Ragatokk Multiple web sites can share the same IP Address. The web server should use the incoming DNS to work out what web site it is. However, you will not be able to have to servers using the same port unless you have two different public IP Addresses.
I love it soo much, Cheers.
Great video
Thanks very much.
thx alot , great video
Why there is not MX record when I nslookup www.hotmail.com ?
Hotmail seems to want to use a CNAME record vs a traditional MX record. That's probably why.
thank you, excellent.
+roxriver91 You're welcome! Thanks for watching.
Great stuff
Thank you!
very well said :) thanks for all the videos
great video
+Nithin Kg Thanks!
well explained thanks !
You're very welcome!
This is great.
Excellent, thanks for the wonderful feedback.
thanks thanks
thanks thanks
very good!!thanks
thanks so much!!
it's helpful thank you
You're welcome, glad the video was helpful!
if they start training institute in indian many students will benefit
I'm studying computer networking for few weeks using web pages and youtube and I mostly encountered courses with indians (I hope that's how you call people from india) so I'm not sure if they even need teacher, since they are teacher itself :D Kidding, but sometimes they really are "know-it-all". Great video and explanations :) Peace
i dont know the use of this stupid service record .. its allways spam filessrv like this ::::::: Firefox Setup 16.0.1SrvSrvSrv .. and i dont know how to stop it .. it creat about 50 - 74 file when i start any program or click any icon :S any one can help me in this ?
Mohamed Abas I have not heard of this before. If you know which computer it is coming from I would do a check for the computer to see what software is installed. perhaps run a packet sniffer on the computer to work out which software is creating them. Perhaps it is Malware so I would do a check for that as well.
1.25 video speed is best
thanks
You're most welcome!
Thank you I mean it u helped me
You're most welcome, thanks for watching!
awesome
Thanks!
Out of everyhting from TCP/IP if find this topic the most difficult to remember !!!!
Networking isn't always intuitive so stick with it!
Am I the only one who thinks DNS is confusing as hell been trying to learn it for about a month
DNS can be difficult at first, is there anything in particular you are having problems understanding?
nice.
teaches better than Uni lol
Thank you.
Such a vague explanation
This is a pretty old video now. It helps if you watch the other DNS videos as well. We generally make the videos now so they can be watched by themselves. Is there anything in particularly you are having trouble understanding.
so confusing
What do you find confusing?
Sorry but this is a terrible and hard to understand presentation for beginners. A more visual explanation of what's being said would've been helpful.
Sorry to hear that. We are currently redoing the way we do videos so future videos should be better.
Your explanation of MX was very confusing.
What was confusing? Perhaps we can help clear up any confusion. :)
Thanks very much.
thanks, it is helpful
Thank you for watching!
THANK YOU
You're very welcome!
Nice
Thanks!
Thank you.
Thanks so much
No problem at all. Thanks for watching.