**这是本文档旧的修订版!**
第4章 GWS邮件管理
练习1
略
DNS介绍
练习2
参考链接https://support.google.com/a/answer/140034
2.TTL默认是3600,但正常使用Gmail后可以改为86400,这样更新频率会改为每天1次
3.如果是要把现行的邮箱系统转移到GWS上,可以保留现在的MX记录,但调低优先级(比如将优先级改为10+),当所有邮箱都经由Google后,再删除原MX记录,这样保证不会有邮件丢失
练习3
检查MX
工具URL为https://toolbox.googleapps.com/apps/checkmx/
点击报警会给出解决方法
测试1
You need to make a change to your MX records and you want the change to be implemented as soon as possible. What approach can you take?
- Change your MX records in the admin console and reduce the Time to Live (TTL) value to one hour. Once the change has been implemented revert the TTL value to 24 hours
- Make the change in your DNS console and reduce the Time to Live (TTL) value to 1 hour. Once the change has been implemented revert the TTL value to 24 hours
- Change your MX records in the admin console and reduce the Time to Live (TTL) value to one hour
- Make the change in your DNS console and reduce the Time to Live (TTL) value to 1 hour
Which type of DNS record determines where mail destined for your domain is routed?
- MX Record
- TXT Record
- NS Record
- CNAME Record
In general, from where would you manage your domain's DNS records?
- All of the options here
- In your local DNS files
- In your domain registrar console
- In the Google Workspace admin console
What are common uses for a DNS TXT record when using Google Workspace? (Choose 2)
- Customise a Google service address
- Control inbound mail to your domain
- Domain verification
- Email security records
邮件安全
3招,SPF,DKIM和DMARC
SPF: verify the domain you own
DKIM: prevent email spoofing on outbound message by adding an encrypted header
DMARC: tell email servers how to handle messages that fail SPF/DKIM checks
练习1
SPF,通过添加TXT记录到DNS中
Xserver中已经有一条记录了,现在在后面追加
include:_spf.google.com ~all
记录生效需要24小时左右
参考链接:https://support.google.com/a/answer/33786#zippy=%2Cspf-%E8%AE%B0%E5%BD%95%E7%A4%BA%E4%BE%8B
练习2
生成后长这个样子
生成的记录在Xserver的DNS DKIM记录中已经有了,一模一样。
参考链接:
https://support.google.com/a/answer/174124
练习3
测试2
What is the main purpose of a Sender Policy Framework (SPF) record?
- It specifies which servers/domains can send messages on your behalf
- It can be used to verify that message content is authentic and has not changed
- It defines the action to take on suspicious incoming messages
You have been asked to implement DomainKeys Identified Mail (DKIM) for your organization. How would you do this?
- Enable DKIM from Apps > Google Workspace > Gmail > Authenticate email
- Enable DKIM directly in your DNS records
- Generate a key from your DNS records and add it to the Google Workspace admin console. Then Enable DKIM from Apps > Google Workspace > Gmail > Authenticate email
- Generate a DKIM record from Apps > Google Workspace > Gmail > Authenticate email. Add the record to your DNS records and then start authentication from the admin console
What policy defines what to do if an incoming message is not authenticated?
- SPF
- DKIM
- All of the options here
- DMARC
DKIM adds an encrypted signature to the header of all outgoing messages. What happens if you don't turn on email signing with your own domain DKIM key?
- Gmail signs all outgoing messages with a temporary key generated for your domain
- Gmail signs all outgoing messages with this default DKIM domain key d=.gappssmtp.com*
- Gmail signs all outgoing messages with a key generated using the From address in the message
- Messages are sent as normal with no additional headers