DNS issue in home network

ranjitcool

Hey Guys,

I am preparing for Windows MCITP Win admin certs.

I have a home lab which is domain.local

Now my default dns for home devices or any device using my internet is my AD/DNS server.

I have some machines joined the domain and some are not.

So when I use my machine not on domain and type in http://domain - it fails.

If i type http://domain.local it finds the right dns record.

Now is this because I did not join my machine to the domain? How do i fix this, for instance be able to type http://movies and get MY movie server rather than some other page?

Please advise.
Thanks
RJ

cisco_trooper

To get to http://movies you need to have a host record entry in the domain.local zone. http://domain is not going to work. domain is not a hostname, whereas movies is a host name. You will have to continue typing http://domain.local in order for that one to work.

ranjitcool

Thanks for the reply, i do have an a record added to my local dns zone. I have it as a movies a record with ip and also a reverse ptr.

ptilsen

A non-domain joined PC will not automatically append the DNS suffix to a hostname during name resolution. Windows does not query DNS for unqualified names (in fact, no system should), and as a result it doesn't matter what you do on the DNS server. For unqualified hostname resolution to work, you must do one of three things:

1. Ensure NETBIOS broadcast is functioning. Network problems, software firewalls, and non-Windows systems are common causes for NETBIOS name resolution problems. In general, NETBIOS broadcast is not a good solution and is generally unreliable.
2. Implement WINS, or any NETBIOS Name Resolution Server. WINS will work seamlessly on your DNS server so it is a good choice
3. Under your network adapter's Properties, within TCP/IP Settings, on the DNS tab, either enter [domain.tld] under "DNS suffix for this connection" and select the "Append parent suffixes of the primary DNS suffix" checkbox, or select the "Append these DNS suffixes (in order):" radio button and add your domain there.

This is a common problem in many corporate networks that have non-domain computers that may attempt to query local resources by hostname. Implementing WINS is by far the easiest and most manageable approach in my environments, including a home environment. Regardless, having a thorough understanding of how name resolution works with NETBIOS and DNS will help you greatly in your certification and your career.

MentholMoose

ptilsen wrote: »

3. Under your network adapter's Properties, within TCP/IP Settings, on the DNS tab, either enter [domain.tld] under "DNS suffix for this connection" and select the "Append parent suffixes of the primary DNS suffix" checkbox, or select the "Append these DNS suffixes (in order):" radio button and add your domain there.

This is my preference, but it is possible to automate if you are using DHCP and control the DHCP server. Enable option 015 (DNS domain name) on the DHCP server, set it to domain.local, and non-domain machines will use it as their DNS suffix. If you are using a Windows server for DHCP this is extremely easy, simply add option 015 to the server or scope options. For other DHCP servers, consult the documentation. If your DHCP server won't let you configure this and your domain controller is running 24/7 anyway, use the DC for DHCP instead.