feat: add full Zonemaster stack with Docker and Spanish UI

- 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>

zonemaster/docs/public/specifications/tests/Methods.md

@@ -0,0 +1,74 @@
+# Methods common to Test Case Specifications (version 1)
+
+This is a list of generic Methods used in many Test Case specifications. The
+Test Cases that makes use of any of these Methods should link directly to
+this text.
+
+This document holds version 1 of the set of Methods. Version 2 is defined in
+[MethodsV2]. Methods from version 1 will be replaced by Methods from version 2 in
+all Test Case specifications.
+
+Before the transition all Test Cases specifications use version 1 (this
+document). During the transition it will be stated in each specification
+if the Test Case uses Methods from version 1 (this document) or Methods from
+version 2 ([MethodsV2]). When the transition is completed, this document will be
+removed.
+
+
+### Method 1: Obtain the parent domain
+
+This Method tries to obtain the parent domain from the domain used as input
+to this Method.
+
+1. A recursive SOA-record lookup for the child domain name starting at the
+   root domain should be done, and the steps of the process recorded.
+2. If the recursion reaches a name server that responds with a redirect
+   directly to the requested domain, including functional glue, the test
+   succeeds. The domain through which the name server was found is
+   considered the parent domain.  
+3. If the recursion reaches a name server that authoritatively responds
+   with NXDOMAIN for the child domain, the test succeeds. The domain through
+   which the name server was found is considered the parent domain.
+
+### Method 2: Obtain "glue Name records" from parent
+
+This Method tries to obtain the authoritative name servers from the
+delegation of the parent domain.
+
+1. Obtain the parent domain as input from Method 1.
+2. Send a query to the parent domain asking for the list of name servers
+   authoritative for the domain that is being tested 
+3. Record the list of name servers obtained from the authority section 
+
+### Method 3: Obtain name servers from child
+
+Just as in Method 2, this Method tries to obtain the name servers configured
+for the child zone from the child domain itself.
+
+1. A NS query for the domain is made to all listed name servers obtained
+   from Method 2. 
+2. Record all the unique name servers from the answers received from the query in 
+   step 1.
+
+### Method 4: Obtain "glue address records" from parent
+
+This Method tries to obtain any glue address records from the delegation
+in the parent zone.
+
+1. Query the servers in Method 2 for A and AAAA addresses.
+2. Record the unique IP addresses from the answers (both A and AAAA) in
+   the additional section, which are the glue address records for the
+   domain.
+
+### Method 5: Obtain the name server address records from child
+
+This Method tries to obtain the IP addresses for the name servers used in
+the child zone.
+
+1. Send an A query to all name servers obtained in Method 3.
+2. Record the list of unique IPv4 addresses in the answer section.
+3. Send an AAAA query to all name servers obtained in Method 3.
+4. Record the list of unique IPv6 addresses in the answer section.
+
+
+[MethodsV2]:                                    MethodsV2.md