We could really do with some example data to really help but whatever you do you aren't going to be able to compare them without performing an extraction on the host name in the event.
Putting this in transforms/props isn't at all tricky but will leave you with a host field that is extracted each time you run a search (without doing rex).
So, there is something in the event that links it to a host? To match these you need to have a common field. Forget inputlookup for now, I don't think thats the right command for what you want to do (it just throws the CSV onto the end of your results).
Lets say you had an event like this in mydata.log;
192.168.2.1 01/01/12 14:30 Error: I'm an event! With no meaning! Danger!
Now you want to match the IP to the host in your CSV. Assuming you have the IP being extracted somewhere by rex or a rex in transforms/props, lets build a CSV...
ip,hostname
192.168.2.1,DC
and we'll call this hostnames.csv
Then in the search I would do a search for;
source=mydata.log | lookup hostnames.csv ip OUTPUT hostname
This would look for hostnames.csv either in the lookup directory of the current app you're in or for a global csv of the same name, it would pass in the ip and for any matches it would throw out the hostname.
This can be taken a step further by writing this straight into transforms/props so every time you run a search it does this, thats where the power of Splunk comes into play.
You could also do this via DNS if you really wanted but it depends on the use-case.
http://blogs.splunk.com/2009/12/15/reverse-dns-lookups-for-host-entries/
Post more details if this is not what you were talking about.
... View more