4 ms·

Just a reminder for anyone on the fence, or who has not considered it previously... Running your own DNS resolver is super easy. It probably has the highest RO

Just a reminder for anyone on the fence, or who has not considered it previously... Running your own DNS resolver is super easy. It probably has the highest ROI of any self-hosted service, because it is so easy and inexpensive to do. I recommend Unbound: https://nlnetlabs.nl/projects/unbound https://nlnetlabs.nl/projects/unbound

lantry 3y ago
Plus you can do fun things like block ads across your whole network with tools like pihole.
- AnonC 3y ago
  Can you disable the blocking on each device as and when needed (for a little while) and enable it back again (on iOS)? That would be a killer feature for running a DNS server and pi-hole at home.
  - snailmailman 3y ago
    It has a pretty easy “toggle for 5 mins” button on the dashboard if I encounter issues. It has a few preset time options. I think you can set rules per device in Pihole? I haven’t tried personally. I’ve only had set a few (3-4) sites manually allowed through the blocklists.
    - hsdropout 3y ago
      Can be done with a combination of client groups, like this: https://discourse.pi-hole.net/t/client-group-management-how-does-it-work/39554 https://discourse.pi-hole.net/t/client-group-management-how-...
RockRobotRock 3y ago
How slow is running your own recursive DNS?
- quesera 3y ago
  Depends on a few factors: My nameserver, 8.8.8.8, and 1.1.1.1 are all about 25ms away from me. Mine is actually a few ms closer, but that will vary. Bigger nameservers will have warmer caches, so first lookup might be a bit slower on my nameserver. I presume the big nameservers are managed well under capacity, so load should not be significant. All told, I cannot perceive any performance difference at all.
- rubatuga 3y ago
  For my DNS resolver I run, it tends to take around twice as long for the initial request compared to other caching resolvers.
- drexlspivey 3y ago
  It's actually a lot faster since unbound can prefetch and cache your most common queries. Most lookups in my pihole resolve in sub 1ms
  - RockRobotRock 3y ago
    Yeah but that's the same as a regular home DNS server that isn't recursive. Your devices also have their own cache.
    - drexlspivey 3y ago
      The point is that if the TTL is 10mins and you lookup the domain after it expires the regular DNS will go and fetch it, unbound fetches it as soon as it expires and it is already cached
      - RockRobotRock 3y ago
        Thank you, I'm sorry I wasn't aware of the prefetch feature. That's actually pretty cool.
- AndyMcConachie 3y ago
  I run my own resolver on my home network and I never notice anything. When loading a webpage or doing pretty much anything else online the DNS delay is negligible. And if the answer is already cached in my house it's definitely faster than having to leave my home network to get a response.

lantry 3y ago

Plus you can do fun things like block ads across your whole network with tools like pihole.

AnonC 3y ago
Can you disable the blocking on each device as and when needed (for a little while) and enable it back again (on iOS)? That would be a killer feature for running a DNS server and pi-hole at home.
- snailmailman 3y ago
  It has a pretty easy “toggle for 5 mins” button on the dashboard if I encounter issues. It has a few preset time options. I think you can set rules per device in Pihole? I haven’t tried personally. I’ve only had set a few (3-4) sites manually allowed through the blocklists.
  - hsdropout 3y ago
    Can be done with a combination of client groups, like this: https://discourse.pi-hole.net/t/client-group-management-how-does-it-work/39554 https://discourse.pi-hole.net/t/client-group-management-how-...

RockRobotRock 3y ago

How slow is running your own recursive DNS?

quesera 3y ago
Depends on a few factors: My nameserver, 8.8.8.8, and 1.1.1.1 are all about 25ms away from me. Mine is actually a few ms closer, but that will vary. Bigger nameservers will have warmer caches, so first lookup might be a bit slower on my nameserver. I presume the big nameservers are managed well under capacity, so load should not be significant. All told, I cannot perceive any performance difference at all.
rubatuga 3y ago
For my DNS resolver I run, it tends to take around twice as long for the initial request compared to other caching resolvers.
drexlspivey 3y ago
It's actually a lot faster since unbound can prefetch and cache your most common queries. Most lookups in my pihole resolve in sub 1ms
- RockRobotRock 3y ago
  Yeah but that's the same as a regular home DNS server that isn't recursive. Your devices also have their own cache.
  - drexlspivey 3y ago
    The point is that if the TTL is 10mins and you lookup the domain after it expires the regular DNS will go and fetch it, unbound fetches it as soon as it expires and it is already cached
    - RockRobotRock 3y ago
      Thank you, I'm sorry I wasn't aware of the prefetch feature. That's actually pretty cool.
AndyMcConachie 3y ago
I run my own resolver on my home network and I never notice anything. When loading a webpage or doing pretty much anything else online the DNS delay is negligible. And if the answer is already cached in my house it's definitely faster than having to leave my home network to get a response.