{"id":805,"date":"2013-10-22T16:01:53","date_gmt":"2013-10-22T21:01:53","guid":{"rendered":"http:\/\/www.poweradmin.com\/blog\/?p=805"},"modified":"2015-04-27T08:34:13","modified_gmt":"2015-04-27T13:34:13","slug":"how-to-configure-dns-client-settings","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/how-to-configure-dns-client-settings\/","title":{"rendered":"How to Configure DNS Client Settings"},"content":{"rendered":"

\n\t\"DNS<\/a>\n<\/p>\n

\n\tIn this article we will discuss some of the DNS settings that each workstation must be configured to in order to communicate within a computer network. DNS is one of the most important services that run within a network or even in the Internet. The infrastructure of the Domain Name System can differ from one dedicated Server to a complex network. If you don\u2019t know all the concepts behind this service, you should check out some of the previous articles from IT training day<\/a>. I won\u2019t take time describing this service here, so instead let\u2019s focus on the elements that need to be configured on a DNS client.\n<\/p>\n

\n\tEach computer network is based on the Client-Server model. In this concept the client will request data from the Server. If the information is found on the Server then the client will receive a direct response with the desired information. This is basically the same way in which the DNS service works.\u00a0 The client will request for a name resolution (getting the IP address from a name) and the Server will either respond with the desired information or it will redirect the request to another DNS Server that is authoritative for the specified domain. Usually, inside large networks, the DNS settings are configured automatically using DHCP servers.\n<\/p>\n

\n\tThere are some cases in which static IP addresses are used within a network so all these DNS settings must be configured manually. As an example, it is recommended that each Server should have a static IP address instead of using a DHCP server to eliminate the single point of failure. Also, inside networks where there is no AD infrastructure and no DHCP servers, DNS settings must be configured individually.\n<\/p>\n

\n\tTo configure the DNS servers list that will be used by a client, you must open the TCP\/IP settings window from the adapter settings. First, navigate to Control Panel\\Network and Internet\\Network and Sharing Center<\/em> and click on the Change<\/em> adapter settings<\/em>. Now select your network interface, right click and select Properties<\/em>. From the Internet Protocol Version 4 (TCP\/IP) properties<\/em> box select advanced<\/em>. In the DNS<\/em> tab you can specify the DNS servers in the order of use:\n<\/p>\n

\n\t\"advanced<\/a>\n<\/p>\n

\n\tAdd the IP address of each DNS server that will be used by this particular machine for DNS queries.\n<\/p>\n

\n\tThe FQDN, or the fully qualified domain name, is composed of two sections: the hostname and the DNS suffix. You can view the computer\u2019s name by typing hostname<\/em> in a command prompt:\n<\/p>\n

\n\t\"command<\/a>\n<\/p>\n

\n\tIf your machine is joined in an Active Directory infrastructure, then the DNS suffix will be added automatically to each machine. The suffix will specify the domain in which the client has been configured. The whole FQDN will identify that particular machine within the specified domain. If you type ipconfig \/all<\/em> you will see the configuration of these two DNS elements:\n<\/p>\n

\n\t\"command<\/a>\n<\/p>\n

\n\tThe primary DNS suffix has two main functions:\n<\/p>\n