You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More specifically, when you set DHCP options, if you're not specifying external/own DNS NS, then you would (probably) want to default to the standard AWS NS. This should probably be the default behavior, but it isn't. What actually happens when you don't specify domain_name_servers is that resolution breaks (or rather you have to manually configure it to make it work by editing /etc/resolv.conf to point to default AWS NS or such). That's fine, but it should at least be mentioned in the docs.
The documentation here doesn't mention anything about how to keep the default AWS NS: https://www.terraform.io/docs/providers/aws/r/vpc_dhcp_options.html
More specifically, when you set DHCP options, if you're not specifying external/own DNS NS, then you would (probably) want to default to the standard AWS NS. This should probably be the default behavior, but it isn't. What actually happens when you don't specify
domain_name_servers
is that resolution breaks (or rather you have to manually configure it to make it work by editing/etc/resolv.conf
to point to default AWS NS or such). That's fine, but it should at least be mentioned in the docs.For more on this: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html#AmazonDNS
I'll make a PR to include a note and warning about this behavior in the docs.
The text was updated successfully, but these errors were encountered: