4 ms·

I had to stop using 1.1.1.1 because I am getting rate limited when using their “cloudflared” dns-over-https proxy. My pretty modest home network and the various

I had to stop using 1.1.1.1 because I am getting rate limited when using their “cloudflared” dns-over-https proxy. My pretty modest home network and the various services running make 20-25k queries per day and I get a lot of REFUSED responses. Google on the other hand has no problem serving all of them. I even set a local cache to bypass the dns TTL but the problem is that sometimes 10 or more queries arrive at the same moment from a service.

omegalulw 5y ago
Why can't you not set up a local DNS on any PC backed by 1.1.1.1 if you really want to stay with Cloudflare?
jgrahamc 5y ago
Did you talk to someone at Cloudflare about this? That sounds... odd.
- elithrar 5y ago
  As John says - sounds odd - but please drop me an email with more details - silverlock at cloudflare Understanding the # of unique names, peak QPS, % of response types, etc will help. I consider it a “bug” if you can take the same profile of DNS queries to another resolver and see no issues ;-)
danuker 5y ago
> 10 or more queries arrive at the same moment from a service. I suspect you hit some sub-second ratelimit.
FunnyLookinHat 5y ago
That's not too many requests, but running any form of a home network would still benefit moderately from a local DNS server. You could even install something like dnsmasq on the most heavy-using boxes to cache lookups locally. Granted, I'm saying this as yet another home-network admin who hasn't quite... ahem... gotten around to installing a DNS server. ^_^; I'm mostly sharing this here in case someone else has a similar problem and wants a solution.
- drexlspivey 5y ago
  I am running a pihole and I have set a minimum TTL of 40 minutes for the local cache, my setup is pihole --> local DoH proxy --> 1.1.1.1 as described here https://docs.pi-hole.net/guides/dns/cloudflared/ https://docs.pi-hole.net/guides/dns/cloudflared/
- mlac 5y ago
  Pi-hole with Tailscale checking in here. Easy to set up.

omegalulw 5y ago

Why can't you not set up a local DNS on any PC backed by 1.1.1.1 if you really want to stay with Cloudflare?

jgrahamc 5y ago

Did you talk to someone at Cloudflare about this? That sounds... odd.

elithrar 5y ago
As John says - sounds odd - but please drop me an email with more details - silverlock at cloudflare Understanding the # of unique names, peak QPS, % of response types, etc will help. I consider it a “bug” if you can take the same profile of DNS queries to another resolver and see no issues ;-)

danuker 5y ago

> 10 or more queries arrive at the same moment from a service. I suspect you hit some sub-second ratelimit.

FunnyLookinHat 5y ago

That's not too many requests, but running any form of a home network would still benefit moderately from a local DNS server. You could even install something like dnsmasq on the most heavy-using boxes to cache lookups locally. Granted, I'm saying this as yet another home-network admin who hasn't quite... ahem... gotten around to installing a DNS server. ^_^; I'm mostly sharing this here in case someone else has a similar problem and wants a solution.

drexlspivey 5y ago
I am running a pihole and I have set a minimum TTL of 40 minutes for the local cache, my setup is pihole --> local DoH proxy --> 1.1.1.1 as described here https://docs.pi-hole.net/guides/dns/cloudflared/ https://docs.pi-hole.net/guides/dns/cloudflared/
mlac 5y ago
Pi-hole with Tailscale checking in here. Easy to set up.