[GH-ISSUE #67] Domain geo record clarification #53

Closed
opened 2026-02-28 14:16:06 +03:00 by kerem · 5 comments
Owner

Originally created by @gugansankar on GitHub (Jul 7, 2015).
Original GitHub issue: https://github.com/abh/geodns/issues/67

I'm planning to migrate my dns from pgeodns to this version. But When I look into the sample configuration of ntp , the entries are making me some confusion on geo record.

What is difference between the below record for country Malaysia

3.my , 1.my , 0.my ,2.my from ntppool.org.json

Originally created by @gugansankar on GitHub (Jul 7, 2015). Original GitHub issue: https://github.com/abh/geodns/issues/67 I'm planning to migrate my dns from pgeodns to this version. But When I look into the sample configuration of ntp , the entries are making me some confusion on geo record. What is difference between the below record for country Malaysia 3.my , 1.my , 0.my ,2.my from ntppool.org.json
kerem closed this issue 2026-02-28 14:16:06 +03:00
Author
Owner

@gugansankar commented on GitHub (Jul 28, 2015):

Any idea ?

<!-- gh-comment-id:125483940 --> @gugansankar commented on GitHub (Jul 28, 2015): Any idea ?
Author
Owner

@abh commented on GitHub (Sep 6, 2015):

Instead of "3", "1", etc think of "www". So if your domain is "example.com" then you make a global/default entry "www" and another "www.my" for users in Malaysia. Does that make sense?

<!-- gh-comment-id:138137099 --> @abh commented on GitHub (Sep 6, 2015): Instead of "3", "1", etc think of "www". So if your domain is "example.com" then you make a global/default entry "www" and another "www.my" for users in Malaysia. Does that make sense?
Author
Owner

@abh commented on GitHub (Sep 6, 2015):

Since you are migrating from pgeodns you might also be interested in the geodes-config program that's in the pgeodns repository. It converts the old pgeodns text configuration format to the JSON format:

https://github.com/abh/pgeodns/blob/master/geodns-config

We actually still use this for some of the perl.org data. (!)

<!-- gh-comment-id:138137279 --> @abh commented on GitHub (Sep 6, 2015): Since you are migrating from pgeodns you might also be interested in the geodes-config program that's in the pgeodns repository. It converts the old pgeodns text configuration format to the JSON format: https://github.com/abh/pgeodns/blob/master/geodns-config We actually still use this for some of the perl.org data. (!)
Author
Owner

@gugansankar commented on GitHub (Sep 7, 2015):

Thanks for your explanation. I already start using Go-GeoDNS.

<!-- gh-comment-id:138195009 --> @gugansankar commented on GitHub (Sep 7, 2015): Thanks for your explanation. I already start using Go-GeoDNS.
Author
Owner

@abh commented on GitHub (Sep 13, 2015):

Very cool. Thank you for following up. 👍

<!-- gh-comment-id:139928977 --> @abh commented on GitHub (Sep 13, 2015): Very cool. Thank you for following up. :+1:
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/geodns#53
No description provided.