- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- nslookup error
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
Forums
Discussions
Discussions
Discussions
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
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
08-21-2000 10:41 AM
08-21-2000 10:41 AM
*** Unknown source : nisplus. not supported.
*** You have defined one or more supported sources.
*** Please modify your configuration file and try again.
*** Or you will get unreliable information.
...
the ypbind and running in the system. I think in the configuration file it setup both nis and nis+. Can anyone tell me how to modify the configuration files? And which file?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 10:46 AM
08-21-2000 10:46 AM
Re: nslookup error
You should be looking at NIS+ first on the following line:
hosts: nisplus [NOTFOUND=return] files
Brian
<*(((>< er
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 11:07 AM
08-21-2000 11:07 AM
Re: nslookup error
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 11:16 AM
08-21-2000 11:16 AM
Re: nslookup error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 11:22 AM
08-21-2000 11:22 AM
Re: nslookup error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 11:25 AM
08-21-2000 11:25 AM
Re: nslookup error
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 12:28 PM
08-21-2000 12:28 PM
Re: nslookup error
I do not think that password map/database has something to do with hosts map (database, whatever).
At least in nis, simple, not plus, you have different maps for password, hosts, services, a.s.o.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 12:32 PM
08-21-2000 12:32 PM
Re: nslookup error
By the way, do you have another HP machine that uses nisplus for hosts resolution? If yes, compare the config and the patches level.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 12:46 PM
08-21-2000 12:46 PM
Re: nslookup error
If in the nslookup prompt, I set the domain server name, then it will works well within the prompt.
It seems the nslookup can not get the domain server name from the /etc/resolv.conf file.
Any ideas?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 12:54 PM
08-21-2000 12:54 PM
Re: nslookup error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 01:10 PM
08-21-2000 01:10 PM
Re: nslookup error
# nslookup venus
Name Server: name.lll.eee.ddd
Address: nnn.nnn.nnn.nnn
Trying DNS
Trying NIS
Trying files
Name: venus
Address: 192.85.248.3
In this example, the resolver finally found the entry in the local hosts file. You can see it first trying DNS, then NIS. The switch file would look like this:hosts: dns [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=return] nis [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=return]
files
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2000 01:16 PM
08-21-2000 01:16 PM
Re: nslookup error
Berlene
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2000 06:52 AM
08-22-2000 06:52 AM
Re: nslookup error
The problem is most likely in your /etc/nsswitch.conf file. If you have both DNS and NIS configured on your system, try adding the following to /etc/nsswitch.conf (create the file if it doesn't yet exist):
hosts: dns nis files
If you aren't using DNS, just add:
hosts: nis files
At 11.x, /etc/nsswitch.conf also supports "passwd" and "group" entries, which may be of interest.
For more information, do a "man switch", or take a look at the sample template files in /etc/nsswitch.*. Hope that helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2000 06:58 AM
08-22-2000 06:58 AM
Solution"Note, NIS+ is not supported by nslookup. If the hosts source nisplus is found in the /etc/nsswitch.conf file. It will be ignored."
Instead, another resolver such as nsquery should be used as nsquery does support the use of nisplus within /etc/nsswitch.conf.
Berlene
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2000 09:00 AM
08-22-2000 09:00 AM