Incorrect host name reported

Problem

The agent is working, but the infrastructure UI shows the wrong hostname or duplicated hosts appear.

Solution

Review the hostname related settings in the agent configuration. To set the correct hostname, try the following steps:

1. Edit the newrelic-infra.yml configuration file and add the override_hostname option, whose value is your expected hostname. For example:

   override_hostname: correct-host.domain.com

   Copy

2. Use your init system to restart the agent service:

   Restart the agent with SystemD

   Use SystemD commands with CentOS 7, Debian 8, RHEL 7, and Ubuntu 15.04 or higher:

   bash

   Copy

   $
   sudo systemctl restart newrelic-infra

   Restart the agent with System V

   Use System V commands with Debian 7:

   bash

   Copy

   $
   sudo /etc/init.d/newrelic-infra restart

   Restart the agent with Upstart

   Use Upstart commands with Amazon Linux, CentOS 6, RHEL 6, and Ubuntu 14.10 or lower:

   bash

   Copy

   $
   sudo initctl restart newrelic-infra

   Restart the agent in Windows

   bash

   Copy

   $
   net stop newrelic-infra
   $
   net start newrelic-infra

Cause

In Linux and macOS, the New Relic infrastructure agent tries to resolve its fully qualified domain name against a domain name server, which may not be properly configured or not controlled by the same user as the New Relic infrastructure agent. In Windows, it resolves the domain name using internal tools.