为了使绑定正常工作，要遵循一些规则以正确配置它。

您需要选择一个域，为其添加区域记录，在该区域记录顶部的主机名中仅添加一个主机名条目，否则所有提及的内容仅是域。

在配置文件（例如domain.com）中，将所有域名以点号结尾是一个好习惯。

NS名称可以是域名。

A记录可以是机器的ip，而不是本地主机的ip，因为网络中的其他机器将拉该指定的ip。

一旦有了记录，就可以随意添加域名，也可以通配符，这就是我所做的。因此，现在所有以我选择的域结尾的域都映射到Web开发内容。

要使用DNS服务的计算机（即客户端）上的适配器IP属性中的DNS设置，您要将DNS设置为DNS服务器的局域网。

仅需要进行调整的是/etc/named.conf、/var/named/ld.pvt.zone以及我上面刚刚提到的IP属性。

这是配置文件，请尽情享受！

/etc/named.conf

// vim:set ts=4 sw=4 et:

acl "trusted" {
        192.168.1.0/24;
        127.0.0.0/8;
};

options {
    directory "/var/named";
    pid-file "/run/named/named.pid";
    listen-on { trusted; };
    listen-on-v6 { any; };
    allow-query { trusted; };
    allow-transfer { none; };
    allow-update { none; };
    forwarders {
        8.8.4.4;
        8.8.8.8;
    };
    query-source address * port 53;
    version none;
    hostname none;
    server-id none;
};

logging {
    channel default_file {
        file "/var/log/named/default.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel general_file {
        file "/var/log/named/general.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel database_file {
        file "/var/log/named/database.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel security_file {
        file "/var/log/named/security.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
channel config_file {
        file "/var/log/named/config.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel resolver_file {
        file "/var/log/named/resolver.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel xfer-in_file {
        file "/var/log/named/xfer-in.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel xfer-out_file {
        file "/var/log/named/xfer-out.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel notify_file {
        file "/var/log/named/notify.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel client_file {
        file "/var/log/named/client.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel unmatched_file {
        file "/var/log/named/unmatched.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel queries_file {
        file "/var/log/named/queries.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel network_file {
        file "/var/log/named/network.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel update_file {
        file "/var/log/named/update.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel dispatch_file {
        file "/var/log/named/dispatch.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel dnssec_file {
        file "/var/log/named/dnssec.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
channel lame-servers_file {
        file "/var/log/named/lame-servers.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    category default { default_file; };
    category general { general_file; };
    category database { database_file; };
    category security { security_file; };
    category config { config_file; };
    category resolver { resolver_file; };
    category xfer-in { xfer-in_file; };
    category xfer-out { xfer-out_file; };
    category notify { notify_file; };
    category client { client_file; };
    category unmatched { unmatched_file; };
    category queries { queries_file; };
    category network { network_file; };
    category update { update_file; };
    category dispatch { dispatch_file; };
    category dnssec { dnssec_file; };
    category lame-servers { lame-servers_file; };
};

zone "ld.pvt" IN {
    type master;
    file "ld.pvt.zone";
};

/var/named/ld.pvt.zone

$TTL 7200
@               1D IN SOA       ld.pvt. root.ld.pvt. (
                                        2007011622      ; Serial
                                        3H              ; Refresh
                                        15M             ; Retry
                                        1W              ; Expire - 1 week
                                        1D )            ; Minimum

                IN      NS      ld.pvt.
ld.pvt.         IN      A       192.168.1.10
*.ld.pvt.       IN      CNAME   ld.pvt.

您可能需要

# mkdir /var/db/nscd
# touch /etc/netgroup
# systemctl restart named

使用journalctl -xn查找错误。

一旦运行，您就应该能够ping通任何东西。ld.pvt，现在您的虚拟主机将知道该怎么做！

现在，在客户端计算机上，您需要调整DNS，并刷新dns解析器缓存。nscd -K然后，nscd或者对于Winbox，ipconfig /flushdns然后尝试在您的LAN上ping通到新的what.ld.pvt 。

要将客户端框放在地图上，您需要添加一个指向其ip的A记录，例如 automated-pooper-scooper.ld.pvt. IN A 192.168.1.44