root@ubuntu:/home/hthh# sudo apt-get install bind9
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  resolvconf
The following NEW packages will be installed:
  bind9
0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Need to get 0B/268kB of archives.
After this operation, 762kB of additional disk space will be used.
Selecting previously deselected package bind9.
(Reading database ... 31778 files and directories currently installed.)
Unpacking bind9 (from .../bind9_1%3a9.4.2.dfsg.P2-2_i386.deb) ...
Setting up bind9 (1:9.4.2.dfsg.P2-2) ...
[color=red]Reloading AppArmor profiles AppArmor parser error in 
/etc/apparmor.d/usr.sbin.named at line 4: syntax error, unexpected TOK_MODE, expecting TOK_OPEN
Profile /etc/apparmor.d/usr.sbin.named failed to load[/color]
: Failed.
invoke-rc.d: initscript apparmor, action "force-reload" failed.
 * Starting domain name service... bind                                  [fail]

root@ubuntu:/home/hthh# cat /etc/apparmor.d/usr.sbin.named
 # See /usr/share/doc/bind9/README.Debian.gz
  /var/lib/named/etc/bind/* rw,

  /etc/bind/** r,
  /var/lib/bind/** rw,
  /var/lib/bind/ rw,
  /var/cache/bind/** rw,
  /var/cache/bind/ rw,
  /var/lib/named/var/run/bind/run/named.pid w,
  # /var/run/bind/run/named.pid w,
  # some people like to put logs in /var/log/named/
  /var/log/named/** rw,
# support for resolvconf
  /var/lib/named/var/run/bind/named.options r,
  # /var/run/bind/named.options r,

  # dnscvsutil package
  /var/lib/dnscvsutil/compiled/** rw,
# add also following lines thanks to Spezi2u
  /var/lib/named/dev/null rw,
  /var/lib/named/dev/random rw,

  /proc/net/if_inet6 r,
  /usr/sbin/named mr,
  /var/run/bind/run/named.pid w,
}

root@usrv:/etc/bind# cat named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
        type hint;
        file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
        type master;
        file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
};

include "/etc/bind/named.conf.local";

root@usrv:/etc/bind# cat named.conf.options
options {
        directory "/var/cache/bind";

        // If there is a firewall between you and nameservers you want
        // to talk to, you might need to uncomment the query-source
        // directive below.  Previous versions of BIND always asked
        // questions using port 53, but BIND 8.1 and later use an unprivileged
        // port by default.

        // query-source address * port 53;

        // If your ISP provided one or more IP addresses for stable
        // nameservers, you probably want to use them as forwarders.
        // Uncomment the following block, and insert the addresses replacing
        // the all-0's placeholder.

forwarders {
203.162.4.191;
203.162.4.190;
};
        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };
};

root@usrv:/etc/bind# cat named.conf.local
//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "hthhnguyen.com" {
type master;
file "/etc/bind/db.hthhnguyen.com";
};

zone "132.195.10.in-addr.arpa" {
type master;
notify no;
file "/etc/bind/db.10";
};[/b][/color]

logging {
        channel query.log {
                file "/var/log/query.log";
                severity debug 3;
        };
        category queries { query.log; };
};

logging {
        channel query.log {
                file "/var/log/query.log";
                severity debug 3;
        };
        category queries {query.log};
};