Google DNS errors

The messages indicate that one of your MX records is formatted incorrectly.  If you can take a screenshot of them, it will be helpful to determine whether this is actually the case.

Thanks for your response please find the attached format for mx and SPF recordm which i have set.

All the MX records appear to have the priority, one space, and then the mail exchanger in the name/IP column, where the only thing should be the name/IP of the mail exchanger.  The MX priority should be somewhere else.  This could  cause the problem described.

This is how i get the option to set the MX record ,there is no option to separate the priority ans MX and if i just put the MX it does not accept.


here is the format it needs

Thank you.  I've double-checked this on a linux server, and the MX records appear to be correct.  Perhaps another expert will have some insight.

drklahn@www:~$ dig -t mx lamprell.com

; <<>> DiG 9.9.5-9+deb8u6-Debian <<>> -t mx lamprell.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9237
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1024
;; QUESTION SECTION:
;lamprell.com.                  IN      MX

;; ANSWER SECTION:
lamprell.com.           12137   IN      MX      50 smtp3.lamprell.com.
lamprell.com.           12137   IN      MX      100 smtp4.lamprell.com.
lamprell.com.           12137   IN      MX      10 smtp2.lamprell.com.
lamprell.com.           12137   IN      MX      5 smtp1.lamprell.com.

;; Query time: 35 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Apr 1 12:44:45 UTC 2016
;; MSG SIZE  rcvd: 129

Select allOpen in new window

Yes sometimes it works because of the other name server which we have apart from google's, if you do the nslookup for MX specifically on google name server it won't work ,we have name server of directi also configured,may be when it hits on directi name server it works,we were adding google name server as additional backup name server,so sometimes when the query goes to google name server it does not work ,but if it goes to directi name server it works,

so it worked for you because it might have reached to the directi name server.
can you do nslookup specifically on google name server and check.

resolved it myself