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

dot or no dot #19

Open
c33s opened this issue Sep 7, 2020 · 1 comment
Open

dot or no dot #19

c33s opened this issue Sep 7, 2020 · 1 comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@c33s
Copy link

c33s commented Sep 7, 2020

for everyone configures bind dns server it's quite common to add a dot at the end of a domain in the config. some abstractions or gui interfaces try to help you and don't require you to add a dot on the end.

but how is it handled here? zone domain with dot or without dot? cname with dot or without? should be somehow handled in the provider docs and maybe add some warning messages if a cname record is created without a dot at the end.

@martinseener
Copy link

As far as I can see in the Hetzner DNS Console when creating entries or when using this terraform module (thx alot @timohirt !) I have to use the dot at the end of the name if it's already an FQDN and the actual domain should NOT be appended.
Code example for hetzners own DNS:

resource "hetznerdns_record" "domain_com_ns1" {
  zone_id = hetznerdns_zone.domain_com.id
  name    = "@"
  value   = "hydrogen.ns.hetzner.com."
  type    = "NS"
}

Same applies to the "name" so if you put in there "www" it will auto-append domain.com in DNS Zone later.

Hope this answers your question?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants