We have noticed that our new users are finding hard to migrate their configuration files to our Lua zone file format, to solve this issue we've decided to add native support for Bind zone files to our service.
How does it work?
Bind zone files can be easily deployed to our name servers with Git in the same way as Lua zone files.
Users have the option to store their configurations in standard Bind format or to use more powerful Lua format. Bind zone files can be mixed with Lua zone files in the same Git repository (Lua files have higher priority).
To get started, follow previous post
to setup your Git repository. Add your Bind files to repository using .bind
extension (Example: mydomain.com.bind) and push your modifications with
git push origin master.
git push command, shortly you'll receive an email with the status of the deployment.
Example Bind zone:
; File: example.org.bind ; Zone: example.org ; Default origin is computed from the file name, ; you may change the origin with $ORIGIN directive ; Example: ; $ORIGIN example.org. ; Default TTL is account's [default TTL](https://api.luadns.com/settings), ; you may change the default TTL with $TTL directive ; Example: ; $TTL 3600 ; 1 hour ; The system will generate and maintain domain's SOA record automatically, ; SOA records found in *.bind files are simply ignored example.org. IN SOA ns1.bind.net. hostmaster.bind.net. ( 2012050901 ; serial 20m ; refresh (20 minutes) 2m ; retry (2 minutes) 1w ; expire (1 week) 1h ; minimum (1 hour) ) ; Domain NS records are replaced with system name servers NS ns1.bind.net. NS ns2.bind.net. NS ns3.bind.net. NS ns4.bind.net. ; The rest of records @ A 220.127.116.11 @ MX 5 aspmx.l.google.com. www CNAME example.org. mail CNAME ghs.google.com. ; SPF record, see http://www.openspf.org/ @ TXT "v=spf1 a mx include:_spf.google.com ~all" ; SIP service available at the host sip.example.com _sip._udp SRV 0 0 5060 sip.example.com.