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.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...