正向和反向运行named-checkzone时,没有当前的所有者名称错误

我试图学习dns,并在数字海洋上绑定centos 7。 当我运行named-checkzone我得到相同的错误。 当我在白色空间周围改变时,我停止了这个错误,只是用0 SOA代替它,没有NS错误。

  sudo named-checkzone example.com /etc/named/zones/example.com.zone /etc/named/zones/example.com.zone:1: no current owner name /etc/named/zones/example.com.zone:2: no current owner name /etc/named/zones/example.com.zone:3: no current owner name /etc/named/zones/example.com.zone:16: no current owner name /etc/named/zones/example.com.zone:17: no current owner name /etc/named/zones/example.com.zone:18: no current owner name /etc/named/zones/example.com.zone:19: no current owner name /etc/named/zones/example.com.zone:24: no current owner name /etc/named/zones/example.com.zone:25: no current owner name /etc/named/zones/example.com.zone:26: no current owner name /etc/named/zones/example.com.zone:27: no current owner name /etc/named/zones/example.com.zone:28: no current owner name /etc/named/zones/example.com.zone:29: no current owner name $ORIGIN example.com. $TTL 14400 @ IN SOA ns1.example.com. hostmaster.example.com. ( 2014071301 ; serial. date. today + increment 3600 ; refresh. seconds. frequency slave refreshes from master. 600 ; retry. seconds. frequency slave retries master after failure. 604800 ; expire. seconds. slave stops responding as authoritative. 86400 ; ttl. seconds. Maximum caching time by resolver. ) ;------------------------------------------------------------------------------ ; Special Records ; ; Note: SPF Records are limited to 10 DNS lookups recursively. ; IN NS ns1.example.com. IN NS ns2.example.com. IN MX 10 mail.example.com. IN TXT "v=spf1 -ALL" ;------------------------------------------------------------------------------ ; Main Records ; @ IN A 192.0.2.1 * IN A 192.0.2.1 ns1 IN A 192.0.2.2 ns2 IN A 192.0.2.3 mail IN A 192.0.2.1 www IN A 192.0.2.1 

与之相反的事情叫做db.192.0

 $ORIGIN 2.0.192.in-addr.arpa. $TTL 86400 @ IN SOA ns1.example.com. hostmaster.example.com. ( 3 ; serial 21600 ; refresh after 6 hours 3600 ; retry after 1 hour 604800 ; expire after 1 week 86400 ) ; minimum TTL of 1 day @ IN NS ns1.example.com. 2 IN PTR ns1.example.com. 3 IN PTR ns2.example.com. 

正如Julie Pelletier已经评论的那样,删除区域logging中的前导空格,因为它们在“绑定”区域文件中具有特殊含义。

通过开始一个带有空格的行(该行不是主机名,区域名称或区域原点的简写),该行成为其上面logging的延续。

 $ORIGIN neilanuskiewicz.com. $TTL 14400 @ IN SOA ns1.neilanuskiewicz.com. ... 

这使得与SOA相关的logging是上面不存在的logging的继续(variables不计算在这方面),因此你的失败; 上面有资源logging,没有所有者申请该延续logging。

 $ORIGIN neilanuskiewicz.com. $TTL 14400 @ IN SOA ns1.neilanuskiewicz.com. ... 

您可以故意使用以空格开头的行,但是:

 @ IN A 192.0.2.1 ; IPv4 address for the bare domain using the @ short hand neilanuskiewicz.com. IN AAAA 2001:db8:10::1 ; IPv6 address for the bare domain www IN A 192.0.2.1 IN AAAA 2001:db8:10::1 ; IPv6 address for www using DNS shorthand by starting this line with a space