This is probablly not so much system administration related, but I'd be
gratefull for any help. At least - where to ask for named problems :)
I've got:
AlphaServer 300, Dunix 4.0b, with duv40bas00007-19980514 patch.
On this Alpha, I run a secondary nameserver for my pliva.hr domain.
Primary nameserver (on another Alpha of course), for my domain, works
nicely, queried for anything, from anywhere (at least, that's what it
looks like to me). Some time ago everything looked ok on this, secondary
one. When I checked recently I've seen problems....
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
2.208.29.195.in-addr.arpa from [161.53.62.3].53
Oct 21 16:35:39 internet named[180]: Unauthorized request pliva.hr from
[157.193.40.37].53
Oct 21 16:36:21 internet named[180]: Unauthorized request pliva.hr from
[131.246.9.116].53
Oct 21 16:39:14 internet named[180]: Unauthorized request
2.208.29.195.in-addr.arpa from [208.131.123.10].53
.....
It seems to me that named boot file is perfectly ok, as well as hosts
and reverse file.
What's going on, what kind of authorisation is missing? What could I
have done wrong?
Thank you gurus,
Hana Breyer Priselac
hana_at_pliva.hr
system engineer
Pliva
Received on Thu Oct 22 1998 - 10:31:08 NZDT