/etc/resolv.conf fails to be populated

TritonDataCenter / smartos-live

For more information, please see http://smartos.org/ For any questions that aren't answered there, please join the SmartOS discussion list: https://smartos.topicbox.com/groups/smartos-discuss

1.57k stars 244 forks source link

/etc/resolv.conf fails to be populated #949

Closed quanah closed 3 years ago

quanah commented 3 years ago

There is no requirement for a dns domain to be populated, however if one is not defined in /usbkey/config, the smartos hypervisor fails to populate /etc/resolv.conf breaking name resolution within the hypervisor. i.e.:

....
dns_resolvers=8.8.8.8
dns_domain=""

results in a broken system. This appears to be due to a bug in /lib/svc/method/net-physical, where it checks for:

if [[ -n ${CONFIG_dns_domain} ]] && [[ -n ${CONFIG_dns_resolvers} ]]; then

quanah commented 3 years ago

duplicate of #948 which I didn't realize was even created because GH threw a 404 error when I first tried to create. ;)