Step 1 script should ping the new puppetmaster hostname

[nfagerlund]

I botched the DNS on my test run, and it got me a bunch of worrying errors (and eventually an inconsistent state when I tried to run the step1 script a second and third time). Although Jeff tells me I could have just run puppet agent --test and called it good, even with the errors.

But that's beside the point: if the user's DNS isn't prepared properly, we should just bail immediately.

[nigelkersten]

+1

[jeffmccune]

I looked at some available options and I don't see a way to do this easily.

Ruby's resolv.rb doesn't even bother to look at nsswitch ... =(

the host command returns 1 if any nameserver responds with NXDOMAIN even if one of them did resolve the name...

Suggestions? I say we don't do this ticket.

[nfagerlund]

:/ There's really not a way to do this? Why not just ping -c 1?

I suppose it's not critical, but it will definitely make the UX of this fix worse for some users; I'm sure I'm not the only one who's gonna misconfigure their name resolution.

[jeffmccune]

On Tue, Oct 18, 2011 at 1:18 PM, nfagerlund <
reply@reply.github.com>wrote:

:/ There's really not a way to do this? Why not just ping -c 1?

I thought about this, but what if the host doesn't respond to ICMP messages?
Lots of places turn this off for "security"