; <<>> DiG 9.10.6 <<>> mx vaspace.org @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56818
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;vaspace.org. IN MX
;; ANSWER SECTION:
vaspace.org. 1342 IN MX 20 ms2.vaspace.org.
vaspace.org. 1342 IN MX 10 ms1.vaspace.org.
;; Query time: 7 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Aug 22 10:44:53 EDT 2019
;; MSG SIZE rcvd: 80
Dig results for 208.67.222.222 (Open DNS). The entry marsspaceport.mail.protection.office365.us is the new, correct entry.
; <<>> DiG 9.10.6 <<>> mx vaspace.org @208.67.222.222
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50228
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;vaspace.org. IN MX
;; ANSWER SECTION:
vaspace.org. 3600 IN MX 10 marsspaceport.mail.protection.office365.us.
vaspace.org. 3600 IN MX 20 ms2.vaspace.org.
;; Query time: 113 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Thu Aug 22 10:49:20 EDT 2019
Flushing the Google DNS cache for the MX record has not resolved the problem. Because Google DNS has not yet picked up the record changes we are still having to route some e-mail through our old, on-premises mail server, and our sites that use Google DNS on their networks are having difficulty logging into services like Skype For Business.
Is there an additional step I need to complete at 1&1 IONOS, or is this just a situation where I need to wait it out?