Share:|

In this blog, we will cover how to ensure that DNS Is properly configured for End User Experience Management (EUEM) so that calls to external services can be correctly routed.

 

Workstations and other client devices get their DNS server and IP settings automatically through DHCP when joined to a network, but servers which are accessed by many devices need to have fixed addresses, and hence, static IP configuration.  Because these networking settings are entered manually, there is no call made out to get these parameters from DHCP. As such, the IP addresses for services such as DNS and NTP must also be entered manually.

 

On Linux systems, the DNS servers that the system uses for name resolution are defined in the /etc/resolv.conf file. Each nameserver line in the resolv.conf file defines a DNS server.  The entries are prioritized by the order they are found in the file, so the primary DNS server would be the first line, the secondary would be the second, tertiary third and so on. At the bottom of the file, we have a search line which is used to complete fully qualified domain names if only the host name is given. For example, if I have “search bmc.com” and I pinged “docs” , the system would assume that I am referring to “docs.bmc.com”.

 

For example:

 

nameserver <IP_of_primary_DNS_server>

nameserver <IP_of_secondary_DNS_server>

nameserver <IP_of_tertiary_DNS_server>

search bmc.com

 

 

Lastly, the DNS servers defined by the resolv.conf file must be identified by IP and not name for the simple fact the system won’t know how to handle domain names until after it knows how to reach the DNS servers.

 

Please feel free to rate this blog or leave us any questions or comments as we are always looking to improve our documentation.

 

To see more blogs like this, see:

TrueSight App Visibility Manager