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

Name servers should belong to zone they serve #857

Closed
wants to merge 1 commit into from
Closed

Conversation

k0da
Copy link
Collaborator

@k0da k0da commented Mar 23, 2022

There is a best practice, glue record should belong to zone it serves.
And records should be the same in dnsZone and edgeDNS

edgeDNS:

  • test.example.com 30 IN NS ns1.test.example.com
  • ns1.test.example.com 30 IN A 1.1.1.1

k8gb-coredns:

  • test.example.com 30 IN NS ns1.test.example.com
  • ns1.test.example.com 30 IN A 1.1.1.1

This commit changes the way NS and Glue records are named in edgeDNS

Signed-off-by: Dinar Valeev [email protected]

There is a best practice, glue record should belong to zone it serves.
And records should be the same in dnsZone and edgeDNS

edgeDNS:
- test.example.com 30 IN NS ns1.test.example.com
- ns1.test.example.com 30 IN A 1.1.1.1

k8gb-coredns:
- test.example.com 30 IN NS ns1.test.example.com
- ns1.test.example.com 30 IN A 1.1.1.1

This commit changes the way NS and Glue records are named in edgeDNS

Signed-off-by: Dinar Valeev <[email protected]>
@ytsarev
Copy link
Member

ytsarev commented Jan 5, 2024

@k0da do you plan to continue working on this PR?

@ytsarev
Copy link
Member

ytsarev commented Oct 2, 2024

It looks very stale, so I will close it. Feel free to reopen if needed!

@ytsarev ytsarev closed this Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants