domain mx records for google app
You enter these values at your domain host, not in your Google Admin console. Note that some hosts use different labels for the name and value fields, and many domain hosts also require a trailing period at the end of the server name.
| Name/Host/Alias | Time to Live (TTL*) | Record Type | Priority | Value/Answer/Destination |
|---|---|---|---|---|
| Blank or @ | 3600 | MX | 1 | ASPMX.L.GOOGLE.COM. |
| Blank or @ | 3600 | MX | 5 | ALT1.ASPMX.L.GOOGLE.COM. |
| Blank or @ | 3600 | MX | 5 | ALT2.ASPMX.L.GOOGLE.COM. |
| Blank or @ | 3600 | MX | 10 | ALT3.ASPMX.L.GOOGLE.COM. |
| Blank or @ | 3600 | MX | 10 | ALT4.ASPMX.L.GOOGLE.COM. |
Time To Live (TTL)
The TTL is a value in a DNS record that determines the number of seconds before subsequent changes to the record go into effect. Each of your domain's DNS records, such as an MX record, CNAME record, and so on, has a TTL value. A record's current TTL determines how long it will take any change you make now to go into effect. Changes to a record that has a TTL of 86400 seconds, for example, will take up to 24 hours to go into effect.
Note that changing a record's TTL affects how long it will take any subsequent change to happen. We recommend setting a TTL value of 3600, which tells servers across the Internet to check every hour for updates to the record. The shorter TTL will only take effect after the prior period expires. This means that next time you update the record, your change will take up to one hour to go into effect. To make subsequent changes happen even more quickly—for example, if you think you might want to quickly revert a change—you can set a shorter TTL, such as 300 seconds (5 minutes). Once the records are configured correctly, we recommend setting a TTL value of 86400, which tells servers across the Internet to check every 24 hours for updates to the record.
