[GH-ISSUE #43] match-clients equivalent (or mapping blocks/ip to countries) #182

New issue

Open

opened 2026-03-01 17:24:24 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 17:24:24 +03:00

Owner

Originally created by @julienmru on GitHub (Sep 16, 2013).
Original GitHub issue: https://github.com/abh/geodns/issues/43

For developing countries, MaxMind database is unreliable but we can find resolver IP addresses/blocks from relevant ISPs and thus have accurate data thanks to the resolver.

It would be perfect if geodns allowed to manually map addresses/blocks to specific countries, taking priority over what MaxMind returns, more or less what we would do in bind with match-clients.

Originally created by @julienmru on GitHub (Sep 16, 2013). Original GitHub issue: https://github.com/abh/geodns/issues/43 For developing countries, MaxMind database is unreliable but we can find resolver IP addresses/blocks from relevant ISPs and thus have accurate data thanks to the resolver. It would be perfect if geodns allowed to manually map addresses/blocks to specific countries, taking priority over what MaxMind returns, more or less what we would do in bind with match-clients.

kerem commented

2026-03-01 17:24:25 +03:00

Author

Owner

@stutiredboy commented on GitHub (Jul 1, 2015):

mm, MaxMind is not enough.

@stutiredboy commented on GitHub (Jul 1, 2015): mm, MaxMind is not enough.

kerem commented

2026-03-01 17:24:25 +03:00

Author

Owner

@abh commented on GitHub (Jul 3, 2015):

I don't think it'd be right to make a generic geoip facility in geodns. It shouldn't be terribly difficult to write maxmind compatible databases and use those; or if there's another data format GeoDNS should support then I'd be open to that.

Another option is to tell MaxMind -- in my experience they are pretty responsive about updating their data. :-)

@abh commented on GitHub (Jul 3, 2015): I don't think it'd be right to make a generic geoip facility in geodns. It shouldn't be terribly difficult to write maxmind compatible databases and use those; or if there's another data format GeoDNS should support then I'd be open to that. Another option is to tell MaxMind -- in my experience they are pretty responsive about updating their data. :-)

kerem commented

2026-03-01 17:24:25 +03:00

Author

Owner

@julienmru commented on GitHub (Jul 4, 2015):

Thanks @abh but I do have a valid use case where manually specifying ranges would help: in Mauritius, some operators route traffic to South-East-Asia, and other operators route traffic to Europe. With help of manual ranges, I could have geodns resolve the closest IP for each operator.

I'm not thinking about writing MaxMind compatible database because the ones we have with our subscription shouldn't be overwritten.

Not sure if that makes sense :)

@julienmru commented on GitHub (Jul 4, 2015): Thanks @abh but I do have a valid use case where manually specifying ranges would help: in Mauritius, some operators route traffic to South-East-Asia, and other operators route traffic to Europe. With help of manual ranges, I could have geodns resolve the closest IP for each operator. I'm not thinking about writing MaxMind compatible database because the ones we have with our subscription shouldn't be overwritten. Not sure if that makes sense :)

kerem commented

2026-03-01 17:24:25 +03:00

Author

Owner

@abh commented on GitHub (Jul 4, 2015):

In v2.5.0 there's support for targeting by IP, but only the specific IP or the /24 network (/48 for IPv6). I believe you specify it with the IP address (instead of the country code) or the first three octets of the IP address. If it's not too many networks you have to override that might work.

@abh commented on GitHub (Jul 4, 2015): In v2.5.0 there's support for targeting by IP, but only the specific IP or the /24 network (/48 for IPv6). I believe you specify it with the IP address (instead of the country code) or the first three octets of the IP address. If it's not too many networks you have to override that might work.