Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Periodically run cmk --update-dns-cache #50

Open
ypid opened this issue Feb 28, 2017 · 5 comments
Open

Periodically run cmk --update-dns-cache #50

ypid opened this issue Feb 28, 2017 · 5 comments

Comments

@ypid
Copy link
Member

ypid commented Feb 28, 2017

Hi

I just noticed that the DNS cache seems to be not updated automatically at least in my deployments (manually setup). Is the DNS cache periodically refreshed when using this role?

@ganto
Copy link
Member

ganto commented Feb 28, 2017

Thanks a lot for hint. So far that's not something that is taken care of by the role. I do this manually whenever I know that a DNS address of a host changed. Maybe I could add a task to refresh the DNS cache whenever the role is run?

@drybjed
Copy link

drybjed commented Feb 28, 2017

I don't like the idea of using Ansible as a dependency for periodical tasks. Ansible can be used to configure a cron entry to do this just fine. You can even involve batch to run the task when system is idle, if this is something intensive. Let the hosts take care of this problem themselves, don't involve sysadmins.

@ypid
Copy link
Member Author

ypid commented Feb 28, 2017

Thanks for the feedback. I would propose a cron job for this.

@ganto
Copy link
Member

ganto commented Feb 28, 2017

I don't really like the idea of a cronjob in this case. DNS changes is not something that "happen" spontaneously. If the IP address of a host is updated, then you need to update the host configuration anyway as the debops-contrib.checkmk_agent role will "hard-code" the IP address as agent property. Also I wouldn't want to wait for an hour (or so) until the DNS cache is updated. Additionally you might also need to update the host parent association (not yet implemented in this role) if you changed the subnet for example. To solve this issue properly there is more effort needed. That's why I do it manually so far...

@ypid
Copy link
Member Author

ypid commented Feb 28, 2017

Understandable. But it is not always the case that the one who updates the DNS also thinks about or even knowns about to run check_mk --update-dns-cache. Even when you do it manually I would at least run the update weekly or so to catch the case that this is forgotten (not saying that this has just happened to me 😉).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants