71–80 of 97 posts
Nextdns.io and cloudflare externally. Pi-hole pointing to those internally. Preferably encrypted. Preferably with Firefox due to esni support.
One question popped into my head is how do you trust nextdns? or are you doing something so that you do not need to trust it?
I run my own DNS servers at home. I have a small virtualization cluster and run a small DNS vm on each physical host. My resolvers perform queries against the root servers directly and cache results. It's refreshing to skip all the DNS fuckery that's going on nowadays.
Earlier quoted context omitted.
What, exactly, does "sending your IP all around the internet" even mean?
Meaning, if you don't want people to know you are searching for snm.donkeyporn.com than going out to the nameserver that donkeyporn is using is not exactly keeping the information private.
I personally feel that concentrating all the information of "what DNS names are people looking up" into the hands of a few parties (e.g. CloudFlare) makes it much easier to collect and analyze this information.
I run my own DNS servers at home. I have a small virtualization cluster and run a small DNS vm on each physical host. My resolvers perform queries against the root servers directly and cache results. It's refreshing to skip all the DNS fuckery that's going on nowadays.
I run my own DNS servers at home. I have a small virtualization cluster and run a small DNS vm on each physical host. My resolvers perform queries against the root servers directly and cache results. It's refreshing to skip all the DNS fuckery that's going on nowadays.
I tried doing the same, how do you precache and reduce query lookup times for a new website ? Could you explain your setup if you don’t mind ?
I run the same setup, local resolver that recurses from the roots, and I don't cache anything other than what my systems actually request. If I hit a new site, I pay the penalty for not having certain information cached.
Hows the DNS server to know what to pre-cache to reduce lookup times?
Even for something that is not in the cache DNS is lightweight and quick, and I have full control over when to flush it, and have logs.
I am not huge fan of the trend of various device manufacturers (looking at you Google, and now Apple too) sending queries over DoH instead of using the local resolver on my network :/
for i in `cat dns_list.txt|grep -v '^#'` do qt=`dig @$i archive.is| grep "Query time:" |cut -f2 -d ':'` echo "$i: $qt" done
Neat, this helped me realize I haven't switched away from my provider's default DNS when I moved in, which is something I usually do. How to choose a DNS server? I usually just go with 8.8.8.8/8.8.4.4, I used to always test this with Namebench ( https://en.wikipedia.org/wiki/Namebench ) and these always turned out as the fastest - but it looks like it hasn't been updated since 2010 - are there any better tools for th…
If I'm not mistaken you can use DNSSEC to authenticate, but not encrypt, your DNS requests. For me however, the simpler way was to just use DoT/DoH. I haven't noticed any slowdowns.
If you care about performance, you could check if your system caches DNS responses and configure that cache accordingly.
Neat, this helped me realize I haven't switched away from my provider's default DNS when I moved in, which is something I usually do. How to choose a DNS server? I usually just go with 8.8.8.8/8.8.4.4, I used to always test this with Namebench ( https://en.wikipedia.org/wiki/Namebench ) and these always turned out as the fastest - but it looks like it hasn't been updated since 2010 - are there any better tools for th…
> I think privacy should be on a different layer. Can you elaborate which layer?
Is it possible these privacy/filtering DNS services like NextDNS come without a performance hit? Imagine setting it up and forgetting about it, and discovering later that all your DNS queries happened with a substantial lag - it's like realizing you've been driving with a hand brake on