resolv.conf problems
I mistyped my DNS ip address when setting up networking here. I fixed resolv.conf to reflect the actual ip. Here's the problem: after a boot, names don't resolve. If I su to root and take down the network and restart it (via /etc/inet.d/network down, then /etc/inet.d/network up) then it works. Does someone know how to fix this? I do not want to do the poor mickey mouse solution of adding those 2 commands to some startup script; I'd rather understand what's going on in my system. Thanks --- Daniel Hollis adzuki @ cs.dartmouth.edu Dartmouth College
Re: resolv.conf problems
On Tue, 12 Jan 1999 [EMAIL PROTECTED] wrote: I mistyped my DNS ip address when setting up networking here. I fixed resolv.conf to reflect the actual ip. Here's the problem: after a boot, names don't resolve. If I su to root and take down the network and restart it (via /etc/inet.d/network down, then /etc/inet.d/network up) then it works. Does someone know how to fix this? I do not want to do the poor mickey mouse solution of adding those 2 commands to some startup script; I'd rather understand what's going on in my system. I don't understand the problem. The IP address of your machine should occur in two places: /etc/hosts and /etc/init.d/network. The /etc/hosts entry should have the proper host name to IP address mapping. The /etc/init.d/network contains only the IP address/netmask, etc. information so your network interface(s) can be configured at boot time. /etc/resolv.conf doesn't contain your machine's IP address, it should be the IP address of the nameserver(s) that are providing DNS service to your machine. If your machine is at home, then most probably the DNS server is provided by your ISP. If your machine is at work/school, then your DNS server is on their network and is administered by your IT/MIS people. The DNS server's IP address should be in /etc/resolve.conf. They should have assigned you an IP address and host name which should go in /etc/hosts. The IP address/netmask info should also be in /etc/init.d/network. Hope this helps...
Re: resolv.conf problems
Hi, Daniel! It's indeed is a strange problem. You may try a few things: 1. One you boot, can you ping computer on the same local network, just using it's numerical IP address? 2. Can you ping computer outside of your local network using it's numerical IP address? 3. Can you ping DNS server using it's numerical IP address? This way you can check that your network card is initialized and your gateways and local network are configured right. My thought here (likely to be wrong) is that it could be the case that somehow your /etc/inet.d/network is called before your network hardware is actually initialized. Have a look in boot messages. Sasha. I mistyped my DNS ip address when setting up networking here. I fixed resolv.conf to reflect the actual ip. Here's the problem: after a boot, names don't resolve. If I su to root and take down the network and restart it (via /etc/inet.d/network down, then /etc/inet.d/network up) then it works. Does someone know how to fix this? I do not want to do the poor mickey mouse solution of adding those 2 commands to some startup script; I'd rather understand what's going on in my system. Thanks
