Unbound is not required and causes hostname lookup failure on AWS

NLnetLabs / krillmanager

Layered infrastructure as code for running Krill as a highly available scalable service with integration points for monitoring and log analysis.

BSD 3-Clause "New" or "Revised" License

0 stars 1 forks source link

Unbound is not required and causes hostname lookup failure on AWS #37

Closed ximon18 closed 4 years ago

ximon18 commented 4 years ago

The DigitalOcean image of KrillManager includes Unbound as the default resolver. It was at one point thought to help with an issue that was being seen but isn't actually needed, but was never removed. However in AWS this causes error messages to appear about the local host name not being resolvable due to bypassing AWS own internal DNS.

ximon18 commented 4 years ago

Done as part of #28.