Not sure if it's ok to ask this here. If not, I apologize.
Expected Behaviour:
DNS Lookups should complete for DNS sites already visited in a reasonable time.
Actual Behaviour:
DNS lookups will often fail for random times for 15-30 seconds at a time, even for websites I normally visit on a daily basis. Doing the dig command returns a connection timed out message.
A couple days ago, I decided to check out DNS encrypting. Initially looked up DNS Crypt with Cloudfare, but then found unbound and decided to go with that. Used the guide here:
Installation went fine. And for the most part, seemed to work. At first, DNS lookups were slow (sometimes took around 10-20 seconds for it to complete at first). But I expected browsing to be somewhat slow at first. And after, seemed to be normal.
But I've noticed, that sometimes, at random times, DNS just doesn't work, for sites I have visited (or normally visit on a daily basis). Seemed odd, as those DNS lookups should be cached (at least that what I understood it would do). Sites would be down for 15-30 seconds at a time.
It doesn't take down the whole internet. During that time where I try and visit a site and DNS doesn't work, I can visit other websites just fine. When I run the command: dig somedomain.com @127.0.0.1 -p 5353
I'll get:
; <<>> DiG 9.9.5-9+deb8u6-Raspbian <<>> somedomain.com @127.0.0.1 -p 5353
;; global options: +cmd
;; connection timed out; no servers could be reached
I have the most update to date roots file (updated yesterday, July 26). The config file is the default from the guide above.
I checked dns lookup via 8.8.8.8, and it worked fine.
It doesn't last long, maybe 30 seconds at latest. But can be slightly annoying to deal with.