oops, that range statement was a typo.<br><br>So about defining the zone... I found some blog post that used the secondary statement that way, but I suspected it wouldn't work since I couldn't find any reliable documentation that used it like that. So if you have two dns servers, how would you define them both as update recipients?<br>
<br>James<br><br><div class="gmail_quote">On Sat, Dec 12, 2009 at 6:13 AM, Glenn Satchell <span dir="ltr"><<a href="mailto:Glenn.Satchell@uniq.com.au">Glenn.Satchell@uniq.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi James<br>
<br>
Nice move from MS to Open Source!<br>
<br>
There's a couple of things with your config.<br>
<br>
The range statement gives the full range of IP addresses to be<br>
allocated. Thus, you should not include addresses in the range that<br>
will be allocated to other devices, or hosts with fixed addresses. So<br>
this is wrong:<br>
<div class="im"><br>
range 192.168.100.0 192.168.101.254;<br>
<br>
</div>It should not include the router's address, or the hosts with<br>
fixed-address, or the DNS servers. At least this:<br>
<br>
range 192.168.1100.6 192.168.101.254;<br>
<br>
The other important gotcha is that a host that is allocated an address<br>
in a host statement does not go through the same processing on the<br>
server as a host that gets adynamic address. The effect of this is that<br>
no DNS updates are performed for the fixed-address hosts.<br>
<br>
There are example DNS configurations in the dhcpd.conf man page, look<br>
for the section titled "DYNAMIC DNS UPDATE SECURITY". The "secondary"<br>
statement is for configuring failover and has nothing to do with DNS.<br>
Due to the way the parser works, it may not throw an error when a<br>
statement appears out of context.<br>
<br>
You need to enable logging on the DNS server to see what is happenning<br>
there, the default behaviour for BIND and most DNS servers is to<br>
silently ignore updates from a client that is not allowed to do so.<br>
<br>
Finally, it is typical to define the host statements in the global<br>
scope, not inside the subnet. There are subtle inheritance rules, and<br>
the global definition is the one you usually want. Defining it in the<br>
subnet scope does not bind it only to that subnet.<br>
<br>
regards,<br>
-glenn<br>
<br>
>From: James Dinkel <<a href="mailto:jdinkel@gmail.com">jdinkel@gmail.com</a>><br>
>Date: Fri, 11 Dec 2009 16:36:27 -0600<br>
>Subject: dhcp not updating dns server<br>
>To: <a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
>X-BeenThere: <a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<div><div></div><div class="h5">><br>
> I'm putting in an ISC DHCPD server to replace Microsoft DHCP server<br>
> because it is a pain in the neck managing reserved hosts in Microsoft's<br>
> DHCP.<br>
><br>
> Anyway, it won't add the clients that it assigns addresses for to the<br>
> DNS servers. I've set the zones on the dns servers to accept secure and<br>
> non-secure updates, and here is my dhcpd.conf:<br>
> --------------------<br>
> ##### SERVER SETTINGS #####<br>
><br>
> ddns-update-style interim;<br>
> ignore client-updates;<br>
> update-static-leases on;<br>
><br>
> zone <a href="http://bucoks.com" target="_blank">bucoks.com</a> {<br>
> primary 192.168.100.2;<br>
> secondary 192.168.100.3;<br>
> }<br>
> zone 100.168.192.in-addr.arpa. {<br>
> primary 192.168.100.2;<br>
> secondary 192.168.100.3;<br>
> }<br>
><br>
> option domain-name "<a href="http://company.com" target="_blank">company.com</a>";<br>
> option domain-name-servers 192.168.100.2, 192.168.100.3;<br>
><br>
> # 8-day leases<br>
> default-lease-time 69102;<br>
><br>
> # disable bootp<br>
> deny bootp;<br>
> #deny dynamic bootp clients;<br>
><br>
> ##### SUBNET SETTINGS #####<br>
><br>
> subnet 192.168.100.0 netmask 255.255.254.0 {<br>
> option routers 192.168.100.1;<br>
> option subnet-mask 255.255.254.0;<br>
><br>
> range 192.168.100.0 192.168.101.254;<br>
><br>
> host server1 {<br>
> option host-name "<a href="http://server1.company.com" target="_blank">server1.company.com</a>";<br>
> hardware ethernet 00:XX:XX:XX:XX:XX;<br>
> fixed-address 192.168.100.4;<br>
> } # end of host<br>
><br>
> host server2 {<br>
> option host-name "<a href="http://server2.company.com" target="_blank">server2.company.com</a>";<br>
> hardware ethernet 00:XX:XX:XX:XX:XX;<br>
> fixed-address 192.168.100.5;<br>
> } # end of host<br>
><br>
> } # end of subnet<br>
> --------------------<br>
<br>
> I can't find anything about even attempting to update dns in the logs, just<br>
> that the dhcp addresses were requested and acknowledged, and all static and<br>
> dynamic clients are getting addresses just fine.<br>
><br>
> Any ideas? I'm not even sure if it's really not even trying to do the dns<br>
> updates or if I just need to set something to get some better logging? A<br>
> tcpdump shows that the dhcp server is not even attempting any communication<br>
> with the dns server.<br>
<br>
</div></div>_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote></div><br>