search

namecoin / proposals

Standards and Best Practices
Creative Commons Zero v1.0 Universal
12 stars 5 forks source link

GeoDNS #20

Open JeremyRand opened 8 years ago

JeremyRand commented 8 years ago

It would be potentially interesting to support GeoDNS use cases. This would provide a clear speed benefit to domain owners who use the Namecoin blockchain.

It might be arguable that this would harm scalability, but I think it could also be argued that the number of domains that actually use complex GeoDNS configurations is low enough, and the financial resources of those domain owners is high enough, that this isn't really a scalability issue. More research would be useful to figure out whether this is a scalability dealbreaker.

@hlandau and I discussed this on IRC a while back.

indolering commented 8 years ago

We could just add a "geo" attribute with values for 2-letter country codes and values for macro-regions and sub-regions based on M29.

I would advise against non-standard sub-regions like US-west or state-level encoding. Values below the resolution of macro regions are silly in DNS. It just doesn't scale well in terms of administrative overhead and the resolution of the geo information available on the client side isn't that great unless you query an IP location database.