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

dhcp_dns don't seem to have any effect #562

Open
opentokix opened this issue Jun 19, 2024 · 2 comments
Open

dhcp_dns don't seem to have any effect #562

opentokix opened this issue Jun 19, 2024 · 2 comments
Labels

Comments

@opentokix
Copy link

opentokix commented Jun 19, 2024

resource "upcloud_network" "private-network" {
  name = "private-network"
  zone = "se-sto1"
  ip_network {
    address = "10.192.168.0/22"
    dhcp = true
    dhcp_default_route = true
    dhcp_dns = ["1.1.1.1", "1.0.0.1"]
    family = "IPv4"
  }
  router = upcloud_router.private-router.id
}

I have created a private network, and a router and get default routs but the dhcp_dns don't seem to be set on the network when I create a machine with a interface on this network.

@kangasta
Copy link
Contributor

Thank you for reporting this. We'll take a look 👀

@kangasta
Copy link
Contributor

This is not yet available for private networks. We will try to clarify the related documentation until dhcp_dns has effect when defined for private networks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants