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

Update dnsdock container version #136

Closed
tekante opened this issue Jan 29, 2018 · 1 comment
Closed

Update dnsdock container version #136

tekante opened this issue Jan 29, 2018 · 1 comment
Assignees

Comments

@tekante
Copy link
Member

tekante commented Jan 29, 2018

Rig currently launches a DNSDock container at version 1.16-1 which suffers from a fatal error if a read timeout is received on the backup DNS server. See aacebedo/dnsdock#90

Rig has restart always set so that the container comes back but during the intervening time DNS requests fail (including the original request). One way to ameliorate this is to select a different DNS server from the default 8.8.8.8 (by using the RIG_NAMESERVERS environmental variable) if connections to 8.8.8.8 are proving unstable.

Updating rig to use version 1.16-3 or better should change this to a warning as opposed to an error. It won't solve an underlying problem with a backup DNS instance being reachable but it will reduce some of the impact in terms of the service needing to fully restart.

@tekante
Copy link
Member Author

tekante commented Jan 29, 2018

Fixed by #137

@tekante tekante closed this as completed Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants