- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: resolv.conf
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 08:56 AM
тАО09-16-2002 08:56 AM
I have configured resolv.conf, nsswitch.conf and /etc/hosts the same as other machines I have running. I can't get get this new install to resolve to our dns machine. For example: when I try to ping a host on a different network, the command just hangs. My other HPUX hosts resolve just fine with these same configurations. I may be overlooking something very basic.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 08:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 09:14 AM
тАО09-16-2002 09:14 AM
Re: resolv.conf
can you ping your own system with
#1: ping 127.0.0.1
# then TCP/IP is not bad
#2: ping DEFAULT-ROUTER # enter your default-router's IP-address here
# then your LAN-cards does work
#3: ping DNS-SERVER # enter DNS-server's IP-address here
# then your DNS-server is reachable
can you reach your DNS-server with
#4: nslookup $(hostname)
# then it answers
#5: nslookup www.your.company.com # or whatever a station in your domain is
#6: traceroute DNS-server # as in #3
Just tell us the output of these commands.
Regards,
Wodisch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 09:38 AM
тАО09-16-2002 09:38 AM
Re: resolv.conf
Just a few checks before you start changing things.
1) Have you registered your new system's IP address with your DNS subsystem. Many times, we forget registering our DNS entry.
2) If you have done this, verify that you are able to do the following and get results.
# ping localhost (you should get a good response)
# ping localrouter (give your router ip instead of localrouter).
# nslookup systemname (check your systemname is being resolved correctly by your DNS server and it is not giving any error while resolving your address or IP )
# verify that in /etc/nsswitch.conf you have this entry
hosts files [NOT FOUND=CONTINUE] dns
# in /etc/hosts
make sure you have the entries in order
172.*.*.* systemname test.us1.com
127.0.0.1 localhost loopback
172.*.*.1 primary NISserver
172.*.*.2 someotherservername
# try pinging now.
# if not then verify in
/etc/resolv.conf
domainname : listyourdomain
nameserver: serverip : name
nameserver2: serverip : name
You may stop your network services and restart them or reboot after doing all this.
Regards,
Anil (Don't forget to assign points if all this helps you)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 09:50 AM
тАО09-16-2002 09:50 AM
Re: resolv.conf
1. Yes, I can ping the local host, 127.0.0.1
2. Yes, I can ping my local router
3. No, I cannot ping my dns machine by ip
(the dns is up, I can ping it from another
machine)
4. nslookup on dns hostname fails
(works on another host)
5. nslookup on www.chapman.edu fails
(works from another host)
6. traceroute dns server fails
(works on another host)
Harry Brown requested the config files and the output of a couple of commands, they are attached.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 09:54 AM
тАО09-16-2002 09:54 AM
Re: resolv.conf
From your routing table entry it doesn't look as though the default gateway has been picked up
Your entry in your netconf file is commented out
Remove the comments
/sbin/init.d/net start
To re read the netconf file
HTH
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 09:57 AM
тАО09-16-2002 09:57 AM
Re: resolv.conf
Sorry , this area
# ROUTE_DESTINATION[0]=default
# ROUTE_MASK[0]=""
# ROUTE_GATEWAY[0]="206.211.133.1"
# ROUTE_COUNT[0]="1"
# ROUTE_ARGS[0]=""
HTH
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 10:02 AM
тАО09-16-2002 10:02 AM
Re: resolv.conf
Don't forget to stop and start your network services after you have done this
/sbin/init.d/nfs.client stop
/sbin/init.d/nis.client stop
/sbin/init.d/nfs.server stop
/sbin/init.d/nfs.core stop
restart the same in the opposite order then.
i think you should be good to go. Right now your system is not able to find the gateway it should use. This should fix it
Regards,
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 10:03 AM
тАО09-16-2002 10:03 AM
Re: resolv.conf
I meant "#" against default entries must be removed.
:-)
Regards,
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 10:15 AM
тАО09-16-2002 10:15 AM