Frequently Asked Questions

Yes, the service is completely free. You can create zones and manage records without any limitations.

All major types are supported: A, AAAA, CNAME, MX, TXT, PTR, SRV, NS, and SOA.

After creating a zone, set our NS servers in your domain settings at the registrar. Changes will take effect within a few hours.

Address groups allow you to associate multiple IP addresses with a single A or AAAA record, with load balancing and health monitoring. Supports health-aware resolution and fail-open.

You can configure HTTP, TCP, or ICMP probes for addresses in a group. Unhealthy addresses are automatically excluded from DNS responses.

Yes, for each zone you can enable AXFR/IXFR with delta format (RFC 1995 §4) and serial wrap-around (RFC 1982), and specify allowed IP addresses of secondary DNS servers.

Log in to your account and go to your profile. There you can change your password.

Yes. We offer a REST API with Bearer token authentication. You can manage zones, records, address groups, and health monitoring. API tokens are created through the web interface. See our API documentation for details.

Yes. Each zone can have up to 64 key-value labels (e.g. env:production, team:backend). Labels are visible on the dashboard and can be used to filter your zones.

Yes. The API supports atomic batch operations with CREATE, DELETE, and UPSERT actions. Batch requests are idempotent — use the Idempotency-Key header for safe retries.

Each token has configurable permissions (zones:read, records:edit, etc.) and optional scope restrictions. You can limit a token to specific zones or even individual records.

Yes. Wildcard records (*.example.com) are fully supported with RFC 4592 compliance, including CNAME chain following. If a wildcard CNAME points to an A record, the server follows the chain automatically.

Yes. You can disable a zone from the zone management page. All DNS responses for that zone will stop immediately. All records remain intact and are not deleted. Re-enabling restores DNS responses. If another zone with the same name exists, your zone will enter "Pending" status until ownership is verified.

Both zones can exist. The first zone gets standard NS servers and is immediately active. The second zone gets unique NS servers (e.g. 42.ns1.1bytedns.ru) and enters "Pending" status. Our verification service checks public DNS every minute — when you point your domain's NS to our servers at the registrar, the zone automatically becomes active.

No. NS records at the zone apex are system-managed and cannot be modified, deleted, or disabled. This ensures zone stability and correct DNS delegation. You can still create NS records at subdomains for zone delegation.

Pending zones that remain unverified for more than 30 days are automatically disabled. You can re-enable them at any time from the zone management page.

The delete button is on the zone management page (zone-edit.php), next to the enable/disable toggle. This keeps all zone actions in one place.

A tribute to PHP. The web interface is written in PHP because it works, it's simple, and it's been serving the web since 1995. Sometimes the best tool is the one that just gets the job done.

IXFR (Incremental Zone Transfer, RFC 1995) sends only the changes between two serial numbers, while AXFR sends the entire zone. This reduces bandwidth and speeds up synchronization for secondary DNS servers. Our server keeps a history of changes and sends them in RFC-compliant delta format. If history is unavailable, it falls back to AXFR.

No. IXFR and address groups are mutually exclusive. When IXFR is enabled for a zone, you cannot bind records to address groups, and vice versa. This is because grouped records store addresses in a separate table, which would corrupt the IXFR history. You need to choose one approach: either use address groups for load balancing, or use IXFR for efficient zone transfers.

Yes. The web interface is fully responsive and works on smartphones and tablets. Tables automatically switch to card view on small screens, navigation uses a hamburger menu, and all touch targets are optimized for touch interaction. No separate mobile app is needed.

Regular users cannot change MNAME — it is automatically set to ns1.1bytedns.ru. This ensures consistency and correct DNS delegation. Administrators can override MNAME per zone from the admin panel if needed.