Looking through the log files I see several errors that are causing you problems. Here are some examples:
You have a syntax error in your named.conf on or near line 66
Code:
Dec 23 14:39:05 test named: /etc/named.conf:66: missing ';' before 'internal'
Dec 23 14:39:05 test named: /etc/named.conf:66: open: /var/named/my.internal.zone.db
Dec 23 14:39:05 test named: };
Dec 23 14:39:05 test named: view : file not found
Dec 23 14:42:18 test named: /var/named/my.internal.zone.db:1: unknown option '@'
Dec 23 14:42:18 test named: /etc/named.conf:65: unexpected token near '}'
Another error in named.conf *note there are others, such as on line 14
Code:
/etc/named.conf:57: open: /var/named.root: file not found
Dec 23 14:25:53 test named: /var/named/named.root:2: '}' expected near ';'
Dec 23 14:28:41 test named: /etc/named.root:2: '}' expected near ';
Not really an error, but a possible indication your header isn't quite right
Code:
slaves/my.ddns.internal.zone.db:1: no TTL specified; using SOA MINTTL instead
Are you trying to run a master and slave server?
Code:
zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 127.0.0.1#53 (source 0.0.0.0#0)
Perhaps ok, but consider it a warning
Code:
zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 127.0.0.1#53 (source 0.0.0.0#0)
This makes it sounds like Bind may not be running as their is either a permissions problem or the port is still closed. I somewhat expect the errors on ipv6 addresses, but not on ipv4. You may have a permissions problem because there were some messages about /var/run (the pid) location. Make sure your permissions are set on the directory and the group/user (named) is set on bind.
Code:
connection refused resolving 'mirrors.ispros.com.bd/AAAA/IN': 192.5.5.241#53
Be careful with this one. I don't think want to run a PUBLICLY authoritative server, at least yet:
Code:
listening on IPv4 interface eth0, 200.200.200.114#53
Here are a couple of links to some DNS how-tos that I found very helpful. With these, I had bind up and running within a couple of hours after installing Ubuntu Server (command line only) on my first attempt.
Link1: How-To on Bind
Link2: Making bind work with DHCP for dynamic updates on your LAN