-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Wed, 2016-05-04 at 14:02 -0400, Rob Heilman wrote: > query failed (SERVFAIL) for zulily- > com.mail.protection.outlook.com/IN/A
;; ANSWER SECTION: zulily-com.mail.protection.outlook.com. 10 IN A 207.46.163.170 zulily-com.mail.protection.outlook.com. 10 IN A 207.46.163.247 zulily-com.mail.protection.outlook.com. 10 IN A 207.46.163.215 ;; AUTHORITY SECTION: mail.protection.outlook.com. 1800 IN NS ns2-proddns.glbdns.o365filtering.com. mail.protection.outlook.com. 1800 IN NS ns1-proddns.glbdns.o365filtering.com. dig ns1-proddns.glbdns.o365filtering.com. a ;; ANSWER SECTION: ns1-proddns.glbdns.o365filtering.com. 30 IN A 207.46.163.176 ns1-proddns.glbdns.o365filtering.com. 30 IN A 65.55.169.42 ns1-proddns.glbdns.o365filtering.com. 30 IN A 207.46.163.143 ns1-proddns.glbdns.o365filtering.com. 30 IN A 207.46.100.42 dig mail.protection.outlook.com. ns @ns1-proddns.glbdns.o365filtering.com. +noedns ;; ANSWER SECTION: mail.protection.outlook.com. 10 IN NS ns1-proddns.glbdns.o365filtering.com. mail.protection.outlook.com. 10 IN NS ns2-proddns.glbdns.o365filtering.com. Note the short TTL on the A and NS records, combined with dns servers that don't understand edns. Is there something in bind 9.9.5 that would not like that combination? I presume that 9.9.5 would try edns first, and then backoff to noedns after receiving the FORMERR. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEAREKAAYFAlcqRVUACgkQL6j7milTFsEoSQCfXoslXPa/YgLrPQ3uHr3zCkwn lb8An1tuJleoYsDG8AS9FvHExWK1PSty =qfx2 -----END PGP SIGNATURE----- _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
