Windows Server 2008: create dns records
This video also works on Server 2003. We so frequently install DNS with Active Directory, we forget that it is a full featured service on its own. This video is just one aspect of many features available from Windows DNS. This how-to video on Microsoft Windows Server 2008 domain name service (DNS) shows how to manually create DNS records. The types of records are A and AAAA records for normal lookups in a IPv4 or IPv6 environment. (Glue record) PTR records for a reverse lookup zone. This is the opposite of DNS. It’s IP Address mapping to DNS name. MX records for mail exchanger CNAME for canonical name records. These resolve one name to another name. It’s like a nickname for machines. NS records to specify other name servers. SOA records to identify the server in charge of the domain. Providing training videos since last Tuesday. technoblogical.com Thanks for watching.
Comments
Comment from ManOfMeans
Time September 1, 2010 at 1:40 pm
@ManOfMeans Sorry, technoblogical. I just happened across some information that may work. Nonetheless, a video talking this process through would still be nice to have! Have a great day 
Comment from ManOfMeans
Time September 1, 2010 at 2:26 pm
Great video! I have a question, however. I realize that using DNS is not the best method for redirecting or blocking websites, but I’d still like to know how to do this through DNS. Do you have a tutorial on how to do this? I cannot find anything on YouTube anywhere nor any real true step-by-step instructions on any web site. Thanks!!!
Comment from mcaffari
Time September 1, 2010 at 2:55 pm
Excellent video, great content and great video quality. where can I find more examples of the other types of dns records? Thank you
Comment from technoblogical
Time September 1, 2010 at 1:12 pm
Well I have a video called “dns forwarders, root hints, and recursion”. It’s not a step by step, but it shows the tabs. To block those websites, you might want to just point them to the loopback address?
If you want to turn off all external websites, turn off recursion. That way if your server doesn’t run it, it won’t answer your requests. If your clients are not able to ask anyone else, tough luck.
Probably not the best way though