{"id":1589,"date":"2021-08-17T10:00:00","date_gmt":"2021-08-17T14:00:00","guid":{"rendered":"https:\/\/enterpriseadmins.org\/blog\/?p=1589"},"modified":"2021-08-13T10:32:56","modified_gmt":"2021-08-13T14:32:56","slug":"simplified-home-lab-domain-name-resolution","status":"publish","type":"post","link":"https:\/\/enterpriseadmins.org\/blog\/lab-infrastructure\/simplified-home-lab-domain-name-resolution\/","title":{"rendered":"Simplified Home Lab Domain Name Resolution"},"content":{"rendered":"\n<p>In previous posts we discussed considerations for building a Home Lab and for deciding on network ranges to use.&nbsp; Once we know the networks we will be using, its time to start thinking about services that will be required.&nbsp; For me the first service is always Domain Name Server (DNS).&nbsp; This is a foundational building block for many systems which expect forward and reverse lookups to be working before you deploy (like vCenter Server).&nbsp;<\/p>\n\n\n\n<p>Its somewhat common to see folks use a name in the reserved top-level domain of .local suffix, like corp.local.&nbsp; I\u2019m not a fan of this practice, as <a href=\"https:\/\/datatracker.ietf.org\/doc\/html\/rfc6762\">RFC 6762<\/a> spells out special considerations for this domain, and that it should be used for link-local names only.&nbsp;<\/p>\n\n\n\n<p>I\u2019ve also seen folks use domains with a common top-level domain, like bwuchlab.com.&nbsp; As of this writing that domain is available for sale, so there wouldn\u2019t be any conflict or such if I started using it internally without registering the domain.&nbsp; I feel like this is a bad practice as someone else could buy that domain, I\u2019d have no control over it, but may have some documentation or screenshots that include that name. &nbsp;I prefer to use a name that I own.&nbsp; For example my internal DNS domain is lab.enterpriseadmins.org.&nbsp; I already own the domain enterpriseadmins.org and have control over who would get to use the subdomain LAB.&nbsp; If I wanted to create an external DNS host name of something.lab.enterpriseadmins.org, I could do that no problem and could even get an SSL certificate issued for that name if needed.&nbsp; I wouldn\u2019t be able to do this with a domain that I don\u2019t own.<\/p>\n\n\n\n<p>If you don\u2019t need\/want to own a domain name, another good option is to use a reserved name. &nbsp;For example, <a href=\"https:\/\/datatracker.ietf.org\/doc\/html\/rfc2606\">RFC 2606<\/a> reserves the names example.com, example.net, and example.org for documentation purposes.&nbsp; You could use them in your internal network without prior coordination with the Internet Assigned Numbers Authority (IANA).&nbsp; This works well as you can take screenshots and such for documentation where example names in screenshots work, for example:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/enterpriseadmins.org\/blog\/wp-content\/uploads\/2021\/07\/image.png\"><img loading=\"lazy\" decoding=\"async\" width=\"508\" height=\"251\" src=\"https:\/\/enterpriseadmins.org\/blog\/wp-content\/uploads\/2021\/07\/image.png\" alt=\"\" class=\"wp-image-1590\" srcset=\"https:\/\/enterpriseadmins.org\/blog\/wp-content\/uploads\/2021\/07\/image.png 508w, https:\/\/enterpriseadmins.org\/blog\/wp-content\/uploads\/2021\/07\/image-300x148.png 300w\" sizes=\"auto, (max-width: 508px) 100vw, 508px\" \/><\/a><figcaption>Screenshot of command prompt, ping results for the name syslog.example.com returning a valid response from IP 192.168.45.80.<\/figcaption><\/figure>\n\n\n\n<p>Once we have selected the DNS names that we are going to use, we also need to figure out a way to get our clients to point at our DNS server for resolution.  I don&#8217;t like pointing clients directly at my lab infrastructure for name resolution.  Just like I mentioned in a previous post about <a href=\"https:\/\/enterpriseadmins.org\/blog\/?p=1587\">Home Lab Networking<\/a>, I don&#8217;t want a lab problem to prevent the TV from working.  There are a couple of options in this space, I&#8217;ve included a few options below with links to more information.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Pi-Hole &#8212; whole network ad-filtering and conditional DNS forwarding: <a href=\"https:\/\/enterpriseadmins.org\/blog\/lab-infrastructure\/setting-up-pi-hole-dns\/\">https:\/\/enterpriseadmins.org\/blog\/lab-infrastructure\/setting-up-pi-hole-dns\/<\/a> <\/li><li>Mac etc\/resolver: <a href=\"https:\/\/blog.scottlowe.org\/2013\/08\/14\/using-your-home-dns-servers-with-corporate-vpns\/\">https:\/\/blog.scottlowe.org\/2013\/08\/14\/using-your-home-dns-servers-with-corporate-vpns\/<\/a><\/li><li>Windows Name Resolution Policy Table (NRPT): <a href=\"http:\/\/www.patrickkremer.com\/per-zone-dns-resolution-for-homelabs\/\">http:\/\/www.patrickkremer.com\/per-zone-dns-resolution-for-homelabs\/<\/a> <\/li><\/ul>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In previous posts we discussed considerations for building a Home Lab and for deciding on network ranges to use.&nbsp; Once we know the networks we will be using, its time to start thinking about services that will be required.&nbsp; For &hellip; <a href=\"https:\/\/enterpriseadmins.org\/blog\/lab-infrastructure\/simplified-home-lab-domain-name-resolution\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[9],"tags":[],"class_list":["post-1589","post","type-post","status-publish","format-standard","hentry","category-lab-infrastructure"],"_links":{"self":[{"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/posts\/1589","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/comments?post=1589"}],"version-history":[{"count":3,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/posts\/1589\/revisions"}],"predecessor-version":[{"id":1598,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/posts\/1589\/revisions\/1598"}],"wp:attachment":[{"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/media?parent=1589"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/categories?post=1589"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/enterpriseadmins.org\/blog\/wp-json\/wp\/v2\/tags?post=1589"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}