topic Re: nslookup timed out in Operating System - HP-UX

nslookup timed out

ulisse lusuardi — Wed, 06 Dec 2000 15:24:05 GMT

My configuration:

I've a Workstation J280 with installed HP-UX 10.20 and the patch-bundle 'december 99'.Actually this WS is running as a standalone and I look out to insert it in a Network as a server.The LAN output is momentaneally connected to a Hub with a BNC T terminator with 2 resistances (50 ohm) connected.
I've configured the DHCP, the DNS ; the daemon "named" and "syslogd" are running.I've tested the syntax of nsswitch.conf with
'nslookup -swdebug' : the result is PARSE SUCCESSFUL.
The DNS server name is 'ms_fserv' and the IP addr is 193.72.242.149.
I've also defined a file /etc/resolv.conf.

My problem:

when try to use nslookup gives me the following errors:

***Can't find server name for address 193.72.242.149: Timed out
*** Default servers are not available
Using /etc/hosts on: ms_fserv

I can ping DNS server using IP address ; when I ping with the serve-name ('ping ms_fserv') I receive the corrected response only after 3 minutes.

What is the problem ?

Best regard
ulisse

Re: nslookup timed out

Kofi ARTHIABAH — Wed, 06 Dec 2000 15:33:56 GMT

Ulisse:

It would appear that the server that runs your dns (named or its equivalent) ie. ms_fserv is not running. In order to confirm, logon to ms_fserv and do a netstat -an and verify that you have a listening service on port 53.
If that works, verify that you can actually do an nslookup from ms_fserv - if that is an NT box, you might want to recycle it... NT's dns is not the most stable.

another thing you might want to check is that you have the correct netmask and broadcast addresses, default gateways, the usual.

also make sure that your /etc/nsswitch.conf contains something like:

hosts: files [NOTFOUND=continue] dns

Re: nslookup timed out

Rhonda Thorne — Thu, 07 Dec 2000 00:58:34 GMT

Ulisse:

When you do an nslookup on the client do ya get the error while using the name or the IP, or even both?

If you only get the error while using IPand not name(or vice versa), then the DNS db files are outta sink and you would want to run host_to_named from a validated /etc/hosts to recreate them.

You may want to verify your db. files to make sur ethey are ok.

Good luck

Re: nslookup timed out

Darrel Louis — Thu, 07 Dec 2000 12:08:06 GMT

Apart from checking the DNS database.
Can you also check the permissions on the files:
- /etc/resolv.conf
- /etc/nsswitch.conf
- /etc/hosts

Can you check with netstat if the Route Gateway is oke.

Re: nslookup timed out

ulisse lusuardi — Thu, 07 Dec 2000 14:53:15 GMT

I thank you very much for the rapide response.
Here I give you some complement of my problem: the hostname is "ms_fserv: and the DNS server is running on the same Workstation.
I've tested the service with 'netstat -an |grep 53' :I attach the result file and I send you also the 'named.data' files, the 'named.run',the'nsswitch.conf', the 'resolv.conf'and the result of different tests with 'nslookup'on a separatly email.

To Mr.Rhonda Thorne :I confirm that the result of nslookup is independent of ping: I've just given the command 'nslookup'.
'ping IPaddr' is another test that run correctly.
'ping 'servname' run currectly but i receive the first response on the console only after 3 minutes.

Generally: can you think that my problem is caused by the fact that I've no connection to other machine?

I think positiv for a solution.

With best regard I thank you very much.

ulisse

Re: nslookup timed out

Steve Massey_1 — Thu, 07 Dec 2000 15:44:30 GMT

Hi

have you checked that your forward and reverse dns files know of network 193.72.242 ??

What about
nslookup
set type=a
ls

what does this show ??

Steve

Re: nslookup timed out

ulisse lusuardi — Mon, 11 Dec 2000 09:55:18 GMT

Mr. Steve Massey,
I give you the result of the different command you have me proposed:
> nslookup
>> ***Can't find server for address 193.72.242.149: Timed out
>>*** Default server are not available
>> Using /etc/hosts on : ms_fserv
>set type=A
>> *** invalid option: type=A
> ls
>> Using /etc/hosts on : ms_fserv
>> looking up FILES
>> *** No Address Information is available for "ls"

I thank you very much and with best regard
ulisse

Re: nslookup timed out

Manuel P. Ron — Mon, 11 Dec 2000 13:05:27 GMT

Try with IP address 127.0.0.1. If your machine is standalone this IP address must work. Try two commands: 'ping 127.0.0.1' and 'nslookup 127.0.0.0'. What's happens? Thanks.

Re: nslookup timed out

Berlene Herren — Mon, 11 Dec 2000 13:58:04 GMT

Check the db file under /etc/named.data and make sure it is the correct IP address for this DNS server.

Berlene

Re: nslookup timed out

ulisse lusuardi — Mon, 11 Dec 2000 14:06:19 GMT

