Hi Agus,

The problem you encounter may comes from your Bind configuration between ns1 and ns2, as it seems ns2 did receive any copy of your DNS zone file.

dig pusatwebhosting.com soa @ns1.pusatwebhosting.com +short
ns1.pusatwebhosting.com. postmaster.pusatwebhosting.com. 2014090430 21600 3600 604800 86400

This successfull replies shows the ns1 server manages the DNS zone file with serial 2014090430.

dig pusatwebhosting.com soa @ns2pusatwebhosting.com +short
--> empty response

This error response shows that the ns2 server did not receive the transfer of the zone file by master DNS.

Let's assume ns1 is your master, and ns2 is your slave. The zone file transfer information need to be retrieved in both bind service configuration, with particular directives for slave or master.

On master (example) :

--> In named.conf.local
 zone "pusatwebhosting.com" {
             type master;
             file "/etc/bind/db.pusatwebhosting.com";             
             allow-transfer { @slave_ip; };
        };

On slave (example)

--> In named.conf.local
 zone "pusatwebhosting.com" {
             type slave;
             file "/etc/bind/db.pusatwebhosting.com";             
             masters { @master_ip; };
        };

With this configuration based on master/slave, you should be able to notify your slave for the zone transfer, and the file will be automatically created in /etc/bind/db.pusatwebhosting.com on your slave.

At this point, your web tool should show a successfull test ;)

Let us know if it worked,

Regards,

--
rustx