In Search of an Open Source DNS Server

You’d think that in this day and age finding a free and open DNS server would be easy, no? Evidently, not so much. That didn’t keep Roblimo from finding one, however.

Roblimo’s Hideaway

Does it matter whether the DNS server you use is open source? Most of the good ones run proprietary code. But after some tedious shopping and testing, I finally found one that’s open source, community-owned, and (so far, at least) as reliable as its proprietary competitors.

One day Web pages started loading slowly for me. Not just on one computer, but on Linux, Windows, Mac, a Chromebook, and two Android phones. All the devices on my home network were suddenly spending a crazy amount of time displaying things like the FOSS Force front page.

It wasn’t my connection speed. I pay Frontier for 25 Mbps FIOS. I did a fast connection speed test and I was getting 30 down and 30 up. That’s fi

Another problem I’ve had with ISPs over the years is their DNS servers, which can be highly variable in speed, plus there are often privacy issues. And I hate hate hate their “typo penalty,” as I call it, where if you type a character wrong in a URL they shove you onto a bullshit search page instead of leaving the mistyped URL in your search bar so you can correct it.

DNS hijaccking by ISPs is a widespread problem. I first ran into it in Maryland, with my first cable modem connection, which was supplied by a company known (not) affectionately as “Comcursed.” Luckily, I had friends in the Computer Science department of nearby UMBC, and they invited me to use the University’s servers and told me how to change DNS settings in my cable modem. This was long enough ago that I believe 4.2.2.2 was the only public DNS server. At least, it was the only one I knew about, and I didn’t really know if a peon like me was supposed to use it.

Anyway, I got away from Comcast’s DNS servers. My Internet service was suddenly more reliable, the sun broke through the clouds, and life was good.

Years of not thinking about DNS servers

In 2000 my wife and I moved from Maryland to Florida. We hooked up with Time-Warner Cable and it was decent. I forgot all about DNS servers. My connection worked. Sure, there was that DNS hijacking thing, but I didn’t mistype domain names often enough that it was a major irritation. We moved (still in Florida), and decided to go with FIOS, then run by Verizon, because it offered far faster upload speeds than a cable connection. And at the time I was making enough videos that upload speed was a concern.

I still gave no thought to DNS. How often do you think about home or small office DNS servers? If you’re a typical, normal American, the answer is probably “never.” You pay the ISP, you hook your stuff up and set up your wireless, and that’s it. Same here.

Until the black day came when I got a sudden slowdown because my ISP’s DNS server was barfing, possibly because technically ept Verizon had sold their Florida FIOS service to inept Frontier.

So I went hunting for an alternate public DNS server. My first thought was Google DNS, partly because their DNS URLs are 8.8.8.8 and 8.8.4.4. Easy to remember. I found the login info for my ISP-supplied router/switch and a few minutes later I was using Google’s DNS servers, which were way more responsive than Frontier’s.

But I’m crazy. Not only am I part of the 5% (at most) of the population that knows or cares about DNS, but I am part of the even smaller crowd that prefers to use open source software whenever possible, and Google DNS is not open source. Their Public DNS FAQ says, “At this time, there are no plans to open source Google Public DNS. But we have detailed all the steps we have taken to increase speed, security, and standards compliance.”

I wasn’t complaining about the Google DNS servers themselves. They’re quite good. This web page tells you why.

But by God I wanted open source. I knew there was plenty of open source software out there you could use to set up your own DNS server, but I didn’t want that. I wanted a big, robust, reliable DNS service. Like, say, OpenDNS. A few minutes after I decided to try their servers, I had them entered in my router. Worked fine, too. Not noticeably faster or slower than Google DNS, and even a test with DNS Benchmark was inconclusive.

OpenDNS offered, in addition to the DNS servers themselves, free services like identity theft protection and customizable controls to keep your kiddies away from porn. And then, finally, I started looking for OpenDNS’s software licenses. They sponsor some open source projects on GitHub, but the service itself runs on software that’s about as open as Windows. Grrr.

So I went hunting again. Most public DNS servers don’t talk about their software or how it’s licensed. I wonder how many users or potential users ever ask? My guess would be somewhere between “not many” and “none.”

Since I had a little time on my hands, I continued my search for the perfect DNS server I could use on my little home office connection. Finally, the heavens opened and a deep voice said, “OpenNic!” And there, on their front page, in big letters, it said, “Are you looking for an alternative DNS provider that is open and democratic, are you concerned about censorship?” Yes and yes!

Note that providing volunteer-run public DNS servers is only a little of what OpenNic does. It’s really an alternative domain supplier. For some reason, not everyone loves ICANN, AKA “Internet Corporation For Assigned Names and Numbers.” And what if you want a .pirate domain? You can’t get it through an ICANN registrar, but you can get it — along with a bunch of other cool TLDs — through OpenNic.

As a domain server, I’d rate OpenNic as right up there with OpenDNS and Google for speed, and I have had no reliability problems with it. Open source? You bet! Even better, it’s a democratic organization. Jump on the IRC channel. Donate money. Volunteer. Maybe even run an OpenNic server.

Is this some sort of online cult? Possibly. If so, I’m happy to join, even if all I do besides using the DNS servers is donate a little money and lurk in the IRC channel now and then.

Now you know about OpenNic. Check the FAQs, poke at it a bit, and then sign up. Changing DNS settings in your computer or router isn’t hard. There are instructions all over the Internet that will tell you how to do it in Linux, Windows, Mac, Unix, and on many/most/all routers.

As they like to say in the land of trite sayings, “Come on in, the water’s fine.” The trite people also like to say, “You’ll be glad you did.” But this is a case where that is actually true, so (this is the last trite saying in this article) “JUST DO IT!”

The post In Search of an Open Source DNS Server appeared first on FOSS Force.

from FOSS Force http://ift.tt/2j8vvdG
via IFTTT