- 论坛徽章:
- 0
|
这是 ‘DNS and BIND’一书的部分内容,希望有帮助
14.5.2. Name Server Reports "No NS Record for SOA MNAME" ( name server 指示缺少 SOA 记录中缺少 NS )
You'll see this error only on BIND 8.1 servers:
May 8 03:44:38 terminator named[11680]: no NS RR for SOA MNAME "movie.edu" in zone "movie.edu"
The 8.1 server was a real stickler ( 坚持己见的人 ) about the first field in the SOA record. Remember that one? In Chapter 4, "Setting Up BIND", we said that it was, by convention, the domain name of the primary master name server for the zone. BIND 8.1 assumes it is and checks for a corresponding NS record pointing the zone's domain name to the server in that field. If there's no such NS record, BIND emits (发出)that error message. It will also prevent NOTIFY messages from working correctly. The solution is either to change your MNAME field to the domain name of a name server listed in an NS record or to upgrade to a newer version of BIND 8. Upgrading is the better option since BIND 8.1 is so old. The check was removed at BIND 8.1.1. |
|