FAQ
Frequently asked questions about subdomains, DNS, pull requests, and usage rules.
We currently support the following DNS record types:
A(IPv4)AAAA(IPv6)CNAME(alias)TXT(verification, metadata)MX(email servers)SRV(service location)CAA(certificate authority authorization)
See the Configuration page for examples.
This usually means your DNS config hasn’t been merged yet, or you’re still seeing cached DNS records. Once your PR is merged, give DNS changes some time (up to a few hours) to propagate.
No — DNS standards require that if you use a CNAME, it must be the only record for that subdomain. If you need multiple types (e.g., A + TXT), use A or AAAA instead.
Most pull requests are reviewed within 24–72 hours. If you follow all guidelines and your config is valid, it’ll be merged as soon as possible.
You can use any service that supports custom domains, including:
- GitHub Pages
- Vercel
- Netlify
- Cloudflare Pages
- Custom/self-hosted servers
Check out the DNS & Hosting guide for help setting these up.
No — at this time we only support one-level subdomains like yourname.owns.it.com. Nested or wildcard subdomains are not supported.
Make sure your GitHub repository has a CNAME file with your full subdomain and that GitHub Pages is configured to enforce HTTPS. Also confirm your DNS CNAME is correctly set.
We’re always open to thoughtful contributors. Open an issue or contribute consistently, and we’ll reach out if a maintainer spot opens up.
Yes. Immediately close the PR and open an issue or email us. We’ll help you remove the content from commit history as needed.
Yes, but you’ll need to use an A record pointing to your server’s IP address. Just make sure it doesn’t violate any of our rules.
We do not support NS records for custom delegation. All DNS is centrally managed by us to ensure stability and prevent abuse.
Allowing NS records opens up the potential for abuse, including unrestricted wildcard subdomains or spammy behavior. By managing DNS centrally, we maintain security and trust across all domains.
To update your subdomain, simply open another pull request modifying your existing config file.
To delete it, remove the file and open a PR with a message like remove yourname.owns.it.com.