Hello. I have Cobbler setup and working nicely, but a new usage scenario has shown up for me. I'll need to be able to deploy hosts using DHCP and having the host register itself using DDNS and TSIG. One problem here is that there are several different TSIG keys for different subdomains, so there will be some conditionals. I also have Puppet running so worst case I could do it with that, but what would be really neat would be setting the hostname during the kickstart and having it register immediately so that you could just SSH into the host using the hostname right away.
Right now I'm thinking about having a script ask for the hostname and domain name in two separate reads, then doing a case statement to determine the TSIG, and finally using a here document to write the dhclient.conf so the host would register when it comes up after the post-install reboot. Does this seem like a sensible approach or am I missing some nifty builtin function that could handle this better?
We're using ISC BIND/DHCPD and I just upgraded to Cobbler 2.2 by the way.
Regards Johan Sunnerstig
Hi Johan,
Have you considered having the dhcpd server send the ddns info directly to bind? I was about to give that a try. (ddns-hostname in the dhcpd config template)
James
On Mon, May 7, 2012 at 1:04 AM, Johan Sunnerstig <Johan.Sunnerstig@auriga.se
wrote:
Hello. I have Cobbler setup and working nicely, but a new usage scenario has shown up for me. I'll need to be able to deploy hosts using DHCP and having the host register itself using DDNS and TSIG. One problem here is that there are several different TSIG keys for different subdomains, so there will be some conditionals. I also have Puppet running so worst case I could do it with that, but what would be really neat would be setting the hostname during the kickstart and having it register immediately so that you could just SSH into the host using the hostname right away.
Right now I'm thinking about having a script ask for the hostname and domain name in two separate reads, then doing a case statement to determine the TSIG, and finally using a here document to write the dhclient.conf so the host would register when it comes up after the post-install reboot. Does this seem like a sensible approach or am I missing some nifty builtin function that could handle this better?
We're using ISC BIND/DHCPD and I just upgraded to Cobbler 2.2 by the way.
Regards Johan Sunnerstig _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Hi. Another guy is dealing with the DNS/DHCP stuff(it's a whole project on its own since it includes IPv6 and some pretty wonky AD integration) so I pretty much just integrate with the stuff he's doing for now. Anyway, it ended up working fine as I described it and no nasty surprises so far so I'm pretty happy for now.
Regards Johan
From: cobbler-bounces@lists.fedorahosted.org [mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of James Clendenan Sent: den 10 maj 2012 03:35 To: cobbler mailing list Subject: Re: [cobbler] Hostname, dhcp and dyndns
Hi Johan,
Have you considered having the dhcpd server send the ddns info directly to bind? I was about to give that a try. (ddns-hostname in the dhcpd config template)
James On Mon, May 7, 2012 at 1:04 AM, Johan Sunnerstig <Johan.Sunnerstig@auriga.semailto:Johan.Sunnerstig@auriga.se> wrote: Hello. I have Cobbler setup and working nicely, but a new usage scenario has shown up for me. I'll need to be able to deploy hosts using DHCP and having the host register itself using DDNS and TSIG. One problem here is that there are several different TSIG keys for different subdomains, so there will be some conditionals. I also have Puppet running so worst case I could do it with that, but what would be really neat would be setting the hostname during the kickstart and having it register immediately so that you could just SSH into the host using the hostname right away.
Right now I'm thinking about having a script ask for the hostname and domain name in two separate reads, then doing a case statement to determine the TSIG, and finally using a here document to write the dhclient.conf so the host would register when it comes up after the post-install reboot. Does this seem like a sensible approach or am I missing some nifty builtin function that could handle this better?
We're using ISC BIND/DHCPD and I just upgraded to Cobbler 2.2 by the way.
Regards Johan Sunnerstig _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.orgmailto:cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler@lists.fedorahosted.org