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
Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI! Discover how Splunk’s agentic AI ...

[Puzzles] Solve, Learn, Repeat: Dereferencing XML to Fixed-length events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Stay Connected: Your Guide to December Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...