OpenDNS Phases Out Redirection To Guide
First time accepted submitter Jim Efaw (3484) writes "Tired of the OpenDNS Guide surprise from website-unavailable.com when you go to an old link or a typo from some ISPs? Relief is at hand: On June 6, 2014, OpenDNS will stop redirecting dead hostnames to Guide and its ads; the OpenDNS Guide itself will shut down sometime afterwards. OpenDNS nameservers will start returning normal NXDOMAIN and SERVFAIL messages instead. Phishing protection and optional parental controls will still stay in place."
Control your own DNS
"We can make enough money from selling your IP and the domains you look up."
Wait, how will they make money then?
Oh, right. The usual answer. Selling our data.
My first program:
Hell Segmentation fault
Self referencing article complete with links to itself. Post click bait, profit!
I like the OpenDNS free service, because compared to everything else out there I know of for doing the same job, they suck less than all other options.
Using my ISPs, or VPNs, Google's, or having to roll my own all suck even more.
You can't be ahead of the curve, if you're stuck in a loop.
My company used to use OpenDNS, but then they'd resolve websites that went MIA and our automated scripts wouldn't know that and vomited on what OpenDNS fed them. We're using Google DNS now and it works perfectly. Gets around all the problems introduced by BT mangling the DNSSEC chain.
Being a prepper of sorts, and seeing the Gub'mint positioning itself to hijack DNS in order to exert control (or potentially just shut everything down by attacking this low hanging fruit) I've been looking around for a very specific type of resolver, which can be placed manually into one of several modes:
NORMAL: all lookups are resolved with network queries (as a standalone resolver OR as a 'thin' resolver which just forwards to some upstream DNS server). The results are returned as a real-time resolver does, but are also cached permanently to disk in a database that will inevitably grow over time.
FALLBACK 1, fill in the blanks: when a real result is received yet it is a fail (NOERROR,SRVFAIL,NXDOMAIN), as might be the case in a hypothetical shutdown attack, a stored query that had a positive result is returned.
FALLBACK 2, DNS network down/disabled: all queries are returned from the database and network lookups are not attempted.
So while we are resolving normally a database is being created for emergency use, yet if some disruption to DNS occurs it would be possible to switch to one of the fallback modes to surf -- if not completely, at least with some reasonable level of success...
A desirable feature would be to store a maintainable list of 'poison' ip/net masks of known DHS/ICE webservers, so any A records matching this list are NOT treated as real results, and trigger fallback action. Another desirable feature would be explicit (and implicit via matching of results) recognition of wildcard DNS schemes such as gobblegook.realdomain.com so repeated resolves of these do not overwhelm the database. But there might be some gruesome heuristics behind this.
I realize OpenDNS is in itself a step in this direction, but the local fallback resolver would also give you options for cases when OpenDNS itself is not reachable, such as a hostile/draconian ISP that rewrites DNS packets to point to its own servers.
<blink>down the rabbit hole</blink>
Use OpenNIC instead - less schennigans
The _behavior_ of redirecting failed DNS lookups to an advertising server is unsurprising. Roughly 10 years ago, Verisign did much the same thing to to the master servers for *.com', and broke the concept of getting a "no such record" result for everyone in the world using ".com" addresses.
http://slashdot.org/story/03/0...
Many, many people were _extremely_ upset when this unannounced change occurred. It broke tools worldwide that were used to verify DNS configuraitons, and it routed email that was misspelled or had faild DNS to Verizon's advertising DNS IP addresses. I was never sure if Verisign bothered to do anything with all the DNS connection requests, FTP requests, SSH requests, or everyehing else redirected to their sites, but it left Verisign in charge of a tremendous amount of data and potential network manipulation.
People, and software, have become more accustomed to such DNS abuse. But it's still problematic if you don't realize it's going on.
Verizon just started redirecting their business class DSL users to Yahoo! search results for bad domains a few weeks ago. Maybe that is what changed OpenDNS's mind about the ads -- they decided they didn't want to be as scummy as Verizon ;-) Oh, and Yahoo!, stay classy.
MaraDNS caches to memory, not disk, but will return expired DNS records to the client when there is no answer from authoritative sources.
PowerDNS can connect to a database backend, which can then permanently store a huge collection of DNS records.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
Any modern DNS server has a caching build-in or comes with cached of some sorts.
Having a manually maintained list of hostname-to-ip records is gonna be tricky, since big sites do Geo-balance / load-balance with DNS and may even change IP on the whim.
Take it easy on him. He was abused as a child.
You may make him commit suicide again. He's done it before, you know.
Doesn't look like a lot of people knew this - you could turn this off. I see people complaining about this feature and how it broke their tools when they used it at work, but it was always (afaik) optional and I always had it turned off, if you found it a problem you could have too.
Puts it in perspective, don't you think?
"I realize OpenDNS is in itself a step in this direction, but the local fallback resolver would also give you options for cases when OpenDNS itself is not reachable, such as a hostile/draconian ISP that rewrites DNS packets to point to its own servers."
If your ISP redirect DNS requests, running a resolver will not help you (it makes requests to other servers that will be redirected). So you have to run it somewhere else (making you dependend on other external services) and either use an alternate port for requests or some kind of VPN.
I trust them not to sell my data for marketing purposes : https://developers.google.com/...
he seems to be a pretty fair programmer by mmell (832646) on Friday May 23, 2014 @02:29PM (#47076923) from http://slashdot.org/comments.p...
After all, You're the one that said he's a decent programmer, mmell!
he seems to be a pretty fair programmer by mmell (832646) on Friday May 23, 2014 @02:29PM (#47076923) from http://slashdot.org/comments.p...
You said apk's a decent programmer, mmell!
The problem is that knowing you to be mentally unstable at best, permitting your software to run within my network would be foolish at best, insane at worst. Witness your habit of referring to yourself in the third person. You may think that's perfectly normal, but unless you were born to the blood royal it isn't.
Really - can you possibly believe that you wouldn't be recognized? Have you not noticed that you are not taken seriously here? You're a joke around here, and a bad one at that. A perfectly good programmer incapable of producing a usable program because of concerns regarding your mental health.
This is not a difficult problem to solve. When your issues have been addressed it will become obvious to the rest of us. Until then, any competent administrator will consider your software unsafe for use and you will not be taken seriously. The only possible exception would be people who are unaware of this side of your personality, and it would almost require an act of wilful blindness on the part of a professional administrator.
I'm glad you have chosen to approach this contact more openly. I am perfectly capable of reasonably admitting my mistakes (believe me, I've made quite a few more than you'll ever know about, youngster). I submit that should be your next step as well. It may not be as satisfying as venting your frustration but I think you will find it surprisingly productive.
Hosts fix those. That's a known solution. Updating's easy from a central LAN location (batchfiles, logon scripts, or other scripting tools + scheduled tasks or chronjobs)! DNS also uses more electrical power, cpu cycles, RAM, & other forms of I/O as well, needlessly (hosts compliment DNS in fact).
Hosts solve that & work WITH DNS (I use OpenDNS myself) securing it vs. Kaminsky flaw redirects + fastflux & dynDNS using botnets - THIS program's "best of breed" per Malwarebytes' hpHosts:
APK Hosts File Engine 9.0++ 32/64-bit:
http://start64.com/index.php?o...
(Details of hosts' benefits enumerated in link)
Summary:
---
A. ) Hosts do more than AdBlock ("souled-out" 2 Google/Crippled by default) + Ghostery (Advertiser owned) - "Fox guards henhouse", or Request Policy -> http://yro.slashdot.org/commen...
B. ) Hosts add reliability vs. downed or redirected DNS + secure vs. known malicious domains too -> http://tech.slashdot.org/comme... w/ less added "moving parts" complexity + room 4 breakdown,
C. ) Hosts files yield more speed (blocks ads & hardcodes fav sites - faster than remote DNS), security (vs. malicious domains serving mal-content + block spam/phish & trackers), reliability (vs. downed or Kaminsky redirect vulnerable DNS, 99% = unpatched vs. it & worst @ ISP level + weak vs FastFlux + DynDNS botnets), & anonymity (vs. dns request logs + DNSBL's).
---
Hosts do more w/ less (1 file) @ a faster level (ring 0) vs redundant browser addons (slowing up slower ring 3 browsers) via filtering 4 the IP stack (coded in C, loads w/ OS, & 1st net resolver queried w\ 45++ yrs.of optimization).
* Addons are more complex + slowup browsers & in message passing (use a few concurrently - you'll see)
** Addons slowdown SLOWER usermode browsers layering on MORE - bloating memory consumption too + hugely excessive CPU usage (4++gb extra in FireFox https://blog.mozilla.org/nneth...)
SO - Instead, I work w/ what you have in kernelmode, via hosts (A tightly integrated PART of the IP stack itself)
APK
P.S.=> "The premise is, quite simple: Take something designed by nature & reprogram it to make it work FOR the body, rather than against it..." - Dr. Alice Krippen "I AM LEGEND"
...apk
powerdns can connect to a database backend, which can then permanently store a huge collection of dns records.
thanks kindly, this route looks the most promising.
All; the other relevant details of my response including a sketch of how I could implement this idea are OMITTED because I am being harassed by Slashdot's 'Lameness filter' and rather than engage in some investigatory process (hint: it had nothing to do with CAPS) I said Fuck It. Time to move to Pipedot?.
<blink>down the rabbit hole</blink>