Description

Current terraform provider does not manage dyndns (dynHost) resources. They can be created only from the web console.

The API endoints exists and could be used by the provider:

/domain/zone/{zoneName}/dynHost/login
/domain/zone/{zoneName}/dynHost/record

New Resource(s) and/or Data Source(s) that would be available:

• ovh_domain_dynhost_login
• ovh_domain_dynhost_record
  `

Potential Terraform Configuration

resource "ovh_domain_dynhost_login" "john" {
  zone      "example.org"
  subdomain "foo"
  password  "s3cr3t"
}

resource "ovh_domain_dynhost_record" "foo" {
  zone      "example.org"
  ip        "192.0.2.0"
  subdomain "foo"

  lifecycle {
    # this should be an implicit default in the provider
    ignore_changes [ ip ]
}