Hi everyone, I am suspicious that it's some recent filter due to last vulnerability of > bind. It could not be?
I currently have exactly same issue after bind99 update on my DNS platform. And I don't know why only *.freebsd.org domains seems to be impacted. Name : bind99 [26/893] Version : 9.9.6P1 Installed on : Tue Dec 23 11:21:51 CET 2014 Origin : dns/bind99 Architecture : freebsd:9:x86:64 Prefix : /usr/local Categories : net ipv6 dns Licenses : ISCL Maintainer : m...@freebsd.org WWW : https://www.isc.org/software/bind Comment : BIND DNS suite with updated DNSSEC and DNS64 Options : DLZ_BDB : off DLZ_FILESYSTEM : off DLZ_LDAP : off DLZ_MYSQL : off DLZ_POSTGRESQL : off DLZ_STUB : off DOCS : on FILTER_AAAA : off FIXED_RRSET : off GOST : off GSSAPI_BASE : off GSSAPI_HEIMDAL : off GSSAPI_MIT : off GSSAPI_NONE : on IDN : on IPV6 : on LARGE_FILE : on LINKS : off NEWSTATS : off PYTHON : off REPLACE_BASE : off RPZ_NSDNAME : off RPZ_NSIP : off RPZ_PATCH : off RRL : off SIGCHASE : off SSL : on THREADS : on Shared Libs required: libxml2.so.2 libidnkit.so.1 libiconv.so.2 libcrypto.so.8 ​ ​If you have an idea why...​ _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
