Malin
8d4eaa1489
- Clone all 5 Zonemaster component repos (LDNS, Engine, CLI, Backend, GUI) - Dockerfile.backend: 8-stage multi-stage build LDNS→Engine→CLI→Backend - Dockerfile.gui: Astro static build served via nginx - docker-compose.yml: backend (internal) + frontend (port 5353) - nginx.conf: root redirects to /es/, /api/ proxied to backend - zonemaster-gui/config.ts: defaultLanguage set to 'es' (Spanish) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
25 lines
933 B
Markdown
25 lines
933 B
Markdown
## RESTRICTION03: Character set restriction for label
|
|
|
|
### Test case identifier
|
|
|
|
**RESTRICTION03:** Character set restriction for label
|
|
|
|
### Objective
|
|
|
|
Even though section 11 of [RFC 2181](https://datatracker.ietf.org/doc/html/rfc2181) mentions
|
|
that any binary string could be part of a label, many of the registries will
|
|
not permit special symbols in the label. This is an habit pursued by the
|
|
registries based on section 2.1 of the [RFC 1123](https://datatracker.ietf.org/doc/html/rfc1123),
|
|
i.e. following the LDH (Letters, Digits and Hyphen) format. Even for the
|
|
IDNs [RFC 5892](https://datatracker.ietf.org/doc/html/rfc5892) limits to the LDH
|
|
format.
|
|
|
|
The objective for this test is verify whether the engine identifies the
|
|
domain names which is not in the LDH format.
|
|
|
|
### Result
|
|
|
|
The engine does not capture the restriction for LDH and the explanation is
|
|
provided here : https://github.com/zonemaster/zonemaster/issues/153
|
|
|