Forum Discussion

Copper Contributor

Jan 29, 2018

Solved

OMS DNS Analytics solution discrepancy

I have configured custom OMS workspace with the DNS Analytics solution enabled. For testing purposes I have generated 43K+ random name resolution queries on test VM against the DNS server that is rep...

azure monitor

OMS

Vedran Matica
Jan 30, 2018
Noa,

I figured it out in the meantime. Random domain name lookup queries were generated with characters which are invalid according to the DNS RFC specification. After excluding invalid characters from lookups, I am getting results which are aligned with the testing scenario.

Kind regards,

Vedran

Noa Kuperberg

Microsoft

Jan 30, 2018

Hi Verdan, in that case I would contact support to review what went wrong.

Noa

Vedran Matica

Copper Contributor

Jan 30, 2018

Noa,

I figured it out in the meantime. Random domain name lookup queries were generated with characters which are invalid according to the DNS RFC specification. After excluding invalid characters from lookups, I am getting results which are aligned with the testing scenario.

Kind regards,

Vedran

Noa Kuperberg
Microsoft
Feb 05, 2018
Glad to hear that, we learned something new.
If you'd like to post your query here we can also use it to add a documentation article or note on that use case.
Thanks for sharing Vedran!
- Vedran Matica
  Copper Contributor
  Feb 05, 2018
  Glad to help, but actually there is nothing to share. I didn't come up with particularly special Log Analytics Query Language query.
  
  I made amendments on the DNS client side (device generating random DNS queries for testing purposes), meaning that random DNS queries were modified to exclude characters which are invalid per DNS RFC.