Skip to main content
Most issues on nxtdev.xyz fall into a handful of categories: claim errors, record rejections, delegation conflicts, and propagation delays. Work through the relevant section below to resolve your issue quickly.
The label you entered matches a blocked keyword pattern used to prevent phishing and impersonation. The system does not reveal which pattern matched to avoid gaming.Fix: Choose a different subdomain label. Avoid names that closely resemble well-known brands, services, or credential-harvesting terms. Legitimate project names are never blocked.
Another user has already claimed that label under nxtdev.xyz.Fix: Choose a different label. There is no waitlist or transfer mechanism for taken subdomains.
nxtdev.xyz checks every IP submitted for A and AAAA records against AbuseIPDB. If the IP carries a high abuse confidence score, the record is rejected to protect the shared namespace.Fix: Use a different server or IP address. If you believe your IP was flagged in error, contact your hosting provider — they can request removal from AbuseIPDB on your behalf. You can also check the score yourself at abuseipdb.com.
Nameserver delegation is active on your subdomain. While delegation is enabled, the nxtdev.xyz dashboard treats DNS records as read-only because an external nameserver is the authority.
1

Open the Nameservers tab

Go to your subdomain in the dashboard and navigate to the Nameservers tab.
2

Remove all delegated nameservers

Delete each NS record listed under your delegation configuration.
3

Return to DNS Records

Once delegation is removed, the DNS Records tab becomes editable and you can add or modify records normally.
Your subdomain has been suspended following a safety review. DNS changes are blocked while the suspension is active.Fix: Email support@nxtdev.xyz to appeal. Include your subdomain label and a brief description of what you are using it for. Suspensions are reviewed manually and are reversible for legitimate use cases.
The record has not resolved yet, or the content may be incorrect.
1

Wait 60 seconds and retry

Cloudflare propagates most changes in under 60 seconds. Run the propagation check again from your dashboard after waiting.
2

Verify the record content

Open the record in your dashboard and confirm the value is correct — for example, that a CNAME points to the right hostname and an A record contains a valid public IP.
3

Check the record host

Make sure you are querying the exact hostname the record is set for. For example, if the record host is api, you should be resolving api.yourname.nxtdev.xyz, not yourname.nxtdev.xyz.
You have reached the per-subdomain limit of 100 DNS records. No new records can be added until existing ones are removed.Fix: Review your records and delete any that are no longer needed. If you legitimately require more than 100 records, set up nameserver delegation and manage records with your own external DNS provider, which has no cap imposed by nxtdev.xyz.
If none of the above resolves your issue, contact the support team at help@nxtdev.xyz. Include your subdomain label, the action you were trying to perform, and any error message you received.