• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Change MX to google apps account

Started by dasv, September 13, 2011, 11:02:43 PM

Previous topic - Next topic

dasv

Hello,
I have added MX records and a A record into my new hurricane account. The MX records point to the servers of Google for my google apps email accounts. Now I have done this change since more than 24 hours that I done the change and I do not receive any email. Is there something wrong in my MX or DNS settings ? thanks

My Hurricane account management page:
Name,Type,TTL,Priority,Data
mydomain.li,SOA,86400,-,ns1.he.net. hostmaster.he.net. 2011091325 10800 1800 604800 86400
mydomain.li,NS,86400,-,ns1.he.net
mydomain.li,NS,86400,-,ns2.he.net
mydomain.li,NS,86400,-,ns3.he.net
mydomain.li,NS,86400,-,ns5.he.net
mydomain.li,NS,86400,-,ns4.he.net
mydomain.li,A,3600,66.40.52.72
mydomain.li,3600,10,ASPMX3.GOOGLEMAIL.COM
mydomain.li,MX,3600,1,ASPMX.L.GOOGLE.COM
mydomain.li,MX,3600,5,ALT1.ASPMX.L.GOOGLE.COM
mydomain.li,MX,3600,5,ALT2.ASPMX.L.GOOGLE.COM
mydomain.li,MX,3600,10,ASPMX2.GOOGLEMAIL.COM

When running the DNStrouble.com checking it gives a reasonable answer:
ALT1.ASPMX.L.GOOGLE.COM   5   220 mx.google.com ESMTP d1si983321fak.66
ALT2.ASPMX.L.GOOGLE.COM   5   220 mx.google.com ESMTP j3si2514166bke.24
ASPMX2.GOOGLEMAIL.COM   10   220 mx.google.com ESMTP t14si2514966bkd.17
ASPMX.L.GOOGLE.COM   1   220 mx.google.com ESMTP h16si3681545wee.60
ASPMX3.GOOGLEMAIL.COM   10   220 mx.google.com ESMTP t15si4403343wfe.77

jrocha

Your account does not have any domains configured, and you obfuscated the actual domain name. Without either of those bits of information, I can't actually make sure your configuration is correct. (Though I do not see anything amiss from what you have posted.)

openlab


Pulpish

I'm having trouble too..

This is from my domain host:


and This is on he:


and google apps is telling me i haven't configured properly :/

kcochran

That's because you have the CNAME from your domain to www.yourdomain.  The CNAME applies before anything else on that resource.  As such, those MXs you specified are never checked, because the CNAME hits first.  You should have nothing else on a record that you're CNAMEing from.

Pulpish

Quote from: kcochran on September 25, 2011, 03:55:14 AM
That's because you have the CNAME from your domain to www.yourdomain.  The CNAME applies before anything else on that resource.  As such, those MXs you specified are never checked, because the CNAME hits first.  You should have nothing else on a record that you're CNAMEing from.
Thanks for the reply, this has been biting at me for a while now..

snarked

A zone with a CNAME having the LHS of that record ("the alias") being the same as the zone name should not even load into a DNS server.  Such is an invalid construct.

A CNAME record cannot coexist with any other record except for DNSSEC records which prove its existence.