Fast DNS management Β· Apex ALIAS Β· REST API Β· Generous limits Β· No unnecessary complexity
DNS infrastructure without the usual artificial limits.
Host your zones, manage records from a clean control panel, automate everything through the API, and use apex ALIAS records when your provider gives you a hostname instead of an IP.
Most DNS hosting platforms are designed around simple record editing. Intent-DNS is designed with developers and infrastructure workflows in mind.
| Intent-DNS | |
|---|---|
| π Authoritative DNS | PowerDNS-based |
| β‘ Apex ALIAS | Yes |
| π REST API | API v1 |
| π¦ Free plan | 20 domains Γ 1,000 records/domain |
| π³ Paid plan | 100 domains Γ 1,000 records/domain β $1 |
| βΎοΈ Unlimited plan | Unlimited domains Γ unlimited records β $4 |
| π DNS discovery | Built in |
| π API authentication | Bearer tokens |
| π₯οΈ Web panel | Included |
Open the Intent-DNS control panel:
Create an account and start with the Free plan.
From the dashboard, add a domain and configure its DNS records.
You can either create records manually or use DNS discovery/import to find existing records.
Set your domain's authoritative nameservers to:
dns1.int.yt
dns2.int.yt
Always use the exact nameservers shown by the Intent-DNS panel if your account displays different values.
dig example.com
dig @dns1.int.yt example.com
dig @dns2.int.yt example.comChoose the amount of DNS infrastructure you actually need.
|
20 domains 1,000 records / domain
|
100 domains 1,000 records / domain
Contact us β admin@int.yt |
Unlimited domains Unlimited records
Contact us β admin@int.yt |
Email: admin@int.yt
Discord: https://discord.gg/NCS96PS4MH
Discord is recommended for faster replies.
One of the core Intent-DNS features is apex/root-domain ALIAS support.
Normally, DNS does not allow a standard CNAME at the zone apex:
example.com β CNAME β service.example.com
Intent-DNS supports:
@ β ALIAS β service.example.com.
This is particularly useful when a hosting platform gives you a hostname such as:
your-project.provider.example
but you want:
example.com
to point to it.
example.com
β
βΌ
@ ALIAS your-project.onrender.com.
β
βΌ
Intent-DNS resolves the target
β
βΌ
Address response returned to the client
Intent-DNS protects zones from invalid ALIAS combinations, including:
- β ALIAS + A at the same owner name
- β ALIAS + AAAA at the same owner name
- β ALIAS + CNAME at the same owner name
- β Multiple ALIAS targets at the same owner name
- β Self-referential ALIAS targets
Appropriate records such as NS, SOA, MX, TXT, SRV and CAA can coexist where valid.
βββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β Type β Purpose β
βββββββββββΌβββββββββββββββββββββββββββββββββββββββ€
β A β IPv4 address β
β AAAA β IPv6 address β
β CNAME β Canonical hostname β
β ALIAS β Apex hostname / DNS flattening β
β MX β Mail exchange β
β TXT β Text / verification / policy data β
β NS β Nameserver delegation β
β SRV β Service discovery β
β CAA β Certificate authority policy β
βββββββββββ΄βββββββββββββββββββββββββββββββββββββββ
@ A 203.0.113.10
www A 203.0.113.10
@ ALIAS service.example.com.
@ MX 10 mail.example.com.
@ TXT "v=spf1 ..."
_service._tcp SRV 10 5 443 service.example.com.
@ CAA 0 issue "letsencrypt.org"
Automate your DNS infrastructure instead of clicking through a dashboard.
Base API:
https://dns.int.yt/api/v1/
Authentication uses Bearer API tokens.
Authorization: Bearer idns_live_YOUR_TOKENPOST /api/v1/auth/tokenGET /api/v1/userGET /api/v1/domains
POST /api/v1/domains
GET /api/v1/domains/{id}
DELETE /api/v1/domains/{id}GET /api/v1/domains/{id}/records
POST /api/v1/domains/{id}/records
PUT /api/v1/domains/{id}/records/{record_id}
DELETE /api/v1/domains/{id}/records/{record_id}curl https://dns.int.yt/api/v1/domains \
-H "Authorization: Bearer idns_live_YOUR_TOKEN"Create a record:
curl -X POST \
https://dns.int.yt/api/v1/domains/DOMAIN_ID/records \
-H "Authorization: Bearer idns_live_YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "www",
"type": "A",
"content": "203.0.113.10"
}'Check the project's API documentation for the exact request and response schemas.
Already have DNS records somewhere else?
Intent-DNS can discover existing records before creating a zone.
βββββββββββββββββββββ
β Enter domain β
βββββββββββ¬ββββββββββ
βΌ
βββββββββββββββββββββ
β DNS discovery β
βββββββββββ¬ββββββββββ
βΌ
βββββββββββββββββββββ
β Review records β
βββββββββββ¬ββββββββββ
βΌ
βββββββββββββββββββββ
β Select records β
βββββββββββ¬ββββββββββ
βΌ
βββββββββββββββββββββ
β Create zone β
βββββββββββ¬ββββββββββ
βΌ
βββββββββββββββββββββ
β Sync to PowerDNS β
βββββββββββββββββββββ
This makes migration from an existing DNS provider significantly easier.
Intent-DNS uses a PowerDNS-based authoritative DNS architecture.
INTERNET
β
DNS queries / delegation
β
βΌ
βββββββββββββββββββββββ
β Intent-DNS β
β Authoritative DNS β
ββββββββββββ¬βββββββββββ
β
βββββββββββββ΄ββββββββββββ
βΌ βΌ
βββββββββββββββββ βββββββββββββββββ
β dns1.int.yt β β dns2.int.yt β
βββββββββ¬ββββββββ βββββββββ¬ββββββββ
β β
βββββββββββββ¬ββββββββββββ
βΌ
βββββββββββββββββββββββ
β PowerDNS Authoritativeβ
ββββββββββββ¬βββββββββββ
β
βΌ
βββββββββββββββββββββββ
β PowerDNS Recursor β
β ALIAS / flattening β
βββββββββββββββββββββββ
Nginx
β
βββ PHP-FPM
β βββ Intent-DNS application
β
βββ HTTPS / web routing
MariaDB
βββ Users, domains, records, plans, audit data
PowerDNS Authoritative
βββ Authoritative DNS zones
PowerDNS Recursor
βββ Recursive resolution used by ALIAS handling
Intent-DNS separates normal users, staff, and administrators.
Users can manage:
- Their own account
- Their permitted domains
- DNS records within their quotas
- API keys where enabled
Staff can manage normal customer resources according to their permissions.
Staff cannot:
- Access administrator-only functions
- Create or modify administrator accounts
- Grant paid/unlimited privileges
- Change administrator-controlled quotas
Production administrator privileges are reserved for the designated administrator accounts.
Administrators can manage:
- Users
- Staff
- Domains
- DNS records
- Plans
- Quotas
- API access
- Announcements
- Administrative settings
- Audit information
Normal signup cannot create an administrator account.
The plan system separates roles from plan capabilities.
Account role
β
βββ User
βββ Staff
βββ Administrator
Plan
β
βββ Free
βββ Paid
βββ Unlimited
Resource controls include:
max_domains
max_records_per_domain
api_enabled
This structure allows future billing/payment integrations without replacing the authorization model.
The Intent-DNS panel provides a complete web interface for DNS management.
- π Dashboard
- π Domain management
- π§Ύ DNS record management
- π DNS discovery/import
- π€ Profile management
- π Password management
- π API key management
- π API documentation
- π οΈ Staff portal
- π Administrator portal
- π’ Announcements
- π Audit information
- π Quota/plan information
- π± Responsive navigation
β οΈ Validation and error feedback- β Success notifications
- β³ Loading states
The production implementation includes testing around:
- User signup/login/logout
- Password and session handling
- CSRF protection
- Administrator restrictions
- Staff lifecycle
- User/staff/admin authorization boundaries
- API token generation
- Authenticated API requests
- Domain CRUD
- DNS record CRUD
- A
- AAAA
- CNAME
- ALIAS
- MX
- TXT
- SRV
- CAA
- Apex ALIAS resolution
- PowerDNS synchronization
- Authoritative DNS resolution
- DNS discovery
- Discovery token handling
- Record selection
- Zone creation
- Database persistence
- PowerDNS synchronization
- Real DNS resolution
Nginx
PHP-FPM
MariaDB
PowerDNS Authoritative
PowerDNS Recursor
| Layer | Technology |
|---|---|
| Backend | PHP |
| Database | MariaDB |
| Authoritative DNS | PowerDNS Authoritative |
| Resolver | PowerDNS Recursor |
| Web server | Nginx |
| Runtime | PHP-FPM |
| API | REST API v1 |
| Frontend | JavaScript / CSS |
| UI | CoreUI-style interface |
Check your authoritative nameservers:
dig NS example.comQuery a specific Intent-DNS nameserver:
dig @dns1.int.yt example.comdig @dns2.int.yt example.comCheck an individual record:
dig A example.com
dig AAAA example.com
dig MX example.com
dig TXT example.comFor ALIAS:
dig example.comIf a nameserver change was made recently, remember that delegation and cached DNS responses can take time to update.
Contributions, bug reports, feature ideas, and infrastructure improvements are welcome.
Please include:
- What you expected
- What actually happened
- Relevant DNS output
- Relevant API response
- Steps to reproduce
- Environment information where useful
Never include:
- Passwords
- API tokens
- Private keys
- Session cookies
- Other credentials
Intent-DNS is intended for legitimate DNS hosting and infrastructure use.
Users are responsible for the domains and records they operate through the service.
Abuse, malicious activity, spam, phishing, or other prohibited activity may result in restrictions or account termination.
| π Website | https://dns.int.yt/ |
| βοΈ Control Panel | https://panel.dns.int.yt/ |
| π§ Email | admin@int.yt |
| π¬ Discord | https://discord.gg/NCS96PS4MH |
Discord is recommended for faster replies.
Star the repository and help more developers discover it.
π Visit Website Β· βοΈ Open Control Panel Β· π¬ Join Discord
Intent-DNS β DNS infrastructure built for developers.
Add the project's chosen open-source license here once the licensing decision has been made (for example, MIT, Apache-2.0, or GPL-3.0).