Updating your subdomain’s DNS records works the same way as the original registration: you edit your JSON file and open a new Pull Request against theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/creepersbs/register/llms.txt
Use this file to discover all available pages before exploring further.
creepersbs/register repository. There is no web panel — every change must go through GitHub. Once your PR is merged, the updated records go live within the normal review window.
Fork or sync your fork
If you already have a fork of
creepersbs/register, sync it with the latest main branch before making changes. Out-of-date forks can cause merge conflicts that delay your PR.On GitHub, open your fork and click Sync fork → Update branch to pull in the latest changes.Edit your existing JSON file
Navigate to the
/domains folder in your fork and open your existing registration file (e.g., yourname.json). Update the record values you want to change — for example, a new IP address in the "A" field, or an updated "TXT" entry.Do not rename the file or change the "subdomain" value. Only update the fields that need to change.Validate with JSONLint
Before opening the PR, paste your updated file into JSONLint and confirm it returns Valid JSON. A single misplaced comma or missing bracket will cause your PR to be rejected.
Open a Pull Request
In your fork, click Contribute → Open Pull Request. The PR description will be pre-filled with the official template. Fill it in as follows:
- Type of PR — check Update / Change DNS Records
- Your information — GitHub username and email
- Subdomain request details — the subdomain you are updating
- Description — briefly describe what you are changing and why
- Confirmation checkboxes — all three must be checked
As of the 04-17-2026 Terms of Service update, you must re-confirm the Terms of Service on every PR submission. All three confirmation checkboxes in the template must be checked before your PR can be reviewed.