Rate-limiting on DNS lookups?
I'm evaluating NextDNS for a possible educational campus purchase. So far, love the product. I purchased the standard package for testing.
Few questions:
- Is there any rate-limiting set on the DNS servers? We would have periods with a few hundred students pounding it at peak periods of 3-4000 DNS looksups a minute. I ran a dnsperf test against my assigned ipv4 address and it fell apart pretty quickly and started blocking once it was loaded up. What's the threshold?
- Is there any way around the limitation of one public IP address to one NextDNS DNS server config?
I understand you have to do it because somebody across the street from me could have the next sequential address, but if I own the entire /24 for my subnet, can we define a /24 for my entire NAT pool rather than make 200 separate configurations?
Great product, fantastic for the consumer at a really reasonable price (I'll end up using it at home after this eval). Just curious how far you stretch into the larger user count.
Thank you!
2 replies
-
If you have a /24 range for your outbound NAT pool (ie: 66.66.66.1-254) you might have 200 of the addresses in that range used for outbound NAT access from your internal clients. I could probably fudge around this but just more generally curious if it can be done on the system side. I could also see the situation where a campus environment would have multiple gateways to the internet and they would want to keep the ruleset consistent across all of them.
It looks like the only way to do that (easily) is using the Firefox plugin to backup/restore the setting to each configuration. Again, not the end of the world, but kind of a pain if you have 20 buildings with individual (non-tunneled) access to the internet.
-
Please contact us via education@nextdns.io
Content aside
- 2 yrs agoLast active
- 2Replies
- 186Views
-
3
Following