Mr. Manuel Perez Ron,
I've tried the 2 command that you have me suggested:
> ping 127.0.0.1 ==> run OK
>nslookup 127.0.0.1
>> *** Can't find server name for address 193.72.242.149: Timed out
>> *** Can't find server name for address 164.128.36.34: Timed out
>>*** Default server are not available
>> Using /etc/hosts on : ms_fserv
>> Looking up FILES
>> Name: localhost
>> Address: 127.0.0.1
>> Aliases: Loopback

With best regard
ulisse

Re: nslookup timed out

Manuel P. Ron — Mon, 11 Dec 2000 14:24:00 GMT

Well, now edit the /etc/resolv.conf and check the line with nameserver: change it to 'nameserver 127.0.0.1' and then restart DNS service with the command 'sig_named restart'. And now, what?
P.S: you have a trouble with IP address 193.72.242.149. It must ping even it's a standalone machine, I guess

Re: nslookup timed out

ulisse lusuardi — Mon, 11 Dec 2000 15:10:41 GMT

Mr. Manuel Perez Ron,
I've changed the file/etc/resolv.conf and restarted the DNS service .
Now with nslookup I receive:
>nslookup
>> Default Name server: Localhost
>> Address : 127.0.0.1

Other test with ping:
> ping 193.72.242.149 ==> run OK
>ping ms_fserv
>> ....after 3 Minutes I receive the correct
response.

What Problem with the originally IP Address from DNS server?
Bye later, Thanks ulisse

Re: nslookup timed out

Victor BERRIDGE — Mon, 11 Dec 2000 15:22:30 GMT

Hi Ulisse,
Have you checked your lan card configuration, I had a similar situation (netboot not nslookup) where ping was OK but the rest was dead slow, the card was on full duplex on a 10Mb bnc...

Good luck
Victor

Re: nslookup timed out

Manuel P. Ron — Tue, 12 Dec 2000 07:43:07 GMT

So, your DNS is right. Try, with (localhost as nameserver, like before) resolve your name (ms_fserv) and your IP address. Only must write the IP address or the name. in the prompt. If it works, really your problem is about your ThinEthernet Card

Re: nslookup timed out

ulisse lusuardi — Tue, 12 Dec 2000 09:50:17 GMT

Mr. Manuel Perez Ron,
I've changed the file/etc/resolv.conf and inserted "nameserver localhost"
After restart from nameserver I do the test:
>nslookup
>> ***Can't find server name for address 164.128.36.34 (*)
>> *** Default servers are not available
>> Using /etc/hosts on: ms_fserv

>ms_fserv
>> using /etc/hosts on: ms_fserv
>> looking up FILES
>> Name: ms_fserv
>> Address: 193.72.242.149

(*) 164.128...is not to consider: he is in resolv.conf for later applications.
I've verified the LAN Card configuration with SAM:
Card type: ETHERNET; Card Name : lan0;
HW Path : 8/12/6 ; Status : Enabled ;
IP : 193.72.242.149 ; Mask: 255.255.255.0
Default Gateway : 193.72.242.149;
Internet Broadcast Addr :193.72.242.255

The command "landiag -> lan -> display" give me no error.
Maybe other tests are necessary for the LAN card?

Your suggestions are very interessant.
Thanks
ulisse

Re: nslookup timed out

Kofi ARTHIABAH — Tue, 12 Dec 2000 13:18:52 GMT

Ulisse:

Your default gateway cannot be the same as your IP address! The default gateway should be the address of the next hop. By the way, is it possible that you have two machines with the same IP address on your network?

>I've verified the LAN Card configuration with >SAM:
>Card type: ETHERNET; Card Name : lan0;
>HW Path : 8/12/6 ; Status : Enabled ;
>IP : 193.72.242.149 ; Mask: 255.255.255.0
>Default Gateway : 193.72.242.149;
>Internet Broadcast Addr :193.72.242.255

log on to 193.72.242.149 and do a netstat -a | grep LISTEN and post the results. BTW you had mentioned earlier that you were posting some named data - it did not get attached so you might want to post it again.

Re: nslookup timed out

Manuel P. Ron — Tue, 12 Dec 2000 14:23:36 GMT

We are going backwards, ulisse... If you change 'nameserver 127.0.0.1' and all is right, why 'nameserver localhost' says address 164.128.36.34???. And, it's more, you must use IP address in the resolv.conf (see man). You must configure a nameserver with IP address, not names (it's not a meta-nameserver)
P.S: What is 164.128.36.34?

Re: nslookup timed out

ulisse lusuardi — Tue, 12 Dec 2000 15:01:33 GMT

Mr. Kofi Arthiabah,
here attached the result of: netstat -a |grep LISTEN
I have only one standalone machine: in moment is no NETWORK connection. See my first message
under "My configuration".
The named.data files follows.

With best regards
ulisse

Re: nslookup timed out

ulisse lusuardi — Tue, 12 Dec 2000 15:05:34 GMT

Mr. Kofi Arthiabah,
here attached the db.mecasoft

Re: nslookup timed out

ulisse lusuardi — Tue, 12 Dec 2000 15:08:33 GMT

Mr. Kofi Arthiabah,
here attached the db.193.72.242