我有一个多networking服务器“dhcp1”,networking接口“192.168.10.151”(eth0)和“192.168.0.151”(eth1)。 机器正在尝试使用具有networking接口“192.168.10.131”(eth0)和“192.168.0.131”(eth1)的名称服务器“ns1”的DDNS。 希望这些是我的dhcpd.conf的相关部分:
ddns-update-style interim; key DHCP_UPDATER { algorithm HMAC-MD5; secret "A6...=="; }; # The 'private' network. subnet 192.168.10.0 netmask 255.255.255.0 { zone example.com. { primary 192.168.10.131; key DHCP_UPDATER; } zone 10.168.192.in-addr.arpa. { primary 192.168.10.131; key DHCP_UPDATER; } ddns-domainname "example.com."; ddns-rev-domainname "in-addr.arpa."; option domain-name "example.com"; host client-private { hardware ethernet ...; fixed-address 192.168.10.13; } ... } # The 'public' network. subnet 192.168.0.0 netmask 255.255.255.0 { zone example.com. { primary 192.168.0.131; key DHCP_UPDATER; } zone 0.168.192.in-addr.arpa. { primary 192.168.0.131; key DHCP_UPDATER; } ddns-domainname "example.com."; ddns-rev-domainname "in-addr.arpa."; option domain-name "example.com"; host client-public { hardware ethernet ...; fixed-address 192.168.0.13; } ... }
'ns1'服务器运行两个'named'实例,一个监听环回和专用networking接口,另一个监听公共接口。
开始第一个实例产生:
May 10 01:24:32 ns1 named[6610]: starting BIND 9.8.1-P1 -u bind May 10 01:24:32 ns1 named[6610]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' 'CPPFLAGS=-D_FORTIFY_SOURCE=2' May 10 01:24:32 ns1 named[6610]: adjusted limit on open files from 4096 to 1048576 May 10 01:24:32 ns1 named[6610]: found 2 CPUs, using 2 worker threads May 10 01:24:32 ns1 named[6610]: using up to 4096 sockets May 10 01:24:32 ns1 named[6610]: loading configuration from '/etc/bind/named.conf' May 10 01:24:32 ns1 named[6610]: reading built-in trusted keys from file '/etc/bind/bind.keys' May 10 01:24:32 ns1 named[6610]: using default UDP/IPv4 port range: [1024, 65535] May 10 01:24:32 ns1 named[6610]: using default UDP/IPv6 port range: [1024, 65535] May 10 01:24:32 ns1 named[6610]: listening on IPv4 interface lo, 127.0.0.1#53 May 10 01:24:32 ns1 named[6610]: listening on IPv4 interface eth0, 192.168.10.131#53 May 10 01:24:32 ns1 named[6610]: generating session key for dynamic DNS May 10 01:24:32 ns1 named[6610]: sizing zone task pool based on 7 zones May 10 01:24:32 ns1 named[6610]: set up managed keys zone for view _default, file 'managed-keys.bind' May 10 01:24:32 ns1 named[6610]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones May 10 01:24:32 ns1 named[6610]: automatic empty zone: 254.169.IN-ADDR.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 2.0.192.IN-ADDR.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 100.51.198.IN-ADDR.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 113.0.203.IN-ADDR.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: DFIP6.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 8.EFIP6.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 9.EFIP6.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: AEFIP6.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: BEFIP6.ARPA May 10 01:24:32 ns1 named[6610]: automatic empty zone: 8.BD0.1.0.0.2.IP6.ARPA May 10 01:24:32 ns1 named[6610]: command channel listening on 127.0.0.1#953 May 10 01:24:32 ns1 named[6610]: couldn't add command channel ::1#953: address not available May 10 01:24:32 ns1 named[6610]: zone 0.in-addr.arpa/IN: loaded serial 1 May 10 01:24:32 ns1 named[6610]: zone 127.in-addr.arpa/IN: loaded serial 1 May 10 01:24:32 ns1 named[6610]: zone 10.168.192.in-addr.arpa/IN: loaded serial 2013092337 May 10 01:24:32 ns1 named[6610]: zone 255.in-addr.arpa/IN: loaded serial 1 May 10 01:24:32 ns1 named[6610]: zone localhost/IN: loaded serial 2 May 10 01:24:32 ns1 named[6610]: zone example.com/IN: loaded serial 2013092554 May 10 01:24:32 ns1 named[6610]: managed-keys-zone ./IN: loaded serial 59 May 10 01:24:32 ns1 named[6610]: zone example.com/IN: sending notifies (serial 2013092554) May 10 01:24:32 ns1 named[6610]: zone 10.168.192.in-addr.arpa/IN: sending notifies (serial 2013092337) May 10 01:24:32 ns1 named[6610]: running
开始第二个实例:
May 10 01:24:54 ns1 named[6635]: starting BIND 9.8.1-P1 -u bind -c /etc/bind/named-1.conf May 10 01:24:54 ns1 named[6635]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' 'CPPFLAGS=-D_FORTIFY_SOURCE=2' May 10 01:24:54 ns1 named[6635]: adjusted limit on open files from 4096 to 1048576 May 10 01:24:54 ns1 named[6635]: found 2 CPUs, using 2 worker threads May 10 01:24:54 ns1 named[6635]: using up to 4096 sockets May 10 01:24:54 ns1 named[6635]: loading configuration from '/etc/bind/named-1.conf' May 10 01:24:54 ns1 named[6635]: reading built-in trusted keys from file '/etc/bind/bind.keys' May 10 01:24:54 ns1 named[6635]: using default UDP/IPv4 port range: [1024, 65535] May 10 01:24:54 ns1 named[6635]: using default UDP/IPv6 port range: [1024, 65535] May 10 01:24:54 ns1 named[6635]: listening on IPv4 interface eth1, 192.168.0.131#53 May 10 01:24:54 ns1 named[6635]: generating session key for dynamic DNS May 10 01:24:54 ns1 named[6635]: sizing zone task pool based on 7 zones May 10 01:24:54 ns1 named[6635]: set up managed keys zone for view _default, file 'managed-keys.bind' May 10 01:24:54 ns1 named[6635]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones May 10 01:24:54 ns1 named[6635]: automatic empty zone: 254.169.IN-ADDR.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 2.0.192.IN-ADDR.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 100.51.198.IN-ADDR.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 113.0.203.IN-ADDR.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: DFIP6.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 8.EFIP6.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 9.EFIP6.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: AEFIP6.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: BEFIP6.ARPA May 10 01:24:54 ns1 named[6635]: automatic empty zone: 8.BD0.1.0.0.2.IP6.ARPA May 10 01:24:54 ns1 named[6635]: command channel listening on 192.168.0.131#953 May 10 01:24:54 ns1 named[6635]: zone 0.in-addr.arpa/IN: loaded serial 1 May 10 01:24:54 ns1 named[6635]: zone 127.in-addr.arpa/IN: loaded serial 1 May 10 01:24:54 ns1 named[6635]: zone 0.168.192.in-addr.arpa/IN: loaded serial 2013092346 May 10 01:24:54 ns1 named[6635]: zone 255.in-addr.arpa/IN: loaded serial 1 May 10 01:24:54 ns1 named[6635]: zone localhost/IN: loaded serial 2 May 10 01:24:54 ns1 named[6635]: zone example.com/IN: loaded serial 2013092573 May 10 01:24:54 ns1 named[6635]: managed-keys-zone ./IN: loaded serial 59 May 10 01:24:54 ns1 named[6635]: zone example.com/IN: sending notifies (serial 2013092573) May 10 01:24:54 ns1 named[6635]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 2013092346) May 10 01:24:54 ns1 named[6635]: running
所有的机器都是虚拟的,使用Ubuntu Server 12.04。
我的期望是当客户端请求在专用networking上'dhcp1'将在相应的专用接口(即'192.168.10.131')上更新'ns1'的IP地址。 当客户端请求在该networking上的IP地址时,我也希望'dhcp1'在公共接口'192.168.0.131'上更新'ns1'。 虽然反向区域更新发生在相应的接口上,但是“dhcp1”总是启动两个networking的前向区域更新到名称服务器的公共接口(即“192.168.0.131”)。
我做错了什么,这是一个错误在isc-dhcp-server,function等? 如果我没有提供足够的具体信息,请让我知道。 有关使用isc-dhcp-server和bind9的多宿主方法的networkingsearch对我而言并没有太多回报。
任何信息,你可以提供在赞赏。 谢谢。
看来区域在configuration中必须是唯一的。
我在dhcpd.conf手册页中找不到这个,但是通过代码挖掘,用configuration进行猜测,给出了服务器实现的概念:
192.168.0.0子网中的区域。 在这一点上,现有的“example.com”。 哈希映射区域数据被replace为新的信息,包括主名称服务器。 由于反向区域是唯一的,因此每个区域都添加到地图中。 192.168.0.131 。 重新排列configuration文件中的子网信息似乎证实了这一点,因为所有的转发区更新被发送到192.168.10.131 。 因此,我的设置可能需要为每个接口单独的dhcpd守护程序,就像我为named所做的那样。 我仍然很好奇这种高可用性networking的多宿主方法是否普遍,如果我正确地做了这些工作。 即使我的问题似乎得到了回答,但任何build议都是值得欢迎的。