3 ms·
"But missing the point. If I am worried about privacy from cloud players, why to trust another cloud player?" The workflow I am (not quite finished) setting up
by rsync 6y ago
"But missing the point. If I am worried about privacy from cloud players, why to trust another cloud player?"
The workflow I am (not quite finished) setting up is as follows - I run a caching, recursive nameserver (unbound) in my own colo space. That DNS server, not me or my devices, is the nextDNS client.
Then I set all of my own networks and devices to use my (unbound) DNS server.
My goal is to receive all of the benefits of a paid nextdns account, but on the nextdns side, all they see is a single, fixed IP, in a fixed location, owned by a corporate entity, doing a bunch of DNS queries.
In fact, I am a bit worried about this exact setup because although I am using this for my own, personal use, consistent with their expectations, I could just as easily be a full-blown ISP passing through my nameservice to nextDNS ... how do they deal with that ?
Do they care ?
- BenjiWiebe 6y agoTotally guessing here. If they saw one IP making ISP-rate queries they could contact you and negotiate a different price. Even with caching you are very likely going to see much higher query rates occasionally when a whole network of people are using it.
- thanksforfish 6y agoYou personally make a many DNS queries as a full-blown ISP? The fact that your server does it's own caching may keep your query rate lower than others. I'm sure they can refuse service to customers in certain cases.
- rsync 6y agoNo, I wouldn't make anywhere near that number of DNS requests, but the setup would be the same - a caching, forwarding nameserver doing a MITM between my networks and nextDNS. So I assume they allow (or, rather, can't really disallow) such a setup but I wonder what ramifications it has when someone decides to front their entire customer base behind their nextDNS acount ...
- thanksforfish 6y agoI'd assume they would just ask them to stop.