I may have been able to solve my problem by moving the ddns-domainname option into the individual subnet blocks (of which I will have hundreds):<div><br></div><div><div>subnet 172.21.33.0 netmask 255.255.255.240 {</div><div>
option subnet-mask 255.255.255.240;</div><div> option routers 172.21.33.1;</div><div> ddns-domainname "x.domain.tld.";</div><div> pool {</div><div> failover peer "dhcp-failover";</div><div> max-lease-time 1800; # 30 minutes</div>
<div> range 172.21.33.5 172.21.33.14;</div><div> }</div><div>}</div></div><div><br></div><div>Can anyone think of a reason why this either would not work, or should not be done?</div><div><br></div><div>Thanks,</div><div>
Kyle</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 5, 2012 at 1:02 PM, Kyle Johnson <span dir="ltr"><<a href="mailto:kjohnson@fixertec.net" target="_blank">kjohnson@fixertec.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi John,<div><br></div><div>Please forgive my ignorance if I am misunderstanding what you are getting at. In my environment, the domain name is not determined by the type of server. All linux servers will never be a member of x.domain.tld, and all windows servers will never be a member of y.domain.tld. Also, as we are not doing any type of static reservations and have no idea what the MAC address of our servers will be before they're spun up (virtual hosts), I couldn't group them by MAC addresses.</div>
<div><br></div><div>Thanks for your time!</div><span class="HOEnZb"><font color="#888888"><div>Kyle</div></font></span><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 5, 2012 at 11:54 AM, John Miller <span dir="ltr"><<a href="mailto:johnmill@brandeis.edu" target="_blank">johnmill@brandeis.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Kyle,<br><br>Since you're doing this with servers, could you just create a host group for each of VMware, Linux, and Windows, put your hosts in there, then specify a ddns-domainname for each group?<br>
<br>John<br>-- <br>
John Miller<br>Systems Engineer<br>Brandeis University<br><a href="mailto:johnmill@brandeis.edu" target="_blank">johnmill@brandeis.edu</a><br><a href="tel:%28781%29%20736-4619" value="+17817364619" target="_blank">(781) 736-4619</a><br>
<br><div class="gmail_quote"><div><div>On Wed, Dec 5, 2012 at 11:47 AM, Kyle Johnson <span dir="ltr"><<a href="mailto:kjohnson@fixertec.net" target="_blank">kjohnson@fixertec.net</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Hello everyone,<div><br></div><div>I am attempting to configure a failover DHCP solution with DDNS and am running into an issue with isc-dhcpd version 4.1.1. The issue seems to be that if the ddns-domainname option is not configured in dhcpd.conf, the DDNS update is not sent to the DNS server for any zone. That is, with ddns-domainame commented out, dhcpd does not attempt to do any type of DDNS updates.</div>
<div><br></div><div>Configuring a single ddns-domainname will not work as we have multiple zones, each for a different domain. For this to work, I imagine that the client (e.g. ESXi hosts, linux and windows servers) would need to send a FQDN, which the DHCP server would then need to use when sending the DDNS update to the DNS server.</div>
<div><br>What is the correct way to configure both DHCP and my clients to allow DDNS to work for multiple zones (domains)?</div><div><br>Thanks,</div><div>Kyle</div>
<br></div></div>_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">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><br clear="all"><br>
<br>_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">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></div>
</div></div></blockquote></div><br></div>