Add nameserver on sub-domain

[shadowgaming100]

Is it possible to add name-server on test.your-domain.dedyn.Io

[fiwswe]

Are you asking whether you can add NS records to the subdomain test.your-domain.dedyn.io? If so, the answer is yes. Just add test NS your-ns1 and test NS your-ns2, etc. to your-domain.dedyn.io (where your-ns1 and your-ns2 are FQDNs of your name servers).

This would delegate the domain test.your-domain.dedyn.io to your name servers. As deSEC e.V. has the goal to encourage the use of DNSSEC you should use name servers that also support DNSSEC. And then you would also need to set the DS records corresponding to the DNSKEY used to sign the subdomain on your name servers. Note that if your name servers routinely rotate the DNSKEYs then you would need to automate updating the DS records as well.

However it is not clear to me why you would want to do this? Seems like a lot of trouble for very little gain.

fiwswe

[shadowgaming100]

I mean to add name server inside a sub-domain example
test.test.dedyn.io

[fiwswe]

Ok, so what is the problem? Just set the NS records on test in test.dedyn.io.

[d4708]

@fiwswe

However it is not clear to me why you would want to do this?

I’m using it for DNS seeder, but today found that can’t change it with the message:

Cannot modify NS records for this domain.

Cannot modify NS records for this domain

I have successfully used following configuration before: seed.domain.org NS ns1.domain.org ns1.domain.org A Server IP Now I found that something went wrong with resolver and seems the issue with desec, or I missed some updates. I’ve logged, removed old record, tried to create same new one, but got this message: Cannot modify NS records for this domain. Does NS feature still work or it is disabled (like new domains registration before)? Anyway I can’t add NS record back, after deleting i…

[fiwswe]

Yes, that info (my answer from 2023) is now outdated. Changing the NS records in subdomains of dedyn.io is no longer allowed. Please read dynDNS service down? - #3 by peter as advised in another thread.

You will need to bring your own domain, if you need to be able to change NS records. (However that only makes sense if you want to split off a subdomain as a separate zone. For the domain itself delegation needs to be handled by your domain registrar.)

[d4708]

Thanks for reply, I spent few days before understand that problem with domain provider and not my local server, also, in control panel it was my previous NS record, that confusing as looks well even does not work.

so I have experimentally removed it, and only after that understand that can’t add it back, and something changed in the desec policies again.

I maybe will use Alfis DNS,
because free providers never work stable for a while.

[fiwswe]

You are confusing the misuse of deSEC services with unstable operations. deSEC has a mission to propagate DNSSEC. Any use that does not further this goal is and always was unsupported. The change that a loophole was technically closed is a direct consequence of people (like you?) misusing deSEC.

[d4708]

I just used self hosted DNS server, to provide dynamically generated peers IP in some decentralized platform. It requires this NS record as Bictoin legacy seeder implementation requires it (link above).

Also this service provided NS option those times. I have no idea what is going on here and loopholes you are talking about.

The answer about NS record not supported is enough for me, thanks.

[GenericUser]

Only subdomains of domains under dedyn.io can’t be delegated to other nameservers. It is a matter of policy. These domains are provided to be used for DNSSEC enabled dynamic DNS, not as free domains to be used somewhere else. It is not a technical limitation of the platform. You can delegate subdomains of your own domains that you host at Desec.