Without divulging details, a Frontier contact shared that there was a glitch this afternoon affecting DNS records. Should be back to normal now, so I will be flushing *.frontier.com on our DNS servers.
Frank -----Original Message----- From: Aaron C. de Bruyn [mailto:[email protected]] Sent: Tuesday, September 26, 2017 4:42 PM To: Frank Bulk <[email protected]> Cc: [email protected] Subject: Re: [mailop] frontier.com lost MX record A query against their nameservers show multiple MX records being returned at the moment. Queries against 8.8.4.4 return MX records for me, but 8.8.8.8 returns: ;; QUESTION SECTION: ;frontier.com. IN MX ;; ANSWER SECTION: frontier.com. 79773 IN CNAME qathostedassist.frontier.com. ;; AUTHORITY SECTION: frontier.com. 692 IN SOA auth.roch.ny.frontiernet.net. hostmaster.frontiernet.net. 1709260004 10800 3600 604800 86400 Probably time to flush the caches... -A On Tue, Sep 26, 2017 at 2:20 PM, Frank Bulk <[email protected]> wrote: > Looks like frontier.com lost their MX and AAAA record sometime before 2:58 > pm today. We're seeing email build up . but before that, my AAAA checks for > http://www.frontier.com failed. > > Frank > > > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
