I have problem adding domain to deSEC

Hello, I am the owner of the domain is-app.top, I am planning to move to deSEC to host my domain, but I am facing a problem here is the error “This domain name conflicts with an existing domain, or is disallowed by policy.” even though I have never used my domain with deSEC. Hopefully I will get some help to fix this.

Best regards,
Min YoonGi

Not sure what is going on here.

One theory: Someone created the zone is-app.top at deSEC. But since they are not the owner they can’t delegate the domain and can’t set up DNSSEC. However this might prevent you from creating the zone. However dig @ns1.desec.io is-app.top soa does not return an answer so the problem may be something else.

Contact deSEC support and be prepared to prove domain ownership.

HTH
fiwswe

1 Like

“is-app.top” is a free subdomain provider. I assume that someone has a subdomain of that domain hosted at Desec. It could also be an actual policy problem to host a public DNS suffix at Desec. Unlike dedyn.io, the is-app.top domain is not yet listed as a public suffix though. It would most certainly be a bad fit, not least because of the rate limits.

1 Like

I have contacted but no one has responded to me

I tried but PSL team does not allow to put this domain in that list

This is a non-profit organisation and a free service. You don’t get SLAs here. Be patient.

Just to satisfy my curiosity:

  • What does “PSL” stand for?
  • And what list are you talking about?
1 Like

public suffix list

https://publicsuffix.org/

That list would be completely irrelevant for delegating a domain to deSEC.

However if what @GenericUser mentioned is true, that users can register subdomains of is-app.top, then the services of deSEC are probably not for you. At least I don’t think deSEC intends to provide free services to domain registries.

You’d be better off building your own DNS services, possibly based on the Open Source code deSEC uses.

1 Like

Being listed as a public suffix could preclude a domain from being hosted at Desec, as a matter of policy, but since the domain isn’t (yet) listed, that doesn’t seem to be the problem.

1 Like

Agreed! :slightly_smiling_face: