The examples I've received so far from folks match the same thing I'm seeing from two separate/unrelated connections (meaning I clearly get back MX records, and all those have A records (dig a fqdn)), so I'm hoping Blake and Ray can run the same and determine what's failing and where. :-) -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | On Mon, Oct 27, 2014 at 04:58:13PM -0700, Jeremy Chadwick via Outages wrote:
Is it possible for someone to provide output from something like "dig mx navy.mil. +trace" ?
-- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB |
On Mon, Oct 27, 2014 at 03:36:31PM -0700, Blake Covarrubias via Outages wrote:
Hello,
Our network is also unable resolve MX records for a number of .mil domains. Not sure of the root cause. What information do you have thus far?
-- Blake Covarrubias
On Oct 27, 2014, at 8:57 AM, Ray Van Dolson via Outages <outages@outages.org> wrote:
Seeing issues connecting to a number of .mil MX servers this morning (via port 25).
I'm able to reproduce the issue from external hosts so I don't *believe* it's just us, but still investigating.
Anyone else seeing this?
Ray _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages