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
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
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
On Mon, Oct 27, 2014 at 4:58 PM, Jeremy Chadwick via Outages < outages@outages.org> wrote:
dig mx navy.mil. +trace
Here you go: $ dig mx navy.mil. +trace ; <<>> DiG 9.8.3-P1 <<>> mx navy.mil. +trace ;; global options: +cmd . 765 IN NS e.root-servers.net. . 765 IN NS k.root-servers.net. . 765 IN NS h.root-servers.net. . 765 IN NS c.root-servers.net. . 765 IN NS d.root-servers.net. . 765 IN NS m.root-servers.net. . 765 IN NS f.root-servers.net. . 765 IN NS b.root-servers.net. . 765 IN NS a.root-servers.net. . 765 IN NS g.root-servers.net. . 765 IN NS i.root-servers.net. . 765 IN NS l.root-servers.net. . 765 IN NS j.root-servers.net. ;; Received 228 bytes from 8.8.8.8#53(8.8.8.8) in 2230 ms mil. 172800 IN NS con1.nipr.mil. mil. 172800 IN NS con2.nipr.mil. mil. 172800 IN NS eur1.nipr.mil. mil. 172800 IN NS eur2.nipr.mil. mil. 172800 IN NS pac1.nipr.mil. mil. 172800 IN NS pac2.nipr.mil. ;; Received 241 bytes from 192.203.230.10#53(192.203.230.10) in 1118 ms NAVY.mil. 21600 IN NS UPBD0FDA02.CSD.DISA.MIL. NAVY.mil. 21600 IN NS UPBD0FDA01.CSD.DISA.MIL. NAVY.mil. 21600 IN NS UPHB0FDA05.CSD.DISA.MIL. NAVY.mil. 21600 IN NS UPHB0FDA06.CSD.DISA.MIL. NAVY.mil. 21600 IN NS GUV10M01.MONT.DISA.MIL. NAVY.mil. 21600 IN NS UTINDO02.CSD.DISA.MIL. NAVY.mil. 21600 IN NS GUV10M02.MONT.DISA.MIL. ;; Received 414 bytes from 199.252.180.234#53(199.252.180.234) in 1338 ms navy.mil. 69510 IN MX 20 sec-jeemsg.eemsg.mail.MIl. navy.mil. 85048 IN MX 30 mx14.nmci.nAVy.MIl. navy.mil. 85048 IN MX 30 mx13.nmci.nAVy.MIl. navy.mil. 85048 IN MX 10 pri-jeemsg.eemsg.mail.MIl. navy.mil. 85048 IN MX 30 mx15.nmci.nAVy.MIl. ;; Received 167 bytes from 214.3.160.21#53(214.3.160.21) in 222 ms -- Alan K. Stebbens Software Architect Ecorithm, Inc. 805-886-8886
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
participants (4)
-
Alan Stebbens -
Blake Covarrubias -
Jeremy Chadwick -
Ray Van Dolson