MAP Advanced Query - Inconsistent query results with Destination hostname

[Andrew-Clement]

Query on Originate Destination Hostname vs Terminate Destination Hostname gives different results:

For Destination Hostname, preferaby it shouldn't matter which. Or there should be an indication that Terminate Destination Hostname is invalid and requires Originate.

originate : destHostName : utoronto.ca
1119 Traceroutes Found
Displaying 1 of a sample of 20 search results
Search results details...
does : originate : destHostName : utoronto.ca : and | Traceroutes: 1119

terminate
902 Traceroutes Found
Displaying 1 of a sample of 20 search results
Search results details...
does : terminate : destHostName : utoronto.ca : and | Traceroutes: 902

GoVia
1488 Traceroutes Found
Displaying 1 of a sample of 20 search results
Search results details...
does : goVia : destHostName : utoronto.ca : and | Traceroutes: 1488

Contain
1488 Traceroutes Found
Displaying 1 of a sample of 20 search results
Search results details...
does : goVia : destHostName : utoronto.ca : and | Traceroutes: 1488

[agamba]

The proper way of searching for traceroutes using the destination hostname is "CONTAIN"
this is the most inclusive. All the other need to be prevented. My guess is that this can be done on the server side but in can also be auto selected on the front-end, and providing some explanation to the user.

does : originate : destHostName : utoronto.ca : and | Traceroutes: 1131
does : terminate : destHostName : utoronto.ca : and | Traceroutes: 902
does : goVia : destHostName : utoronto.ca : and | Traceroutes: 1500
does : contain : destHostName : utoronto.ca : and | Traceroutes: 1507