Add standard for DNS - Githubissues

SovereignCloudStack / standards

SCS standards in a machine readable format

https://scs.community/

Creative Commons Attribution Share Alike 4.0 International

30 stars 21 forks source link

Add standard for DNS #570

Open markus-hentsch opened 2 months ago

markus-hentsch commented 2 months ago

Based on the latest findings of https://github.com/SovereignCloudStack/issues/issues/229 I made the following changes/additions:

only make the dns driver mandatory (not dns_domain_ports); this should be more then sufficient for internal DNS
for infrastructures offering DNSaaS (Designate), instead make dns_domain_ports mandatory and subnet_dns_published_fixed_ip recommended

markus-hentsch commented 2 months ago

I implemented a test script that verifies the existence of the API extensions as mandated by the current standard draft. The script queries the Neutron Extensions API and relies on the information it provides.

However, due to https://bugs.launchpad.net/neutron/+bug/2063669 the test will succeed in any OVN-based setup since the DNS extensions are always reported as being available even if none of them actually are.

Upstream needs to fix this for the test script to actually report accurate results ...

markus-hentsch commented 1 month ago

LGTM, beside missing two explanations for "OVM" and "OVS".

Thanks for pointing that out! This is quite important. I've added them to the glossary.

horazont commented 5 days ago

imho the standard should mandate RFC compliant DNS Servers that should be made available to the customer, given the fact there are a lot of non compliant dns servers out there.

Good idea. Do you have a list of RFCs a good recursor should adhere to? I'm not sure if we need to list the RFCs of all RRs which we expect to be supported or whether that's something any base-RFC-compliant recursor MUST handle correctly anyway (even though history has shown they don't always).