DNSSR recommendations

  1. All data, including DNS records and distribution records, are stored in the local database. API requests are only made when adding, deleting, modifying, or querying records, ensuring both stability and fast performance.

  2. Added support for 3rd-level or 4th-level DNS records. (A host input field has been added when creating records.)

  3. To edit or delete a record, you first need to obtain the DNS record’s ID. This ID can be stored in the local database when the record is created, or retrieved by calling the list function.

  4. We have already enabled add/delete/update/query operations for NS records. Please use the corresponding API for these actions.

https://vps8.zz.cd/dnsopenapi

We hope more developers will use and make the most of our DNS Open API to build related applications.

Currently, regarding dnssr:

  1. Cannot resolve 3rd- and 4th-level records.

  2. Cannot delete or edit records. Deletion throws an error (ID is not retrieved or submitted), and there is no entry point for editing.

  3. Frequent API requests.

  4. Cannot handle NS records.

All of the above are points that can be improved.

Thank you for your support!

6 Likes

Correct.
If it only supported @, that would be quite a limitation.

OP’s analysis and suggestions are spot on—dnssr will only keep getting better.

1 Like

:xhj16:

1 Like

The original poster is a domain name expert, the number one in NL :ear_of_corn:.

1 Like

As expected, you’re a true expert—your advice is spot on.

The DNS API for NS is now online.

https://vps8.zz.cd/dnsopenapi

Experts are truly professional, no doubt about it…

My view is that professional matters should be left to the professionals—it’s not necessary to do everything yourself. Take building a car, for example: it might have a German engine, a Japanese transmission, a French dashboard, and Fuyao glass from China. Huye has the money and likes to do things his own way, wanting everything to be self-made: building his own forum, his own email service, his own domain distribution… dabbling in a bit of everything, but mastering none. The battlefront gets stretched too thin, and it’s not sustainable in the long run. I suggest VPS8 discuss with Huye and learn from the nodeloc community: the main platform stays with VPS8, and Huye can have his own dedicated distribution page. All his domains can be distributed through his personal page, and he only needs to have complete management rights over his own domains. The technical backend can be handled by the VPS8 platform, which will also give users more confidence.

Hu Ye wants to play on his own, and even wants to create a nodeloc (forum).

One day, he’ll turn back and sing with me: Only You~

1 Like

Changing the nameserver (NS) can only be done via the API? Looks like it can’t be operated on the VPS8 website—there’s no option to choose NS in the type menu (I’m referring to domains that aren’t distributed by VPS8).

Also, after waiting for a while, it seems like this NS hasn’t taken effect; it’s not showing up in lookups.

In VPS8, you don’t add an NS record; instead, go to the tab above to find Name Servers. You need to modify the name servers.

The DNS is propagating slowly in some regions. It’s already taken effect in some places.

Right, domains that aren’t from vps8 generally don’t support adding NS records. But he might still be able to do it using the API.

I did a test: for domains that aren’t VPS8, like x.x.x, I set up an ns called ok.x.x.x. Although it was added successfully via the API, it doesn’t actually take effect.

From my screenshots above, it looks like some of them have taken effect. Let’s check again in 48 hours.

Oh my god, 48 hours? Then it’s really going to be tricky for Hu Ye to manage those subdomains on the new platform. :ac01:

1 Like

It’s a DNS cache issue in various locations; it has nothing to do with us.

DNS resolution alone is useless; you need the other party’s system to actually host it for it to take effect. And once that’s done, it takes effect quickly.