NSLOOKUP can't find server but DNS is fine...

[Willem Grooters]

Another thing I ran into I can't figure out.

My VMS box is (authorative)dns server for the local network. It's behind a router/firewall that will handle requests it cannot handle. In the firewall log I can see these requests.
Within the network there not any trouble locating and accessing remote systems, so DNS works.
But NSLOOK up doesn't:

$ nslookup
*** Can't find server name for address 192.168.0.2: Server failed
*** Default servers are not available

but this isn't true (I think):

tcpip sho host

LOCAL database

Host address Host name

192.168.0.2 DIANA.INTRA.mynet.NL, DIANA
127.0.0.1 LOCALHOST
192.168.0.30 charon.intra.mynet.nl

BIND database

Server: 192.168.0.2 DIANA.INTRA.MYNET.NL

Host address Host name

192.168.0.195 athene.INTRA.MYNET.NL
192.168.0.30 charon.INTRA.MYNET.NL
192.168.0.200 cl_grooters.INTRA.MYNET.NL
192.168.0.2 diana.INTRA.MYNET.NL
192.168.0.13 extranet.INTRA.MYNET.NL
192.168.0.3 hera.INTRA.MYNET.NL
192.168.0.11 intranet.INTRA.MYNET.NL
192.168.0.12 javadoc.INTRA.MYNET.NL
192.168.0.193 mars.INTRA.MYNET.NL
192.168.0.196 venus.INTRA.MYNET.NL

BTW: Diana is the VMS machine, Charon the router.

Why can't I use nslookup....

tcpip sho config name/full
--------------------------

BIND Resolver Configuration

Transport: UDP
Domain: INTRA.MYNET.NL
Retry: 4
Timeout: 4
Servers: DIANA.INTRA.MYNET.NL
Path: No values defined

Options in BIND.CONF:
--------------------
options {
directory "SMAN:[DIANA.CONF.BIND]";
// query-source address * port * ;
forwarders {
192.168.0.30 ;
} ;
forward first ;
};

(Don't try to find MYNET.NL, if you find it, it isn't me ;-D)

[Martin P.J. Zinser]

Hello Willem,

not sure if this is the case here, but...
I have seen similar strange error situation if the local host name (DIANA) was not both in UPPER >>and<< lowercase in the hosts database. Should be an easy test...

Greetings, Martin

[Christopher Rupnik · Accepted solution]

Hi
To me, this is a DNS problem, not a VMS problem. Are you sure you have a reverse lookup file that specifies what 192.168.0.2 is?

in your bind.conf

zone "0.168.192.IN-ADDR.ARPA" {
type master;
file "db.192.168.0";
};

file db.192.168.0

2 IN PTR DIANA.INTRA.mynet.NL.

[Willem Grooters]

Putting hostname in lowercase didn't work - same problem.
It indeed were DNS settings. In the forward references (my.domain.db) I found a NS specified that's no DNS-server anymore. Removed that and restarted BIND. That did the trick.(Was changes somehere begin August, just after I came back from holiday. That migh be the reason it slipped...
Thanx guys, you earned your points.