<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to make sure all servers checking in with the deployment server use FQDN? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-make-sure-all-servers-checking-in-with-the-deployment/m-p/247298#M47703</link>
    <description>&lt;P&gt;Thank you. &lt;/P&gt;

&lt;P&gt;Interesting about the "only to applicable to Windows only" caveat. &lt;/P&gt;

&lt;P&gt;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. &lt;/P&gt;</description>
    <pubDate>Fri, 20 Jan 2017 14:52:33 GMT</pubDate>
    <dc:creator>jlemoine</dc:creator>
    <dc:date>2017-01-20T14:52:33Z</dc:date>
    <item>
      <title>How to make sure all servers checking in with the deployment server use FQDN?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-make-sure-all-servers-checking-in-with-the-deployment/m-p/247296#M47701</link>
      <description>&lt;P&gt;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. &lt;STRONG&gt;myserver.mydomain.com&lt;/STRONG&gt;, and which hosts just check in with short names, e.g. &lt;STRONG&gt;myserver.&lt;/STRONG&gt; &lt;/P&gt;

&lt;P&gt;Can someone tell me how to control this function? Ideally, I want all servers checking in with the deployment server to use FQDNs.&lt;/P&gt;

&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2017 21:52:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-make-sure-all-servers-checking-in-with-the-deployment/m-p/247296#M47701</guid>
      <dc:creator>jlemoine</dc:creator>
      <dc:date>2017-01-19T21:52:43Z</dc:date>
    </item>
    <item>
      <title>Re: How to make sure all servers checking in with the deployment server use FQDN?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-make-sure-all-servers-checking-in-with-the-deployment/m-p/247297#M47702</link>
      <description>&lt;P&gt;Edit &lt;CODE&gt;server.conf&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;hostnameOption = &amp;lt;ASCII string&amp;gt;
* 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
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 20 Jan 2017 06:16:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-make-sure-all-servers-checking-in-with-the-deployment/m-p/247297#M47702</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-01-20T06:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to make sure all servers checking in with the deployment server use FQDN?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-make-sure-all-servers-checking-in-with-the-deployment/m-p/247298#M47703</link>
      <description>&lt;P&gt;Thank you. &lt;/P&gt;

&lt;P&gt;Interesting about the "only to applicable to Windows only" caveat. &lt;/P&gt;

&lt;P&gt;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. &lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2017 14:52:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-make-sure-all-servers-checking-in-with-the-deployment/m-p/247298#M47703</guid>
      <dc:creator>jlemoine</dc:creator>
      <dc:date>2017-01-20T14:52:33Z</dc:date>
    </item>
  </channel>
</rss>

