Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-05 Thread Sam Wilson
In article , Stephane Bortzmeyer wrote: > On Wed, May 04, 2016 at 02:02:24PM -0400, > Rob Heilman wrote > a message of 305 lines which said: > > > We run BIND 9.9.5-9 on Debian x86_64 to support a moderately sized > > email hosting system. System info listed at the end of this > > message.

Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread John Miller
Ok--I see what's up now! This has been one of the stranger DNS setups I've ever seen: different NS records pointing to overlapping sets of IP addresses, EDNS disabled, really short TTLs on both NS and A records. Even though you're not querying at the name listed in the NS records, it's usually th

Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread Rob Heilman
What is the typo? I ran it three times. The first time gave me the “couldn’t get address” error. The second I got the FORMERR, the third worked when I added +noedns. -rh > On May 4, 2016, at 3:57 PM, John Miller wrote: > > On Wed, May 4, 2016 at 3:23 PM, Rob Heilman wrote: >> Could it be

Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread John Miller
On Wed, May 4, 2016 at 3:57 PM, John Miller wrote: > On Wed, May 4, 2016 at 3:23 PM, Rob Heilman wrote: >> Could it be that the “adberr:2” logs entries are indicating that it >> periodically can’t find the name servers? >> >> -Rob Heilman >> >> >> >> # dig zulily-com.mail.protection.outlook.com.

Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread John Miller
On Wed, May 4, 2016 at 3:23 PM, Rob Heilman wrote: > Could it be that the “adberr:2” logs entries are indicating that it > periodically can’t find the name servers? > > -Rob Heilman > > > > # dig zulily-com.mail.protection.outlook.com. > @ns1-prodeodns.glbdns.o365filtering.com. > > dig: couldn't

Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread Rob Heilman
Could it be that the “adberr:2” logs entries are indicating that it periodically can’t find the name servers? -Rob Heilman # dig zulily-com.mail.protection.outlook.com. @ns1-prodeodns.glbdns.o365filtering.com. dig: couldn't get address for 'ns1-prodeodns.glbdns.o365filtering.com.': failure

Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread John Miller
> > 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

Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread Carl Byington
-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.c

RE: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread John W. Blue
I ran several digs using: dig @ns1-prodeodns.glbdns.o365filtering.com. A zulily-com.mail.protection.outlook.com. +short​ without error. As mentioned previously by Mark Andrews: > SERVFAIL usually means that the server is configured for the zone > but doesn't have a current copy. You gave

Re: Intermittent Issues Resolving Microsoft Hostnames

2016-05-04 Thread Stephane Bortzmeyer
On Wed, May 04, 2016 at 02:02:24PM -0400, Rob Heilman wrote a message of 305 lines which said: > We run BIND 9.9.5-9 on Debian x86_64 to support a moderately sized > email hosting system. System info listed at the end of this > message. We are seeing intermittent but frequent issues resolvin