[METRON-507] Elasticsearch is incorrectly indexing the Bro DNS "answers" field

• Type: Bug
• Status: Done
• Priority: Major
• Resolution: Done
• Fix Version/s: 0.3.0
• Flags: Important
• Assignee: Unassigned
• Reporter: Jon Zeolla
• Created: 18/Oct/16 18:17
• Updated: 11/Nov/16 15:03
• Resolved: 18/Oct/16 19:27

Description

Currently the template provided to Elasticsearch for bro logs is assuming that it will get an ip address in the answers field of a Bro DNS log, however that is not always true. Depending on the type of record being received, the contents could vary between IPs, domain names, or character strings. Various RFCs outline this, however a good starting point is RFC 1035 section 3.3.

Example error:
[1]: index [bro_index_2016.10.18.12], type [bro_doc], id [xyz-abc], message [MapperParsingException[failed to parse [answers]]; nested: IllegalArgumentException[failed to parse ip [something.example.com], not a valid ip address];]