DNS recommendations
-
Any suggestions about the most reliable DNS for pfSense?
-
Huh? What do you mean by reliable? I've not seen much in the way of problems with DNS Forwarder, DNS Resolver or Bind. Are you having a DNS problem that you are trying to solve?
-
The best solution for the vast majority of use cases would be the default unbound as full resolver, doing dnssec.
If your in a situation that where resolving is an issue, then maybe the forwarder dnsmasq might be better suited that unbound in forwarder mode. If you need to be an authoritative nameserver or need to do zone transfers or some of the other features that bind can do, like AAAA filtering than that might be the best solution for that use case.
As KOM so rightly points out if you want advice to what might be best suited for your use case, then we need to understand your use case or feature needs, etc. But most of the time, unbound as it out of the box will be fine and the best choice. Since your sure to be using dnssec, etc
-
@KOM:
Huh? What do you mean by reliable? I've not seen much in the way of problems with DNS Forwarder, DNS Resolver or Bind. Are you having a DNS problem that you are trying to solve?
This isn't specifically a pfSense issue, I'm using an optical fibre system provided by Orange and almost always get these sorts of error msgs when trying access pages from Google or YouTube.
This site can’t be reached
The webpage at https://www.google.pl/search?q=pfsense&oq=pfsense&aqs=chrome..69i57j69i60l2j69i61j69i59.3685j0j8&sourceid=chrome&ie=UTF-8 might be temporarily down or it may have moved permanently to a new web address.
ERR_QUIC_PROTOCOL_ERRORI want to change the DNS set by the router to something else and would like reccommendations, as I can't figure out what is causing these errors.
Using Yahoo as a search engine works fine, but Google invariably returns the above error.
-
Why do you think that has anything to do with dns???
ERR_QUIC_PROTOCOL_ERROR
Do you know what quic is?? Quic is http over UDP.. I would assume that is more related to your problem then looking up www.google.pl
what browser are you using? Chrome? Disable quic I think you can do it like this
In the URL type "chrome://flags"- Search for "Experimental QUIC protocol" and disable it
Are you blocking outbound udp?
-
Why do you think that has anything to do with dns???
ERR_QUIC_PROTOCOL_ERROR
Do you know what quic is?? Quic is http over UDP.. I would assume that is more related to your problem then looking up www.google.pl
what browser are you using? Chrome? Disable quic I think you can do it like this
In the URL type "chrome://flags"- Search for "Experimental QUIC protocol" and disable it
Are you blocking outbound udp?
I've never heard of QUIC but following your advice I have disabled it in Chrome and now have no problems accessing Google.
Many thanks and sorry for misdiagnosing the problem.
-
While that is a work around for sure.. Something not right with your connection if your having that many problems with udp.. Is your pipe full? is it shitty/slow ?
your not blocking it outbound are you? You prob want to get with your isp if your having problems with udp connections.
As to the misdiagnosis, that is why we are here - but we need info to help ;)
