- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Name Resolution
Operating System - Linux
1753773
Members
5308
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО01-11-2002 06:16 AM
тАО01-11-2002 06:16 AM
Name Resolution
nsswitch.conf contains:
hosts: files nisplus dns
When I try to resolve a host name
that is NOT in dns, but is in my
/etc/host file, resolution fails. I don't
think nslookup ever looks at the
/etc/host file. Anyone know how to
insure the /etc/host file is looked at?
hosts: files nisplus dns
When I try to resolve a host name
that is NOT in dns, but is in my
/etc/host file, resolution fails. I don't
think nslookup ever looks at the
/etc/host file. Anyone know how to
insure the /etc/host file is looked at?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2002 06:30 AM
тАО01-11-2002 06:30 AM
Re: Name Resolution
Additional information - RedHat 7.2
I am using a static ip address.
I have tried moving resolv.conf to a
different name.
I am using a static ip address.
I have tried moving resolv.conf to a
different name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2002 02:20 PM
тАО01-12-2002 02:20 PM
Re: Name Resolution
Hello,
Of sure, on linux's nslookup is unable to check /etc/hosts.
There are 2 ways to make the system use /etc/hosts first :
-> /etc/nsswitch.conf : your syntax is correct.
-> /etc/host.conf : it depends on the libc you are using. Normally, it should contains something like :
order hosts,bind
multi on
To check whether your /etc/hosts is actually used or not, put a fake entry in it, using an IP that is currently up and available on your network, and using a hostname for which you are sure DNS is not going to reply. Example :
192.168.1.1 fakehost
Then, try to ping fakehost : if it replies, then you are sure /etc/hosts have been used.
If you want more help, please describe exactly the tests you did and the problem you have with name resolution.
Good luck.
Kodjo
Of sure, on linux's nslookup is unable to check /etc/hosts.
There are 2 ways to make the system use /etc/hosts first :
-> /etc/nsswitch.conf : your syntax is correct.
-> /etc/host.conf : it depends on the libc you are using. Normally, it should contains something like :
order hosts,bind
multi on
To check whether your /etc/hosts is actually used or not, put a fake entry in it, using an IP that is currently up and available on your network, and using a hostname for which you are sure DNS is not going to reply. Example :
192.168.1.1 fakehost
Then, try to ping fakehost : if it replies, then you are sure /etc/hosts have been used.
If you want more help, please describe exactly the tests you did and the problem you have with name resolution.
Good luck.
Kodjo
Learn and explain...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP