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

CNAME setting and processing in NNS #6

Open
roman-khimov opened this issue Sep 9, 2021 · 2 comments
Open

CNAME setting and processing in NNS #6

roman-khimov opened this issue Sep 9, 2021 · 2 comments

Comments

@roman-khimov
Copy link

I'm not sure NNS supports CNAME properly now, the behavior allows to set CNAME along with other types (like A or AAAA) and at the same time any non-CNAME record overrides CNAME in resolve. I don't think it's expected if we're roughly following DNS logic:
https://datatracker.ietf.org/doc/html/rfc1034#section-3.6.2
https://datatracker.ietf.org/doc/html/rfc2181#section-10.1

@erikzhang
Copy link
Member

I know that CNAME records and A or AAAA records cannot coexist. But if they are checked every time, additional GAS will be consumed. Do you think it is necessary?

@roman-khimov
Copy link
Author

We'll inevitably have misconfigured names otherwise. We can of course say that it's a user's problem, but preventing it seems a bit better to me. At the same time we'll have to use Find again probably and yes, it's somewhat expensive.

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

2 participants