Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] BDNS - a browser addon for accessing OpenNIC TLDs

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] BDNS - a browser addon for accessing OpenNIC TLDs


Chronological Thread 
  • From: "astanze AT blockchain-dns.info" <astanze AT blockchain-dns.info>
  • To: "discuss AT lists.opennicproject.org" <discuss AT lists.opennicproject.org>
  • Subject: Re: [opennic-discuss] BDNS - a browser addon for accessing OpenNIC TLDs
  • Date: Fri, 03 Nov 2017 19:08:07 +0300
  • Authentication-results: mxback18j.mail.yandex.net; dkim=pass header.i= AT blockchain-dns.info

About adding BDNS link to OpenNIC wiki, is it fine to put it above Web Proxies section on the main page?
 
https://wiki.opennic.org/doku.php
 
30.10.2017, 19:22, "Jonah Aragon" <jonah AT triplebit.net>:

Well, been trying this out a bunch more and it does seem to be working great. The extension (debug and Chrome Store versions) works fine on computers that let me load unpacked extensions, so I didn’t really need to do any debugging. It doesn’t work on any of the Chromebooks I’ve tried out here, but I also wasn’t able to install the debug version to find out why because Developer Tools were disabled. Some sort of policy must be getting in the way, but I’m not sure what since all the API endpoints are accessible if I just visit them directly in the browser. Ah well, I’ll investigate further if I have time, but I would still definitely recommend this extension at the moment.

Thanks for the feedback.
 
I don't have any Chromebook to test this on so if you get another time to test this, please try installing one of the alternative extensions, primarily PeerName:
 
https://peername.com/browser-extension/
 
BDNS addon uses the same mechanism as PeerName so it would give me some clue.
 
For mobile devices in general, it seems the only option is Firefox on Android (BDNS works there). iOS and other Android browsers will likely not support addons in any form.
 

“Blockchain-DNS” now strikes me as an inadequate name now that you’ve decided to expand to other alternative roots. Not really an issue, just a thought I had.

You're right. I couldn't have foreseen this development so my primary focus was (and remains) on Emercoin NVS as the perfect decentralized DNS medium. Still, one can use "BDNS" name for short in such cases when referring to other roots.
 

What Tier 2 servers do your servers query to resolve OpenNIC domains? Or is each server its own resolver directly from the root?

For now I simply use one of the two fusl anycasts for all queries (below) because I figure that they already provide some load balancing and failover as my servers are in different countries, plus they resolve nmc/emc domains which makes the setup simpler.
 
169.239.202.202
185.121.177.177
 
Do you see a problem with this approach?
 


Jonah

 
-- 
astanze / PGP key:
https://blockchain-dns.info/astanze.asc
 


  • Re: [opennic-discuss] BDNS - a browser addon for accessing OpenNIC TLDs, astanze AT blockchain-dns.info, 11/03/2017

Archive powered by MHonArc 2.6.19.

Top of Page