大网数据广告活动
服务器运维问答

Is it bad practice to put IP addresses into SPF records instead of lookups if you are also in control of the lookedup record?

· 52CE 我爱测

If someone owns a domain that needs to be looked up in an SPF record, is it bad practice for them to put the IP address of that domain instead of the domain itself in order to cut down on lookups? E.g. to stop going over the 10 l…

问题原文

原帖链接 · d786b09987n · CC BY-SA 4.0

If someone owns a domain that needs to be looked up in an SPF record, is it bad practice for them to put the IP address of that domain instead of the domain itself in order to cut down on lookups? E.g. to stop going over the 10 lookups limit?

I understand that this would result in needing to change two IPs in the DNS records if the IP needed to be changed instead of one change. Is there any other reason it shouldn't be done?

已采纳解答

原帖链接 · Esa Jokinen · CC BY-SA 4.0

As mail server related DNS records are only changed occasionally but queried all the time, it is better optimize the latter. Administrator's Considerations in RFC 7208, 10.1.2 summarizes this well:

There might be administrative considerations: using a over ip4 or ip6 allows hosts to be renumbered easily at the cost of a DNS query per receiver. Using mx over a allows the set of mail hosts to be changed easily. Unless such changes are common, it is better to use the less resource-intensive mechanisms like ip4 and ip6 over a or a over mx.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2020-12-24)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。