Ah, that explains it then; this is a 'manage_dhcp : 0' setup. Thanks!
On Thu, May 21, 2009 at 5:51 PM, Jeff Schroeder <[email protected]> wrote: > On Thu, May 21, 2009 at 8:12 AM, Dick Davies > <[email protected]> wrote: >> I can define static IP configured systems like this: >> >> cobbler system add --name=vera --hostname=vera.domainname >> --profile='centos-53-i386-puppet' \ >> --static=true --gateway=1.2.1.254 --subnet=255.255.128.0 >> --ip=1,2.5.27 --mac=00:0C:F1:f1:f1:f1 \ >> --name-servers='1.2.0.20 1.2.0.10' --name-servers-search='domainname' >> >> but that's a lot of typing :) anyway to inherit these (say from the profile)? >> >> I know, this is what DHCP is for :) but I need the values hardcoded >> into the machines >> after they're built. >> >> Tried setting 'default_name_servers' in cobbler/settings >> and it seemed to be a null-op; certainly had no effect on existing >> systems, even if I re-created their >> definitions. >> >> Am I missing something? Thanks! > > We have the same problem and get around it by putting the dns servers > in /etc/cobbler/dhcp.template. You need to statically define the > subnets via the normal isc dhcpd methods for each network. Anaconda > (network-manager actually) will pick them up and write them out to > resolve.conf during the intstall. Then everything works as expected. > Its pretty simple once you wrap your head around it. > > -- > Jeff Schroeder > > Don't drink and derive, alcohol and analysis don't mix. > http://www.digitalprognosis.com > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
