lb-99's questions

我正在使用 Linux DDNS 设置设置 Windows AD 服务器。Linux DDNS 按预期运行得非常好。但是，当我尝试将 AD 角色添加到 Windows Enterprise 2019 服务器时，该角色会按预期安装，但不会使用该区域的 SRV 记录更新主 DNS 数据库。

在 Wireshark 中，在 Windows AD 设置期间和之后，我可以看到对 SRV 记录的主 DNS 查询，主 DNS 以“没有这样的名称”响应。

我已允许在主 DNS 上的 named.conf.local 中更新/查询 AD 服务器，并且 AD 服务器设置为使用主 DNS 服务器的地址作为其 DNS 服务器。

我现在已经尝试了两次全新安装 AD 服务器，每次都遇到相同的问题。我不知道可能是什么问题 - 一个潜在的解决方案是否只是手动将所有必要的 SRV 记录添加到数据库文件中？

我在下面添加了配置（我知道允许地址授予太多权限，named.conf.local但我只是在试验并试图让它工作，因为这是我第一次设置它）。

/etc/bind/named.conf.local

zone "lims.co.uk" {
        type master;
        file "/var/lib/bind/db.lims.co.uk";
        notify yes;
        allow-update {
                192.168.80.3;
                192.168.80.7;
                192.168.80.8;
                192.168.80.9;
                localnets;
        };
        allow-query {
                127.0.0.1;
                192.168.80.3;
                192.168.80.5;
                192.168.80.6;
                192.168.80.7;
                192.168.80.8;
                192.168.80.9;
                localnets;
        };
        allow-transfer {
                192.168.80.3;
                192.168.80.5;
                192.168.80.6;
                192.168.80.7;
                192.168.80.8;
                192.168.80.9;
        };
};

zone "80.168.192.in-addr.arpa" {
        type master;
        file "/var/lib/bind/db.80.168.192.in-addr.arpa";
        notify yes;
        allow-update {
                192.168.80.3;
                192.168.80.7;
                192.168.80.8;
                192.168.80.9;
                localnets;
        };
        allow-query {
                127.0.0.1;
                192.168.80.3;
                192.168.80.5;
                192.168.80.6;
                192.168.80.7;
                192.168.80.8;
                192.168.80.9;
                localnets;
        };
        allow-transfer {
                192.168.80.3;
                192.168.80.5;
                192.168.80.6;
                192.168.80.7;
                192.168.80.8;
                192.168.80.9;
        };
};

/var/lib/bind/db.lims.co.uk

$ORIGIN .
$TTL 604800     ; 1 week
lims.co.uk              IN SOA  lims.co.uk. admin\@lims.co.uk. (
                                2021032201 ; serial
                                604800     ; refresh (1 week)
                                86400      ; retry (1 day)
                                2419200    ; expire (4 weeks)
                                604800     ; minimum (1 week)
                                )
                        NS      ns1.lims.co.uk.
                        NS      ns2.lims.co.uk.
                        A       192.168.80.7
                        A       192.168.80.8
                        A       192.168.80.9
$ORIGIN lims.co.uk.
AD1                     A       192.168.80.7
BDC1                    A       192.168.80.8
BDC2                    A       192.168.80.9
ns1                     A       192.168.80.5
ns2                     A       192.168.80.6
dhcp                    A       192.168.80.3

db.80.168.192.in-addr.arpa

$ORIGIN .
$TTL 604800     ; 1 week
80.168.192.in-addr.arpa IN SOA  80.168.192.in-addr.arpa. admin\@lims.co.uk. (
                                2021032201 ; serial
                                604800     ; refresh (1 week)
                                86400      ; retry (1 day)
                                2419200    ; expire (4 weeks)
                                604800     ; minimum (1 week)
                                )
                        NS      ns1.lims.co.uk.
                        NS      ns2.lims.co.uk.
$ORIGIN 80.168.192.in-addr.arpa.
3                       PTR     dhcp.lims.co.uk.
5                       PTR     ns1.lims.co.uk.
6                       PTR     ns2.lims.co.uk.
7                       PTR     AD1.lims.co.uk.
8                       PTR     BDC1.lims.co.uk.
9                       PTR     BDC2.lims.co.uk.
$TTL 300        ; 5 minutes
99                      PTR     DESKTOP-9MFAP8Q.lims.co.uk.

192.168.80.3 DHCP

192.168.80.4 主 DNS

192.168.80.5 辅助 DNS

192.168.80.6 辅助 DNS

192.168.80.7 Windows 广告

192.168.80.8 备份域控制器（尚未配置）

192.168.80.9 备份域控制器（尚未配置）

更新：

我在我的 AD 服务器上收到以下错误。

DFS 复制服务未能联系域控制器以访问配置信息。复制停止。该服务将在下一个配置轮询周期内再次尝试，该周期将在 60 分钟后发生。此事件可能由 TCP/IP 连接、防火墙、Active Directory 域服务或 DNS 问题引起。

附加信息：错误：160（一个或多个参数不正确。）

此计算机现在托管指定的目录实例，但 Active Directory Web 服务无法为其提供服务。Active Directory Web 服务将定期重试此操作。

目录实例：NTDS 目录实例 LDAP 端口：389 目录实例 SSL 端口：636

