Nameserver should respond with A and AAAA records for websites

[fauno]

Since Godaddy doesn't support ALIAS records, we had to delegate a domain name to dns.he.net to create an ALIAS to api.distributed.press so it keeps IP addresses in sync, and NS to _dnslink for P2P protocols.

If the DP nameserver could craft answers for A/AAAA queries for websites pointing to its own IP address, it would be easy to just delegate the domain to DP and not having to configure a third party nameserver.

Right now it seems to be ignoring the query type, I ask for A records and returns TXT:

drill a custom.domain @api.distributed.press
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 57997
;; flags: qr rd ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; custom.domain. IN      A

;; ANSWER SECTION:
custom.domain.    60      IN      TXT     "dnslink=/ipns/XXXX/"
custom.domain.    60      IN      TXT     "dnslink=/hyper/XXXX/"

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 179 msec
;; SERVER: 198.50.215.13
;; WHEN: Wed Oct 25 19:04:32 2023
;; MSG SIZE  rcvd: 222

[fauno]

Also for completion respond to NS queries

[RangerMauve]

Interesting, that means we'd need to tell the server what it's IPv4 and IPv6 is when launching it.

Here's what we'd need:

• New (optional) options for ipv4 and ipv6 when initializing the server here
• pass those options to the dns module
• in the dns resolution code respond with those addresses for a and aaaa if the options were supplied
• add test

[fauno]

Alternatively you could emulate ALIAS/ANAME by resolving the IP addresses from host option and craft A/AAAA records on the fly

[fauno]

Support for this would make it simpler to set DNS records because you'd only have to set a single NS record to api.distributed.press. :D

More complex setups (ie. domains with subdomains and/or e-mail) could still use ALIAS/ANAME/A/AAAA/CNAME.