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

What is the difference between NS record and SOA record in DNS entry?

· 52CE 我爱测

I am trying to understand the difference between NS record and SOA record. As NS record is supposed to store a primary authoritative nameserver and secondary authoritative nameserver as a backup of data. And according to RFC of D…

问题原文

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

I am trying to understand the difference between NS record and SOA record. As NS record is supposed to store a primary authoritative nameserver and secondary authoritative nameserver as a backup of data. And according to RFC of DNS, SOA stores "the name server that was the original or primary source of data for this zone" in MNAME. Why does SOA record sometimes different from NS record? Example:

htw-berlin.de.          460     IN      SOA     infoblox1.htw-berlin.de. net-rz.htw-berlin.de. 2009142669 10800 3600 2419200 900
htw-berlin.de.          20965   IN      NS      infobloxv.htw-berlin.de.
htw-berlin.de.          20965   IN      NS      dns-2.dfn.de.

In this case: infoblox1.htw-berlin.de. != infobloxv.htw-berlin.de.

社区高分解答

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

The Wikipedia SOA article hints at the reason, but to make it explicit: the MNAME designates the primary master name server for a zone.

That can be and often is one of the public authoritative name servers, that are also found in the NS records and/or the WHOIS record, but it can also name a different DNS server. Such a configuration is often called a hidden master.

Hidden Master

A hidden master is a name server that is not advertised and does not appear in any NS records. In other words, it is not designated publicly on the Internet as a name server for your domain and does not answer any queries from the internet. The hidden master’s purpose is to provide zone transfers to a set of "secondary" name servers that are known publicly as authoritative for your domain and answer queries.

It is considered to have some operational and security benefits: Often the "hidden master" is protected by a firewall and access is restricted, or the hidden master is part of your internal network. And that is where the domain administrator will manage the DNS records. Reloads and restarts of the hidden master do not impact resolution of your domain. And your DNSEC private keys will be better protected.

Other say consider such a setup something confusing and contrary to Internet standards.

https://www.inetdaemon.com/tutorials/internet/dns/configuration/hidden_master.shtml

(In this case I could assume that an organisation uses an Infoblox appliance/solution for their internal DNS and rather than using additional appliances directly to manage their public DNS, they manage their internet domain and public DNS records with the same internal appliance.
Or they have an even more complex solution like this one: https://docs.infoblox.com/space/BloxOneDDI/290685979/BloxOne+DDI+as+the+Hidden+Primary+Master )

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

资料来源与适用范围

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

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

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