Getting Data In

How to make sure all servers checking in with the deployment server use FQDN?

jlemoine
Path Finder

I've noticed that among all of the universal forwarders checking in with my deployment server, there is no consistency in which hosts are fully qualified domain names (FQDN), e.g. myserver.mydomain.com, and which hosts just check in with short names, e.g. myserver.

Can someone tell me how to control this function? Ideally, I want all servers checking in with the deployment server to use FQDNs.

Thanks in advance!

0 Karma
1 Solution

woodcock
Esteemed Legend

Edit server.conf:

hostnameOption = <ASCII string>
* The option used to specify the detail in the server name used to identify this Splunk instance.
* Can be one of "fullyqualifiedname" , "clustername", "shortname"
* Is applicable to Windows only
* Shall not be an empty string

View solution in original post

woodcock
Esteemed Legend

Edit server.conf:

hostnameOption = <ASCII string>
* The option used to specify the detail in the server name used to identify this Splunk instance.
* Can be one of "fullyqualifiedname" , "clustername", "shortname"
* Is applicable to Windows only
* Shall not be an empty string

jlemoine
Path Finder

Thank you.

Interesting about the "only to applicable to Windows only" caveat.

Actually, now that I look at it, it is only the Windows hosts that are not qualified on the forwarder management page. All of the *nix hosts are.

0 Karma
Get Updates on the Splunk Community!

Celebrating Fast Lane: 2025 Authorized Learning Partner of the Year

At .conf25, Splunk proudly recognized Fast Lane as the 2025 Authorized Learning Partner of the Year. This ...

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...