Closed hashibot closed 6 years ago
This is happening on Windows VMs as well. Just tested again in Terraform 0.9.11.
In the vm resource: domain = "${var.domain}"
Where ${var.domain} is the same variable used to join the machine to the domain elsewhere in the config - so the var itself is correct. End result as far as dns goes though is:
This can be overridden and set explicitly with the dns_suffix "optional" value.
Hey all,
This should now be functional as we have merged #185, which adds the domain to the customization spec properly. Closing this now, but if anyone is still having issues please open a new issue!
PS: To be specific on the relation of dns_suffixes
and domain
: the values specified in dns_suffixes
actually override what is in domain
, so if you want the domain name specified in domain
to be a search domain as well, it needs to specifically be in dns_suffixes
. This may change in futrue versions of the provider so that dns_suffixes
is more like extra_dns_search_domains
or something like that, to avoid duplication of values.
Thanks!
This issue was originally opened by @totojack as hashicorp/terraform#6658. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
terraform 0.6.16
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/totojack/4db892bf6d9b03b3b982401fedd8c2f6
Expected Behavior
domain value saved in files:
Actual Behavior
domain value saved as default value 'vsphere.local' in files:
Steps to Reproduce
add gateway to configuration terraform apply
Important Factoids
I'm testing with a Centos 7 VM on vsphere 6.