switching from A records to NS records.

[FWEEaaaa1]

Requirements

• I agree to the Terms of Service.
• My file is following the domain structure.
• My website is reachable and completed.
• My website is software development related.
• My website is not for commercial use.
• I have provided contact information in the owner key.
• I have provided a preview of my website below.

Website Preview

https://job.is-a.dev

Now you may be asking.. Why are you getting NS records?

There are a couple reasons why which I am happy to explain below:
Realistically speaking, I have been with is-a.dev for a long time now enough for you all to trust me using NS records, knowing I won't abuse use of them (since May 2025 around that time).
And another reason is it creates an ease of access not just for me, but for the maintainers too. If I want to make a project, then it will be more easier for me over NS records as I won't need to make a PR every 5 minutes, which will obviously tire me out and be a LOT more time consuming, and it's also time consuming for maintainers as they'll need to merge a LOT of PRs every couple of seconds lol.
And with NS records, it will be easy for me to manage my records. I also have a minecraft server under this domain, and it will be easy for me to edit my web server if it somehow goes down or has an issue, instead of me making a PR if some downtime happens with my servers.
Rest assured, I can GUARANTEE you that there is nothing going on with my website, and I will not abuse NS records. I've donated to this project before and I am active on the discord server. I've also been here long enough for you all to trust me, so therefore I can assure you that I will not be abusing NS records and there is nothing going on with my website right now.
Thank you for reviewing.

[is-a-dev-reviewbot]

Hi there! 👋

You've successfully made a pull request! Here are some steps to do while waiting for a maintainer to review the pull request:

1. Check if the checks have failed or passed. You should see the status at the bottom of the pull request or a icon next to the commit ID. You can click on the 3 dots next to the "CI / Tests" check then click "View details", it will show you the logs of the tests.
2. Check if the filename, file format, and records are valid. If you don't know if it's valid, please read this part of the documentation and use a JSON validator/formatter, like jsonlint. Make sure that the file is in the domains directory and not somewhere else in the repository.
3. Please make sure that you've filled out the pull request template. It is generally not a good idea to overwrite the pull request template with something else unless you know what you are doing. Make sure to add either a publicly available preview of your website or a screenshot of it.
4. Please wait patiently. Pull requests may take between a couple hours to 3 days. All of the maintainer team are volunteers and try to review the pull requests in their spare time. If you want a chance of getting your pull request merged faster then send your pull request number once in the #pull-requests channel in our Discord server and wait patiently.
5. Please note that mentioning maintainers in pull requests without it being reviewed could lead to you getting marked as "low priority"; this also applies to pinging the maintainers in the Discord server or messaging the maintainers in private to review the pull request.

Note: if you've opened this pull request while there is a high number of other open pull requests, your wait time will be longer than usual. Please be patient!

[FWEEaaaa1]

and P.S i have a LOT of servers under this domain which is kind of hard to manage under an A record only.
sorry for writing and updating here so many times.
I'll leave you all to make your decisions.