The update is done by generating configuration- and zone files based on the information in the database. The strengths of Pro BIND are: This page has two sections, separated by a horizontal bar. ( 2001062501 ; serial 21600 ; refresh after 6 hours 3600 ; retry after 1 hour 604800 ; expire after 1 week 86400 ) ; minimum TTL of 1 day ; @ IN NS dns1. This fact is even more important if you pay for your own VPS server.Another DNS nameservers available on a Linux systems are NSD ( Name Server Daemon) or djbdns ( tinydns ).However, even when you use a tool, it is critical to know what goes on when the files are updated, so we'll start with the manual method.
The database contents are pushed onto the DNS servers only when a Pro BIND user explicitly requests it (it is also possible to execute the update from a cron job).
Navigate to /etc/bind/ directory execute following sequence of commands to navigate to zones/master//etc/bind/zones/master directory will contain a zone file for a domain. IN A 192.168.0.10 ns1 IN A 192.168.0.10 ns2 IN A 192.168.0.11 www IN CNAME At this stage the bind DNS server can resolve an IP address mapped to a host. Alternatively if you are google fan use 220.127.116.11 or 18.104.22.168.
Pro BIND is an application for managing DNS servers.
Slave name servers will load this new data sometime within the time interval defined in the SOA record for refreshing their data.
Sometimes your users won't want to wait for the slaves to pick up the new zone data -- they'll want it available right away.