closest match algorithm in play?
Mon Mar 4 21:19:19 CET 2019
i get multiple records from a query where i have zones that overlap. somehow i had gotten the impression that "best match" was in play? is that not the case? how do i achieve a "sieve" effect here?
in a combined dataset:
$DATASET ip4trie:test test
given a query "126.96.36.199.test.example.com", i'd expect to see "127.0.0.16"
given a query "188.8.131.52.test.example.com", i'd expect to see "127.0.0.24", but i get both records back. huh?
admittedly, it does match both zones, but i really just want the more "exact" match.
More information about the dev