faq.md - is-a-dev-docs - is-a.dev Documentation

faq.md (5613B)
      1 ---
      2 icon: question
      3 label: FAQ
      4 route: /faq
      5 tags: useful
      6 ---
      7 
      8 # 📘 Frequently Asked Questions (FAQ)
      9 
     10 This page provides our most frequently asked questions regarding our service.
     11 
     12 ## Which DNS record types are supported?
     13 
     14 We support the following DNS record types:
     15 
     16 * `A`
     17 * `AAAA`
     18 * `CAA`
     19 * `CNAME`
     20 * `DS`
     21   * *Note: Can only be used alongside `NS` records.*
     22 * `MX`
     23 * `NS`
     24   * *Note: Only approved in specific cases. See [Who can use NS records?](#who-can-use-ns-records) for details.*
     25 * `SRV`
     26 * `TLSA`
     27 * `TXT`
     28 * `URL`
     29   * *Note: This is not a true DNS record. It is a custom made redirector specifically for is-a.dev.*
     30 
     31 ---
     32 
     33 ## Why does my domain still redirect to the is-a.dev homepage?
     34 
     35 This usually happens due to browser caching. [Clear your browser cache](https://support.google.com/accounts/answer/32050) and try again.
     36 
     37 ---
     38 
     39 ## Can I use a CNAME record with other record types?
     40 
     41 No, unless the domain is proxied. A `CNAME` cannot be combined with other record types (`A`, `MX`, `TXT`, etc.) in the same record set. For exceptions and setup instructions, see [Proxying Your Domain](https://docs.is-a.dev/domain-structure/#-proxied-optional).
     42 
     43 ---
     44 
     45 ## How long does it take for my pull request to be merged?
     46 
     47 We're a team of volunteers, and is-a.dev is a side project for us, so review times can vary. We'll get to your PR as soon as we can.
     48 
     49 ---
     50 
     51 ## Which platforms or services are supported?
     52 
     53 While you can use almost any service, these are the most commonly used with is-a.dev:
     54 
     55 * Cloudflare Pages
     56 * GitHub Pages
     57 * Netlify
     58 * Railway
     59 * Vercel
     60 
     61 ---
     62 
     63 ## Can I create nested subdomains (e.g., `sub.example.is-a.dev`)?
     64 
     65 Yes! You can nest subdomains as deeply as you'd like. To create one, name your file like `blog.example.json`. You **must own** `example.is-a.dev` to register `blog.example.is-a.dev`.
     66 
     67 ---
     68 
     69 ## I get an SSL error using GitHub Pages. How do I fix it?
     70 
     71 Go to your GitHub Pages settings for your repository and **enable "Enforce HTTPS"**. This resolves most SSL issues.
     72 
     73 ---
     74 
     75 ## Can I become a maintainer or join the is-a.dev team?
     76 
     77 We don't accept direct applications. Team members are **handpicked**, often based on community involvement and support activity. Even then, it does **not guarantee** a position.
     78 
     79 ---
     80 
     81 ## I accidentally leaked sensitive data in my PR, what can I do?
     82 
     83 * If **your PR containing sensitive information has not been merged**, contact us immediately:
     84 
     85   * Email: [admin@is-a.dev](mailto:admin@is-a.dev)
     86   * Discord: [@williamharrison](https://discord.com/users/853158265466257448)
     87 
     88 * If your PR **has already been merged**, we cannot retroactively remove it.
     89 
     90 ---
     91 
     92 ## Can I use my domain for a Minecraft server?
     93 
     94 Yes, use an `A` record and an `SRV` record.
     95 Refer to this [Namecheap article](https://www.namecheap.com/support/knowledgebase/article.aspx/9765/2208/how-can-i-link-my-domain-name-to-a-minecraft-server) for guidance.
     96 
     97 > ⚠️ Root subdomains (e.g., `yourname.is-a.dev`) **must relate to software development** as required in our [Terms of Service](https://is-a.dev/terms).
     98 > Use a *nested* subdomain (e.g., `mc.yourname.is-a.dev`) for Minecraft.
     99 
    100 ---
    101 
    102 ## Who can use NS records?
    103 
    104 We **allow** NS records only when:
    105 
    106 * The standard DNS record types we support aren't sufficient.
    107 * A provider (e.g. Aternos) **requires** NS delegation and **does not** have any other method of setting up a subdomain.
    108   * This is mostly regarding SaaS providers, **not** DNS providers like Cloudflare or deSEC.
    109 
    110 We **do not allow** NS records for:
    111 
    112 * Self hosting
    113   * **Note**: This can vary from case to case
    114 * Convenience or ease of use
    115 * Unverifiable or unsupported claims
    116 * Non-functional or placeholder purposes
    117 * Self hosting websites that can be easily hosted on a free platform like GitHub Pages
    118 * If we have security or abuse concerns
    119 * New users of is-a.dev
    120   * If you have not had an is-a.dev subdomain for at least 30 days, you will be denied due to security reasons.
    121 * Users that have abused is-a.dev subdomains in the past
    122 
    123 > ⚠️ **We reserve the right to deny any NS request at our discretion for any reason.**
    124 
    125 All NS record requests are reviewed on a case by case basis by the service owner.
    126 
    127 Any PRs that clearly lack approved reasoning or evidence can be immediately denied by any maintainer, without a review from the service owner.
    128 If denied by another maintainer, you do reserve the right to request a more thorough review from the service owner, which is possible by requesting the maintainer to escalate the PR.
    129 
    130 > How long will it take for my NS record request to be reviewed?
    131 
    132 Times can vary, usually within 24-72 hours, however in some rare cases it can take up to 2 weeks.
    133 
    134 ---
    135 
    136 ## Why are NS records restricted?
    137 
    138 NS records give full control over DNS for a subdomain. That opens the door to misuse, abuse, and security concerns. To protect the community and domain integrity, we must be strict about who receives NS delegation.
    139 
    140 ---
    141 
    142 ## How can I update or delete my is-a.dev subdomain?
    143 
    144 Follow these steps:
    145 
    146 1. **Review the [documentation](https://docs.is-a.dev) and [ToS](https://is-a.dev/terms)**.
    147 2. **Open your JSON file** (in `/domains/your-subdomain.json`).
    148 3. **Make your changes** (or delete the file if you're removing your domain).
    149 4. **Commit the changes** to your fork.
    150 5. **Push** them to your GitHub fork.
    151 6. **Open a pull request** from your forked repo.
    152 7. **Wait for approval and merging** by a maintainer.
    153 
    154 > 💡 Keep an eye on your pull request, we may request changes before merging.
    155 
    156 ## Why does my PR have the "low priority" label?
    157 
    158 This is because you have mentioned or messaged maintainers to get your PR approved.