Skip to content
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.

Additional rules needed for SOA mname #504

Open
jdef opened this issue Jul 11, 2017 · 1 comment
Open

Additional rules needed for SOA mname #504

jdef opened this issue Jul 11, 2017 · 1 comment

Comments

@jdef
Copy link
Contributor

jdef commented Jul 11, 2017

There's another, related issue that we could solve as part of this ticket: if the SOA mname isn't part of the mesos-dns domain, then mesos-dns SHALL NOT report an A RR. We don't perform any checks for this (https://github.com/mesosphere/mesos-dns/blob/9d21ea6de38bd371e34bde196ceaee94cdac8a2c/records/generator.go#L478).

See the examples here: http://www.zytrax.com/books/dns/ch8/soa.html

We should either:
(a) validate that the SOA mname is within the mesos-dns domain, or else;
(b) NOT generate A RR's for an mname that is outside the scope of the mesos-dns domain

@jdef
Copy link
Contributor Author

jdef commented Oct 9, 2017

related: DNS glue entries https://serverfault.com/questions/309622/what-is-a-glue-record

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

No branches or pull requests

1 participant