Getting Data In

connection_host = dns not working

lukasz92
Communicator

Hi,

I set new sourcetype: syslog-net for syslog events I don't want to extract host from.
My settings:

inputs.conf
[udp://55555]
connection_host = dns
disabled = 0
index = net
sourcetype = syslog-net

props.conf
[syslog-net]
MAX_TIMESTAMP_LOOKAHEAD = 32
REPORT-syslog = syslog-extractions
SHOULD_LINEMERGE = False
TIME_FORMAT = %b %d %H:%M:%S
category = Operating System
maxDist = 3
pulldown_type = true
TRANSFORMS =

Problem is that it sometimes (for some IP address) doesn't work. I see reverse dns requests to DNS server, but even if there are responses, I see some IP not resolved (10.26.x.y instead of resolved host name).

Do you have any ideas?

Tags (1)
0 Karma

ronekarleone
Explorer

I have only one idea. Your sourcetype from props.conf overwrite resolved host field. You can read about it input.conf example:

* If the input is configured with a 'sourcetype' that has a transform that   overrides the 'host' field e.g. 'sourcetype=syslog', that will take precedence over the host specified here.
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!

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...

SOK it to Me: Top 3 Benefits of Using Splunk Operator on Kubernetes that’ll Make ...

    Thursday, July 9, 2026  |  11:00AM–12:00PM PDT Duration: 1 hour (includes Q&A) Managing can feel like a ...