After reverse records and secondary zones, primary zones are now supported too. If you'd like, you can manage your domains' DNS records through vpsAdmin.
- In DNS → Primary zones, create a zone for your domain. The zone name is simply the domain name, usually a second-level domain, though you can delegate higher-level domains too.
- At your domain registrar, switch the nameservers to our shared servers. You'll find the assigned servers in the zone details, for example ns3.vpsfree.cz and ns4.vpsfree.cz.
- Then manage DNS records through the vpsAdmin interface.
We support these DNS record types: A, AAAA, CNAME, MX, NS, PTR, SRV and TXT.
Dynamic records
For A and AAAA records, you can generate a unique link that updates the record to the address the HTTP request came from when visited. This is useful if your home has a public address that isn't static and may change. Run wget/curl on your router from cron or in response to an address change to keep DNS records up to date.
DNSSEC
We support DNSSEC, but you need to pass the DNSKEY/DS record to the parent zone; check the procedure with your registrar. Enable DNSSEC in the zone details in vpsAdmin. Keys are generated and the zone signed automatically, using BIND's default policy. To view DNSKEY/DS records, click View DNSKEY and DS records in the zone details.
Your own secondary servers
You can run your own DNS server in a VPS as an additional secondary. Add it through the Secondary servers form in the zone details in vpsAdmin, which will then show an example configuration. Once it works, you can add it to the nameservers at your domain registrar.
Alternatively, use this to export records from our servers and import them into yours.
Summary
Want to run your own authoritative DNS server in a VPS and need a secondary? Use secondary zones in vpsAdmin.
If you want to manage DNS records through vpsAdmin, use primary zones.