You only need one file for the zone komentari.info. In that file you put all hosts in that zone. No, need to use different files
Code:
$TTL 86400
@ IN SOA @ hexteam.gmail.com. (
42 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
IN NS ns1.komentari.info.
IN NS ns2.komentari.info.
ns1 IN A 208.84.149.210
ns2 IN A 208.84.151.35
komentari.info. IN A 208.84.149.210
I entered this file on my OpenBSD workstation and started named. The following command shows it is running/LISTENing
Code:
]netstat -an -f inet
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp 0 0 192.168.222.20.53 *.* LISTEN
tcp 0 0 127.0.0.1.53 *.* LISTEN
tcp 0 0 *.6000 *.* LISTEN
tcp 0 0 127.0.0.1.587 *.* LISTEN
tcp 0 0 127.0.0.1.25 *.* LISTEN
tcp 0 0 *.22 *.* LISTEN
tcp 0 0 *.515 *.* LISTEN
A non-recursive lookup (not starting at the [a-m].root-servers.net] results in the following
Code:
$ dig +norecurse -t ns komentari.info @127.0.0.1
; <<>> DiG 9.3.4 <<>> +norecurse -t ns komentari.info @127.0.0.1
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42956
;; flags: qr aa ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUESTION SECTION:
;komentari.info. IN NS
;; ANSWER SECTION:
komentari.info. 86400 IN NS ns1.komentari.info.
komentari.info. 86400 IN NS ns2.komentari.info.
;; ADDITIONAL SECTION:
ns1.komentari.info. 86400 IN A 208.84.149.210
ns2.komentari.info. 86400 IN A 208.84.151.35
A similar lookup for komentari.info
Code:
$ dig +norecurse komentari.info @127.0.0.1
; <<>> DiG 9.3.4 <<>> +norecurse komentari.info @127.0.0.1
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47363
;; flags: qr aa ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;komentari.info. IN A
;; ANSWER SECTION:
komentari.info. 86400 IN A 208.84.149.210
;; AUTHORITY SECTION:
komentari.info. 86400 IN NS ns1.komentari.info.
komentari.info. 86400 IN NS ns2.komentari.info.
;; ADDITIONAL SECTION:
ns1.komentari.info. 86400 IN A 208.84.149.210
ns2.komentari.info. 86400 IN A 208.84.151.35
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 27 03:03:42 2008
;; MSG SIZE rcvd: 116
You should get similar results with
dig +norecurse -t ns komentari.info. @208.84.149.210 and
dig +norecurse -t ns komentari.info. @208.84.151.35.
With those commands you can check whether the nameserver has been configured correctly.
The next problem is to make non-recursive queries working. In other words, recursive queries starting from the DNS root servers
Code:
]dig -t ns komentari.info.
; <<>> DiG 9.3.4 <<>> -t ns komentari.info.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23254
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;komentari.info. IN NS
;; ANSWER SECTION:
komentari.info. 11395 IN NS ns1.green-grupa.com.
komentari.info. 11395 IN NS ns2.green-grupa.com.
;; Query time: 1 msec
;; SERVER: 192.168.222.10#53(192.168.222.10)
;; WHEN: Tue May 27 03:28:24 2008
;; MSG SIZE rcvd: 83
This query is answered by by my local recursive nameserver 192.168.222.10.
As you can see it doesn't find yours
You have to contact your registrar for the
komentari.info zone and tell him that your nameservers are ns1 and ns2.komentari.info at addresses 208.84.149.210 and 208.84.151.35. They have to enter this information in the nameservers for the *.info top level domain.
After that is done, my and other recursive nameservers will find your nameservers at 208.84.149.210 and 208.84.151.35.