Turned out the difference was that I had not configured a domain for the
machine. The dhcp server had been providing a domain. Once I added a
domain to my machine, everything worked with the static ip.
On Thu, Sep 6, 2012 at 9:27 AM, Bai Shen <baishen.lists@gmail.com> wrote:
> When I did my initial testing, I was running puppet on a network with an
> existing dhcp server. The puppet master received it''s ip from
that
> server. On the puppet master I ran my own dhcp server with next-server
> configured to point to the puppet master and to deny unknown hosts. This
> allowed me to use cobbler for just the specific machines I wanted to.
> Everything worked fine.
>
> Now I''m on another network and my puppet master has a static ip
and is the
> only dhcp server. When I do puppet cert --list --all I see the certs, but
> it no longer has the puppet dns name after it, and therefore my puppet
> client gets a cert host name mismatch and won''t connect.
>
> What about going from a dynamic to static ip caused this and how do I fix
> it?
>
> Thanks.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.