Getting Data In

Does a multiple IPs hostname trigger Forwarder round robin?

uchoa
Engager

When writing outputs.conf, setting several receivers to "server=" causes the forwarder to round robin through those receivers.

Now consider a hostname that is resolved to 4 different IPs:

$ nslookup myindexers.host.com
Server: #some-server#
Address: #some-address#

Non-authoritative answer:
Name: myindexers.host.com
Address: 10.1.2.1
Name: myindexers.host.com
Address: 10.1.2.2
Name: myindexers.host.com
Address: 10.1.2.3
Name: myindexers.host.com
Address: 10.1.2.4

Would "server=myindexers.host.com:9997", when it comes to round robin, be equivalent to "server=10.1.2.1:9997,server=10.1.2.2:9997,server=10.1.2.3:9997,server=10.1.2.4:9997"?

Thanks,
André Uchôa

0 Karma
1 Solution

jtacy
Builder

Yes, this will do exactly what you want. The forwarder will use the multiple host records it gets back from DNS as a list of receivers to connect to for autoLB. Also see https://docs.splunk.com/Documentation/Forwarder/6.4.3/Forwarder/Configureloadbalancing#Set_up_DNS-ba... for an example from the docs.

View solution in original post

jtacy
Builder

Yes, this will do exactly what you want. The forwarder will use the multiple host records it gets back from DNS as a list of receivers to connect to for autoLB. Also see https://docs.splunk.com/Documentation/Forwarder/6.4.3/Forwarder/Configureloadbalancing#Set_up_DNS-ba... for an example from the docs.

Get Updates on the Splunk Community!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...