Many thanks go to
Keith C. Barth (barthkei_at_aquinas.edu)
Dejan Muhamedagic (dejan_at_yunix.co.yu)
especially to Dejan Muhamedagic, who pointed me into right direction.
The solution:
Correct in a way that makes sense, or completely remove, the secure_zone
record in hosts database file. The secure_zone record says which hosts
are allowed to do queries - all other are considered unauthorized. As
for me - I had it set on primary DNS so that it serves only localhost
(yes, all other were unauthorized). Once that was fixed, all other works
nicely.
The original question:
....
> This, secondary nameserver behaves like this:
> A nslookup for anything, done localy, works just fine.
>
> A nslookup from any other domain gives an correct answer for hosts > it's
> not authorative for, but for hosts in my domain, the answer looks > like:
>
> > router.pliva.hr
> Server: internet.pliva.hr
> Address: 195.29.208.3
>
> *** internet.pliva.hr can't find router.pliva.hr: Non-existent
> host/domain
>
> The syslog says:
> Oct 21 16:32:53 internet named[180]: Unauthorized request
> internet.pliva.hr from [161.53.62.3].53
>
> What's going on, what kind of authorisation is missing? What could I
> have done wrong?
That's it,
Hana Breyer Priselac
hana_at_pliva.hr
system engineer
Pliva
Received on Fri Oct 23 1998 - 10:12:48 NZDT