Repository navigation
Add DNS records for names owned in the W3BS Moshpit instance - #267
Merged
Merged
Conversation
Signed-off-by: Anthony Ettinger <anthony@chovy.com>
Signed-off-by: Anthony Ettinger <anthony@chovy.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
W3BS previously exposed registration and redirects but no DNS-record management. Add /net/records using the primary Moshpit records workflow: filter owned names, publish AAAA/CNAME/MX/TXT with TTL and MX priority, inspect and remove records, with inline success/errors and retained input. APIs enforce local W3BS ownership and active name/namespace status; imported primary-network records remain read-only. CNAME exclusivity is serialized, including PostgreSQL name-row locking. Discovery identifies this as a separate Moshpit instance.
The companion resolver change queries this instance's APIs for names under w3bs.org rather than treating the primary network's ownership as equivalent. DNS and public HTTPS readiness are explicitly separate; a registrar/ACME failure is not hidden by a successful resolver query.
Validation: full local suite 158 passed / 4 skipped; syntax/signature checks passed. New integration regression covers ownership, inactive namespaces, public reads, AAAA/MX/TXT, CNAME conflicts/concurrent writes, deletion and validation. Desktop 1440px and mobile 390px browser checks passed for publishing/removing, conflict feedback, retained input, retry, no JS errors and no overflow. CI also exercises PostgreSQL.