Deployment Architecture

Splunk deployment - multiple A records issue

adnalla
New Member

We have setup deployment server. It works pretty well but we have problem with one of our systems - We have four machines (windows) where splunk universal forwarders are installed and these four machines are part of a distributed system setup. We have multiple A records for the same domain name. i.e These servers are hit on a round robin basis for load balancing purposes.

I understand the deployment server uses reverse DNS lookup to identify the hostname. ON reverse lookup of each IP of the above machines, you get two records - one is the domain name we have setup for load balancing and the other is the complete hostname(FQDN)

Whenever the deployment server captures the FQDN/hostname as the dns attribute, it is able to push the apps without any issue. But if the domain name we have set for load balancing is captured all apps are wiped off the client machines.

PLease help as we couldnt find any configuration in Splunk to handle this?

Tags (1)
0 Karma

Mathieu_Dessus
Splunk Employee
Splunk Employee

Have you tried to enter manual addresses in /etc/hosts (or widows equivalent if the deployment server runs windows) in order to force Splunk to see non-balanced addresses ?

0 Karma
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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

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 ...