On Sun, 16 Aug 2015, Kimmo Paasiala wrote:
It could be the classic fall back to TCP on SRV records problem on
your upstream DNS forwarder if you're using one:
http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/074801.html
The cure would be to use your own caching DNS resolver (configured to
query the authoritative name servers directly) such as dns/unbound.
2015-08-16 Christian Kratzer wrote:
I run my own bind9 resolvers on freebsd 10 at both sites. I never
particurlarly like the concept of an "upstream" resolver.
All my resolvers are behind firewalls although different kinds.
ASA at one site and freebsd pf at the other.
I will investigate though. Thanks for the tip.
ASA firewall has a nasty setting to *discard* DNS UDP packets
with UDP message size over 512 bytes, i.e. it does not allow EDNS0
option. Check that you have this DNS deep packet inspection
misfeature turned off. Check also the firewall log.
This would affect UDP DNS responses to a SRV query
_http._tcp.update.FreeBSD.org, which comes close to the size limit
(possibly depending on geolocation). Using google's public DNS server
may avoid the problem by stripping nonessential records from the
DNS reply (like the ADDITIONAL SECTION).
Mark
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
