> > > > I don't know if this will be usable for your case, here at home the aDSL > > > > modem tries to be the resolver. The trouble is with the ISP: their DNS > > > > servers are quite frequently unreliable and unstable. They even affect > > > > the PPP connection sate, as the modem firmware uses that to trigger self > > > > induced reboots, while link is present and working. You can imagine how > > > > frustrating this can be for users not realising what's going on in > > > > fact. > > > > > > Yes, I agree completely. It is very frustrating. And of course, I want > > > to use sites that must have DNS working right now. > > > I could use my phone as a hotspot, but I need to use that money for > > > something else more important. One time, both systems for DNS went down! > > > > I've had this many many times, the DSL service is more than 12 years active > > and this trick went into production on the first day it came in service ;-) > > > > > > To solve this, multiple times with various different locations, I ended > > > > up setting up local resolving DNS server, recently this became Unbound, > > > > on the gateway OpenBSD system, and it does resolution directly querying > > > > root DNS servers. I think this solved it for me ultimately many times. > > > > For this ISP, this is the solution here, I believe this can help > > > > others. > > > > > > Well, in any case, I should learn how to use Unbound. Hopefully that can > > > help. And if not right here, maybe other spots with that problem. I've > > > had this problem with my laptop in many places with free wifi. > > > > It will. If the ISP you're going through does capture all outgoing DNS > > traffic and force redirects it through their name serverice, another go > > at it is to optionally tunnel out (ssh, or anything else) and use DNS > > service via the tunnelled connection. Either set Unbound, or another > > recursive resolver there and use it for your resolver, or simply pass > > your DNS traffic for your own resolving name server through the tunnel. > > The Unbound DNS resolver is in base, let me know if you need any tech > > details with this in direct message and I'll add more specific details. > > > > I expect to need some help. I will read up on unbound and some other > stuff first. I appreciate the help.
Locate your configuration file in /var/unbound/etc/unbound.conf and adjust as required. Probably nothing required to configure at first if you run it locally on the same system where you use the resulting DNS resolution. The details are pretty self explanatory, there is a very concise and useful manual page unbound.conf(5) (same as online) unbound.conf - Unbound configuration file [http://man.openbsd.org/unbound.conf] I don't remember having to copy the initial configuration file from examples or another location, so this means it must have been there all along. To start use, set your resolver to 127.0.0.1 and issue: # rcctl enable unbound # rcctl start unbound You can always read other material later, just try it. Also Stuart sent one very Excellent DNS troubleshooting post for your reference. > Have a good day (night)!
