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

Support DNAME Records #134

Closed
bhuntley-cu opened this issue Jun 6, 2017 · 6 comments
Closed

Support DNAME Records #134

bhuntley-cu opened this issue Jun 6, 2017 · 6 comments

Comments

@bhuntley-cu
Copy link

https://tools.ietf.org/html/rfc6672

Thanks!

@tlimoncelli
Copy link
Contributor

Which providers support this?

@bhuntley-cu
Copy link
Author

I had expected R53 to do so since the only DNAME record we have at this point came from Amazon SES, but it does appear that R53 and most of the other providers don't know what to do with them. Clearly, this is a feature request more about RFC compliance than a pressing need.

@tlimoncelli
Copy link
Contributor

Marking this "wontfix". We'll gladly reopen if someone has a live use-case.

@spreegabe
Copy link

my active directory / msdns environment has DNAME records. v3 silently ignores them and v4 crashes during get-zone.

failed GetZone gzr: msdns/convert.go:nativeToRecord rtype="DNAME" unknown: props=map[DomainNameAlias:asdfasdfasdfasdfasdf.gx.internal.cloudapp.net.] and map[]

@cafferata
Copy link
Collaborator

@spreegabe would you mind creating a new bug report issue? This GitHub issue concerns the implementation of DNAME record.

@spreegabe
Copy link

Of course. I guess I did find a use case though!

We'll gladly reopen if someone has a live use-case.

see #2840

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

No branches or pull requests

4 participants