On Thu, Jun 24, 2010 at 08:16:05AM +0000, Kossi TEPE wrote:
> zone "[11]univ-lome.tg"{
> type master;
> allow-update {none;};
> file "/var/named/data/ulhostext";
> allow-transfer { 80.248.64.3;};
> };
>From here, it looks like you don't have delegation from above (.tg)
$ dig univ-lome.tg. ns
...
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37072
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
^^^^^^^^^
;; QUESTION SECTION:
;univ-lome.tg. IN NS
;; AUTHORITY SECTION:
tg. 3586 IN SOA tld.cafe.tg. kido.cafe.tg.
2010061801 21600 3600 604800 86400
That is: no NS records found, so no way to locate your nameservers.
Strangely, querying the authoritative server directly (tld.cafe.tg) doesn't
give an NXDOMAIN, but a NOERROR with 0 records. Compare output of these two
commands:
$ dig @tld.cafe.tg. univ-lome.tg. ns # NOERROR, ANSWER: 0
$ dig @tld.cafe.tg. univ-lomezzzz.tg. ns # NXDOMAIN
However, if I query your ns1 directly, it works:
$ dig @41.207.188.27 www.univ-lome.tg. a # get the data
although I get no response from this one:
$ dig @41.207.188.30 www.univ-lome.tg. a # timeout
So it looks like a delegation issue, rather than an error with the setup of
your nameserver. Talk to your TLD administrator about how best to resolve
this (pun not intended).
HTH,
Brian.