Does nslookup affect any network related files?

Does nslookup affect any network related files?

Post by Yi Qin (BCW P » Fri, 03 Jun 1994 02:15:03

Hello, netters.

This may relate to my problem I posted to this group early on.
To describe the problem again, I have everything running including
ping ( :-) ) after I install Consensys SVR4.2. But if I do nslookup,
the system command hangs. After I kill the nslookup command, I can
no longer ping again. (I had set up hosts and resolv.conf, btw.)

ping: hangs.
telnet: Cannot assign requested address.

In the next reboot, the Ethernet base I/O address checking was not
displayed. So I assusme some device table was corrupted, and pssibly
the system failed to make a device entry. ifconfig -a gives me nothing.
The system concerned is an Intel486 machine.

Please could anyone help me diagnose the cause of the problem. You
are welcome to email me discussing about more details of the problem.
Is there anything other files I need to touch when I set up TCP/IP,
to make it working stably. I don't run named on my machine. The nameserver
is pointed to in resolv.conf.


Yi Qin


1. Trying to look for Linux Networking files (Ethernet related), any Document available?

Networks experts: I need to add more debugging prints to understand
Networking stack in Linux, is there any document available about which
files are Network related files, also can I make it as Loadable module
instead part of Kernel. Thanks in advance.

In Linux, if I connect two Linux machines through Serial ports (COM),
can I able to communicate using some socket based application?.

2. MDK 8.1: No networking

3. repartitioning Linux --- will it affect DOS?

4. unix command to search a file

5. for 2.2.x i386 Linux kernel DoS - Affects 2.2.x and probably 2.0.x

6. Dell Insperion 3200 / 3com 3CX559 NIC-Modem

7. LILO affects DOS?

8. I am having trouble with tcpip

9. DOS virus affecting MBR&LILO

10. Reformatting/repartitioning DOS w/o affecting Linux-partition: Tips?

11. FW: i386 Linux kernel DoS - Affects 2.2.x and probably 2.0.x

12. Hard disk woes affect Linux, not DOS

13. doing backups that _do_ _not_ affect access time/date