terraform-provider-vultr

terraform-provider-vultr copied to clipboard

Hi. I'm just want to suggest add function that i need. I need to have ability create reserved IP and also set reverse dns record for IPs. Thank.

@grinay thanks for bringing this up. I've never used this functionality myself but I'm glad to hear about it. This issue will require two pieces:

• [ ] add reverse DNS to the IP resource
• [x] implement the reserved IP resource (c8cc3a14027ffb531c7316f48ba5f624081372b1)

Please let me know if I understood incorrectly.

Hello. Absolutely right. This is what I need. 

Суббота, 21 апреля 2018, 2:29 +11:00 от Lucas Servén [email protected]:

@grinay thanks for bringing this up. I've never used this functionality myself but I'm glad to hear about it. This issue will require to pieces: [ ] add reverse DNS to the IP resource [ ] implement the reserved IP resource Please let me know if I understood incorrectly. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread .

@squat

Can you confirm how to utilize the reserved IP functionality? I'd like to attach one to a server for VPN functionality.

The quoted commit doesn't seem to be about that functionality

From what I can tell, this was the commit you're referring to

https://github.com/squat/terraform-provider-vultr/commit/c8cc3a14027ffb531c7316f48ba5f624081372b1

@rtizzy, very right. Thanks I just updated the comment.

With a reserved IP you can create an IP separately from your VPS and keep it even after you tear down your servers or other Vultr infra. This way you can tie your DNS to a known value and it will remain known.

If you want to have a reserved IP that survives infra churn, then you may want to have to separate terraform configurations. Otherwise you can do it all in one. The general idea is:

• create server
• create reserved_ip attached to server
• create DNS tied to reserved_ip.cidr
• use server and DNS record as you wish in your manifests

I think this request is an excellent idea, it's always a good idea to have the A/PTR records in sync - especially if acting as an MTA.

I don't understand why we'd meed to consider a reserved IP? After being dynamically assigned a public IPv4 address, it should be a boolean defaulting to 'true' to also set the PTR record to match, if it's exposed via the API.

It seems to already be references in this upstream library: vendor/github.com/JamesClonk/vultr/lib/ip.go

Yes, this would also work. Reserved IPs were discussed in this thread simply because the original issue author said they required that feature.

Is there a timeline for when the Reverse DNS support will be shipped?