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!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...