-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Fri, 2016-11-11 at 13:09 -0500, Eric Tykwinski wrote: > Here's what I'm showing: > protection.outlook.com. 7200 IN NS > ns1-gtm.glbdns.o365filtering.com. > protection.outlook.com. 7200 IN NS > ns2-gtm.glbdns.o365filtering.com.
> Not bad at all. Honestly, the amount of traffic for each person is > probably minimal, > and I would think it would affect those DNS servers before ours. Well, taking one of my clients names, "dig mbmgmedia- com01b.mail.protection.outlook.com" shows the 10 second TTL on the A records, and an authority section showing the next zone cut at mail.protection.outlook.com. "dig mail.protection.outlook.com. ns @ns2-proddns.glbdns.o365filtering.com. +noedns" shows a 10 second TTL on the NS records as well. And the +noedns is required since Microsoft cannot be bothered to understand edns options. That may require another round trip to their dns servers if your resolver tries the initial NS query with edns options - which is very common. ns2-proddns.glbdns.o365filtering.com has 4 A records, with a 30 second TTL there. Microsoft loves really short TTLs. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEAREKAAYFAlgmQLcACgkQL6j7milTFsHVWwCfRwRKvxdvsYutTBPGCk8ikbzn NEgAnRYWYaBP4p30Db9AHYqRef3DSTLl =LMuo -----END PGP SIGNATURE----- _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
