[GH-ISSUE #50] clarification on how to set different answer per geo #37

New issue

Open

opened 2026-02-28 14:16:01 +03:00 by kerem · 4 comments

kerem commented

2026-02-28 14:16:01 +03:00

Owner

Originally created by @anuaimi on GitHub (Jan 8, 2014).
Original GitHub issue: https://github.com/abh/geodns/issues/50

I've got geodns up and running with a sample zone file. What's not clear is how I set different answers for different Geos. Do I just add the geo after the record name. As an example:

"www" : { "a" : "192.168.0.1" },
"www.us" : { "a" : "192.168.1.1" },
"www.ca" : " { "a" : "192.168.2.1"},
"www.europe" : {"a" : 192.168.3.1" }

And is there a way to have different answers for different US states?

thanks in advance

Originally created by @anuaimi on GitHub (Jan 8, 2014). Original GitHub issue: https://github.com/abh/geodns/issues/50 I've got geodns up and running with a sample zone file. What's not clear is how I set different answers for different Geos. Do I just add the geo after the record name. As an example: "www" : { "a" : "192.168.0.1" }, "www.us" : { "a" : "192.168.1.1" }, "www.ca" : " { "a" : "192.168.2.1"}, "www.europe" : {"a" : 192.168.3.1" } And is there a way to have different answers for different US states? thanks in advance

kerem commented

2026-02-28 14:16:01 +03:00

Author

Owner

@abh commented on GitHub (Jan 13, 2014):

Yup, that's basically it!

To get different answers for US states you need the GeoCity database installed and then you add a "targeting" key in the zone json, like:

     "targeting": "@ continent country regiongroup region",

@, continent, country are the defaults. regiongroup are "us-west", "us-central" and "us-east". region are "us-ca", "us-az", "us-ny", etc. Regions are only supported for the US.

Ask

@abh commented on GitHub (Jan 13, 2014): Yup, that's basically it! To get different answers for US states you need the GeoCity database installed and then you add a "targeting" key in the zone json, like: ``` "targeting": "@ continent country regiongroup region", ``` @, continent, country are the defaults. regiongroup are "us-west", "us-central" and "us-east". region are "us-ca", "us-az", "us-ny", etc. Regions are only supported for the US. Ask

kerem commented

2026-02-28 14:16:01 +03:00

Author

Owner

@aredondo commented on GitHub (May 13, 2014):

With subdomains, this works fine. But how can I add geo-based responses for the apex? I have tried:

".europe": { "a": [ [ … ] ] }
"domain.europe": { "a": [ [ … ] ] }
"domain..europe": { "a": [ [ … ] ] }
"@.europe": { "a": [ [ … ] ] }

But none seem to work.

In addition, an entry without geographic information is used as default when the source of the request cannot be determined?

@aredondo commented on GitHub (May 13, 2014): With subdomains, this works fine. But how can I add geo-based responses for the apex? I have tried: - ".europe": { "a": [ [ … ] ] } - "domain.europe": { "a": [ [ … ] ] } - "domain..europe": { "a": [ [ … ] ] } - "@.europe": { "a": [ [ … ] ] } But none seem to work. In addition, an entry without geographic information is used as default when the source of the request cannot be determined?

kerem commented

2026-02-28 14:16:02 +03:00

Author

Owner

@abh commented on GitHub (May 14, 2014):

Simpler than you thought! :-)

For the default records:

"": { "a": ... }

target to europe:

"europe": { "a": ... }

etc.

@abh commented on GitHub (May 14, 2014): Simpler than you thought! :-) For the default records: - "": { "a": ... } target to europe: - "europe": { "a": ... } etc.

kerem commented

2026-02-28 14:16:02 +03:00

Author

Owner

@ghpass commented on GitHub (Dec 15, 2015):

maybe "europe" is a host name. so how to make a distinction between host name and region?
I don't know how to configure as the feature "view" in bind.

@ghpass commented on GitHub (Dec 15, 2015): maybe "europe" is a host name. so how to make a distinction between host name and region? I don't know how to configure as the feature "view" in bind.