DDNS for multiple zones

[Kyle Johnson]

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):

subnet 172.21.33.0 netmask 255.255.255.240 {
  option subnet-mask 255.255.255.240;
  option routers 172.21.33.1;
  ddns-domainname "x.domain.tld.";
  pool {
    failover peer "dhcp-failover";
    max-lease-time 1800; # 30 minutes
    range 172.21.33.5 172.21.33.14;
  }
}

Can anyone think of a reason why this either would not work, or should not
be done?

Thanks,
Kyle


On Wed, Dec 5, 2012 at 1:02 PM, Kyle Johnson <kjohnson at fixertec.net> wrote:

> Hi John,
>
> 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.
>
> Thanks for your time!
> Kyle
>
>
> On Wed, Dec 5, 2012 at 11:54 AM, John Miller <johnmill at brandeis.edu>wrote:
>
>> Hi Kyle,
>>
>> 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?
>>
>> John
>> --
>> John Miller
>> Systems Engineer
>> Brandeis University
>> johnmill at brandeis.edu
>> (781) 736-4619
>>
>> On Wed, Dec 5, 2012 at 11:47 AM, Kyle Johnson <kjohnson at fixertec.net>wrote:
>>
>>> Hello everyone,
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> What is the correct way to configure both DHCP and my clients to allow
>>> DDNS to work for multiple zones (domains)?
>>>
>>> Thanks,
>>> Kyle
>>>
>>> _______________________________________________
>>> dhcp-users mailing list
>>> dhcp-users at lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>>
>>
>>
>>
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20121205/5db19363/attachment-0001.html>