I am a teacher at an IT vocational school and would like to provide my students with a public domain. Your platform would be ideal for this.
Unfortunately, I am encountering a problem with AWS: EC2 IP addresses cannot be registered with you. I am aware that you do not allow classic static IPs. However, the public IPs automatically assigned by AWS are static too, but changing when the instance is stopped or started, and are therefore virtually dynamic in practice.
Is there a solution for this scenario, or is your service fundamentally unsuitable in combination with AWS? Other ideas to get free managable domain names?
The purpose of the .dedyn.io service is not to provide free domains for general purposes (dynamic or non-dynamic IP addresses), but for residential users. This limitation is in place because we’ve had to deal with a large number of .dedyn.io domains hosting abusive content, which both causes very (!) high support load for takedowns and strains our infrastructure. As a result, A records relating to non-residential IPv4 blocks from which we’ve observed abuse cannot be created under .dedyn.io:
Although this policy is in place for AAAA records on paper, we have not observed IPv6 abuse so far. Until that changes, you may use .dedyn.io domains with your students and at the same time teach them about IPv6.
Cool idea! So, theoretically, students can create a subdomain (sub.m158.dedyn.io), which is managed (NS records) via their own DNS (Ubuntu bind9) server?
To do this, we would simply create AAAA glue records pointing to the AWS Ubuntu bind9 machine and add some NS records for the managed subdomain, right? many thanks again!
Sorry, but I don’t think that’s accurate. Subdomains of dedyn.io, even one level deeper than the directly delegated domains, can’t be delegated to other nameservers. Desec won’t let you set NS records for those domains, no way, no how. This can be done with managed domains, i.e. domains that are delegated to the Desec nameservers from outside. You can get your own domain elsewhere and delegate subdomains of that to the Desec account(s) that students use and then your students can delegate sub-subdomains to their own nameservers. At that point, hosting your own instance of the Desec stack may be easier.
I’ve submitted a pull request that allows flagging domains as allowed for delegation instead of making it only dependent on the dedyn.io status. If merged, deSEC support could allow your domain may be delegated.