我在主 dns 服务器上使用 bind9，两个辅助 dns 服务器处于主/从关系。我正在尝试实现 DDNS，但在添加转发映射时似乎遇到了问题，我收到了错误

无法将 DESKTOP-9MFAP8Q.student.co.uk 的正向映射添加到 192.168.80.51：SERVFAIL

我最初得到一个 REFUSED 错误，直到我将 DHCP 服务器的地址添加到主 dns 上的allow-query和allow-transfer选项中。named.conf.local我不确定这是否需要，这只是我为了让它工作而尝试的东西。

我尝试使用更改区域文件的权限

sudo chown 绑定：绑定 /etc/bind/*.db

sudo chmod 664 /etc/bind/*.db

但这对结果没有任何改变。

我将在下面发布配置文件，不胜感激。

路由器 - 192.168.80.2

DHCP - 192.168.80.3

主 DNS - 192.168.80.4

辅助 DNS - 192.168.80.5、192.168.80.6

-------------------------主 DNS------------------------ --

命名.conf.local

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

key "rndc-key" {
        algorithm hmac-sha256;
        secret "ppxPx1DgcHkDWDgngLNlgKAETBPEEL9+k8kn9zI/iKRHMdP/8G+U4FRasufyNGOKuUGgTfNqHnOyFxs3zuWlMA==";
};

zone "student.co.uk" {
        type master;
        file "/etc/bind/db.student.co.uk";
        notify no;
        allow-query {
                127.0.0.1;
                192.168.80.5;
                192.168.80.6;
                192.168.80.3;
        };
        allow-transfer {
                192.168.80.5;
                192.168.80.6;
                192.168.80.3;
        };
        allow-update {
                { key rndc-key; };
        };
};

zone "80.168.192.in-addr.arpa" {
        type master;
        file "/etc/bind/db.80.168.192.in-addr.arpa";
        notify no;
        allow-query {
                127.0.0.1;
                192.168.80.5;
                192.168.80.6;
        };
        allow-transfer {
                192.168.80.5;
                192.168.80.6;
        };
        allow-update {
                { key rndc-key; };
        };
};

命名.conf.options

options {
        directory "/var/cache/bind";

        // If there is a firewall between you and nameservers you want
        // to talk to, you may need to fix the firewall to allow multiple
        // ports to talk.  See http://www.kb.cert.org/vuls/id/800113

        // If your ISP provided one or more IP addresses for stable
        // nameservers, you probably want to use them as forwarders.
        // Uncomment the following block, and insert the addresses replacing
        // the all-0's placeholder.

         forwarders {
                8.8.8.8;
                8.8.4.4;
         };
         allow-query {
                192.168.80.5;
                192.168.80.6;
                127.0.0.1;
         };
         allow-transfer {
                192.168.80.5;
                192.168.80.6;
                127.0.0.1;
         };

        //========================================================================
        // If BIND logs error messages about the root key being expired,
        // you will need to update your keys.  See https://www.isc.org/bind-keys
        //========================================================================
        dnssec-validation auto;

        listen-on-v6 { any; };
};

db.80.168.192.in-addr.arpa

; BIND reverse data file for local loopback interface
;
$TTL    604800
@       IN      SOA     localhost. root.localhost. (
                     2021020902         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@       IN      NS      ns1.student.co.uk.
@       IN      NS      ns2.student.co.uk.
150     IN      PTR     www.student.co.uk.
151     IN      PTR     www.student.co.uk.

db.student.co.uk

; BIND data file for local loopback interface
;
$TTL    604800
@       IN      SOA     localhost. root.localhost. (
                     2021021902         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@       IN      NS      ns1.student.co.uk.
@       IN      NS      ns2.student.co.uk.
ns1     IN      A       192.168.80.5
ns2     IN      A       192.168.80.6
www     IN      A       192.168.80.150
www     IN      A       192.168.80.151

-------------------------DHCP------------------------ -

dhcpd.conf

# option definitions common to all supported networks...
option domain-name "student.co.uk";
option domain-name-servers 192.168.80.5, 192.168.80.6;

default-lease-time 600;
max-lease-time 7200;

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-updates on;
ddns-update-style standard;
update-static-leases on;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

allow unknown-clients;
use-host-decl-names on;

key rndc-key {
        algorithm hmac-sha256;
        secret ppxPx1DgcHkDWDgngLNlgKAETBPEEL9+k8kn9zI/iKRHMdP/8G+U4FRasufyNGOKuUGgTfNqHnOyFxs3zuWlMA==;
};

zone student.co.uk. {
    primary 192.168.80.4;
    key rndc-key;
}

zone 80.168.192.in-addr.arpa. {
    primary 192.168.80.4;
    key rndc-key;
}

subnet 192.168.80.0 netmask 255.255.255.0 {
  range 192.168.80.50 192.168.80.100;
  option domain-name-servers 192.168.80.5, 192.168.80.6;
  option domain-name "student.co.uk";
  ddns-domainname "student.co.uk.";
   ddns-rev-domainname "in-addr.arpa.";
  option subnet-mask 255.255.255.0;
  option routers 192.168.80.2;
  option broadcast-address 192.168.80.255;
  default-lease-time 600;
  max-lease-time 7200;

  host DOMAIN1 {
    hardware ethernet 00:0c:29:20:87:b0;
    fixed-address 192.168.80.99;
    ddns-hostname "test";
  }
}