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

Can i store A record of my second level domain directly in TLD zone file (com. for example)?

· 52CE 我爱测

Can be A record for third-level domain stored directly in TLD zone file, not delegating zone of subdomain with NS record? What about CNAME record for 2nd domain?

问题原文

原帖链接 · Alex78191 · CC BY-SA 3.0

Can be A record for third-level domain stored directly in TLD zone file, not delegating zone of subdomain with NS record? What about CNAME record for 2nd domain?

已采纳解答

原帖链接 · Andrew B · CC BY-SA 3.0

Yes, so long as no zone cut appears between the TLD and the record that is being defined. A zone cut occurs when a nameserver no longer considers itself authoritative for a subdomain, either through presence of a delegating NS record (i.e. non-apex) or an "overlapping" zone in the server configuration that is more specific.

An authoritative nameserver receiving a delegation is authoritative for all records inside of the delegated namespace. Until it gives that authority away, it owns the entire namespace. Once that authority has been delegated away, it cannot provide an authoritative definition for any records inside of the zone cut. It can offer temporary, non-authoritative suggestions for nameserver IPs in the form of glue records, but that is a separate topic.

Likewise, there is nothing to stop the operators of a TLD from defining catch-call wildcard records barring a contract forbidding them to do so. This is typical with ICANN partnerships, but there are a number of TLDs which have no such restrictions and choose to engage in those practices.


As a side note, based on the context of one of your comments, I suspect you're really asking whether you can get the TLD to define one of these records for you. The answer to that is no.

The first two levels of the DNS hierarchy are managed by domain name registries. There are systems in place that allow DNS registrars to insert and remove delegations from these zones in very controlled ways, but what you are looking to do falls outside of that process. It is an unreasonable administrative burden considering the "shared" nature of those domains.

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

资料来源与适用范围

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

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

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