Re: [mailop] Office365 question...

2016-11-11 Thread Carl Byington
-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. 7200IN NS > ns1-gtm.glbdns.o365filtering.com. > protection.outlook.com. 7200IN NS > ns2-gtm.glbdns.o365filtering.com. > N

Re: [mailop] Office365 question...

2016-11-11 Thread Eric Tykwinski
- From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Tim Bray Sent: Friday, November 11, 2016 12:42 PM To: mailop@mailop.org Subject: Re: [mailop] Office365 question... On 11/11/16 03:15, Bill Cole wrote: > > I think it's a perfectly reasonable TTL for a mail system tha

Re: [mailop] Office365 question...

2016-11-11 Thread Tim Bray
On 11/11/16 03:15, Bill Cole wrote: > > I think it's a perfectly reasonable TTL for a mail system that uses > round-robin DNS for loadbalancing and high availability. Arbitrarily > forcing it higher on the client end could have unintended negative > consequences. (quick reply) The other questi

Re: [mailop] Office365 question...

2016-11-10 Thread Bill Cole
On 10 Nov 2016, at 21:27, Eric Tykwinski wrote: We had some DNS issues, so I was looking through logs and noticed that domain-com.mail.protection.outlook.com was set to a 10 second refresh on the TTL. IMHO, this seems just a bit extreme. Give

[mailop] Office365 question...

2016-11-10 Thread Eric Tykwinski
We had some DNS issues, so I was looking through logs and noticed that domain-com.mail.protection.outlook.com was set to a 10 second refresh on the TTL. IMHO, this seems just a bit extreme. Given I know end users can set the min TTL to be what