Ask Your Question
0

What causes "Could not resolve ... no name for ..." log entries?

asked 2014-11-12 12:48:26 -0500

Joseph Carlos gravatar image

updated 2014-11-12 15:36:26 -0500

I am seeing quite a few lines in my log files on the Puppet CA server like this:

puppet-master[2618]: Could not resolve 172.16.216.200: no name for 172.16.216.200

At first I thought it was because the address 172.16.216.200 did not have an associated DNS entry, but that is not the case: it does.

What else might be causing these log entries?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2014-11-13 06:26:40 -0500

rnelson0 gravatar image

While it sounds like you checked for a PTR record for 172.16.216.200, it is unclear where you performed that check, on the master or another node. Is the master able to resolve the PTR record? It is not uncommon for a master to have different DNS servers than other network nodes, often by accident, that can introduce such issues.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2014-11-12 12:48:26 -0500

Seen: 999 times

Last updated: Nov 13 '14