Getting Data In

Splunk does not resolve hostnames in rDNS

torgeirarnoy
Engager

Hi,

We have a fairly new install of Splunk 5.0.4, and i've now opened UDP:514 and the syslog is flowing in. The problem tho is that Splunk lists the hosts with theyr source IP adress instead of the real hostname.

The IPs are all resolveable in rDNS on the splunk server. I cant really find anything reasonable for this case in the manager section either.

What can cause this?

Tags (3)
0 Karma
1 Solution

rturk
Builder

Hi Torgeirarnoy,

This would be the point you dive into the config files, specifically the inputs.conf where you have specified the UDP:514 input. You'll need to change the default 'connection_host' value (ip) to (dns).

[udp://514]
connection_host = dns
sourcetype = syslog

REF: http://docs.splunk.com/Documentation/Splunk/5.0.4/admin/Inputsconf

Hope this helps!

View solution in original post

rturk
Builder

Hi Torgeirarnoy,

This would be the point you dive into the config files, specifically the inputs.conf where you have specified the UDP:514 input. You'll need to change the default 'connection_host' value (ip) to (dns).

[udp://514]
connection_host = dns
sourcetype = syslog

REF: http://docs.splunk.com/Documentation/Splunk/5.0.4/admin/Inputsconf

Hope this helps!

torgeirarnoy
Engager

Worked perfectly. Thanks alot

Get Updates on the Splunk Community!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...