r00k
2[H]4U
- Joined
- Aug 24, 2004
- Messages
- 2,696
I have a client who recently transitioned to G-Suite (Google Apps for Non-Profits, specifically). Their registrar is bluehost.com
Since then, their email is only working spottily from what they can tell. I have many clients who have G-Suite, and so i checked their configuration against other clients. The configuration for this domain is generally correct. They have Google's 5 MX records. However, when i run a DNS report on them at dnsstuff.com, i get this (less relevant information omitted)
ns1.bluehost.com. | 162.88.60.37
ns2.bluehost.com. | 162.88.61.37
162.88.60.37 has aspmx.l.google.com. | 74.220.199.6 listed.
162.88.60.37 has alt1.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.60.37 has alt2.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.60.37 has alt3.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.60.37 has alt4.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has alt1.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has alt2.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has alt3.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has alt4.aspmx.l.google.com. | 74.220.199.6 listed.
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
Bluehost's nameservers are spitting out the same bluehost park page for all google's mail exchange servers.
Another client using G-Suite gives the following:
ns03.domaincontrol.com. | 216.69.185.2
ns04.domaincontrol.com. | 208.109.255.2
216.69.185.2 has ASPMX.L.GOOGLE.com. | 64.233.168.26 listed.
216.69.185.2 has ALT1.ASPMX.L.GOOGLE.com. | 64.233.185.26 listed.
216.69.185.2 has ALT2.ASPMX.L.GOOGLE.com. | 173.194.68.26 listed.
216.69.185.2 has ALT3.ASPMX.L.GOOGLE.com. | 173.194.210.26 listed.
216.69.185.2 has ALT4.ASPMX.L.GOOGLE.com. | 64.233.190.27 listed.
208.109.255.2 has ASPMX.L.GOOGLE.com. | 64.233.168.26 listed.
208.109.255.2 has ALT1.ASPMX.L.GOOGLE.com. | 64.233.185.26 listed.
208.109.255.2 has ALT2.ASPMX.L.GOOGLE.com. | 173.194.68.26 listed.
208.109.255.2 has ALT3.ASPMX.L.GOOGLE.com. | 173.194.210.26 listed.
208.109.255.2 has ALT4.ASPMX.L.GOOGLE.com. | 64.233.190.27 listed.
These all give the expected result, which all other DNS servers resolve no sweat.
When i called bluehost, they said there was no problem, and that everything was resolving correctly, or that Google is the one who is responsible for the resolved ip's. i was hitting my head against a wall with them.
Setting my own workstation dns entry to just the bluehost nameserver, an nslookup confirms they resolve those mx records to the park page.
Am I wrong or missing something? What's the next step?
Since then, their email is only working spottily from what they can tell. I have many clients who have G-Suite, and so i checked their configuration against other clients. The configuration for this domain is generally correct. They have Google's 5 MX records. However, when i run a DNS report on them at dnsstuff.com, i get this (less relevant information omitted)
ns1.bluehost.com. | 162.88.60.37
ns2.bluehost.com. | 162.88.61.37
162.88.60.37 has aspmx.l.google.com. | 74.220.199.6 listed.
162.88.60.37 has alt1.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.60.37 has alt2.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.60.37 has alt3.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.60.37 has alt4.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has alt1.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has alt2.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has alt3.aspmx.l.google.com. | 74.220.199.6 listed.
162.88.61.37 has alt4.aspmx.l.google.com. | 74.220.199.6 listed.
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
74.220.199.6 | failed message send with: failed cx open with: failed socket connect with: Operation now in progress
Bluehost's nameservers are spitting out the same bluehost park page for all google's mail exchange servers.
Another client using G-Suite gives the following:
ns03.domaincontrol.com. | 216.69.185.2
ns04.domaincontrol.com. | 208.109.255.2
216.69.185.2 has ASPMX.L.GOOGLE.com. | 64.233.168.26 listed.
216.69.185.2 has ALT1.ASPMX.L.GOOGLE.com. | 64.233.185.26 listed.
216.69.185.2 has ALT2.ASPMX.L.GOOGLE.com. | 173.194.68.26 listed.
216.69.185.2 has ALT3.ASPMX.L.GOOGLE.com. | 173.194.210.26 listed.
216.69.185.2 has ALT4.ASPMX.L.GOOGLE.com. | 64.233.190.27 listed.
208.109.255.2 has ASPMX.L.GOOGLE.com. | 64.233.168.26 listed.
208.109.255.2 has ALT1.ASPMX.L.GOOGLE.com. | 64.233.185.26 listed.
208.109.255.2 has ALT2.ASPMX.L.GOOGLE.com. | 173.194.68.26 listed.
208.109.255.2 has ALT3.ASPMX.L.GOOGLE.com. | 173.194.210.26 listed.
208.109.255.2 has ALT4.ASPMX.L.GOOGLE.com. | 64.233.190.27 listed.
These all give the expected result, which all other DNS servers resolve no sweat.
When i called bluehost, they said there was no problem, and that everything was resolving correctly, or that Google is the one who is responsible for the resolved ip's. i was hitting my head against a wall with them.
Setting my own workstation dns entry to just the bluehost nameserver, an nslookup confirms they resolve those mx records to the park page.
Am I wrong or missing something? What's the next step?