- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dns client
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
04-15-2002 01:53 AM
04-15-2002 01:53 AM
I have configured DNS client.
edited /etc/resolve.conf and /etc/nsswitch.conf
When I do nslookup it works fine but after that swlist complains that "Could not contact host."
my /etc/resolve.conf looks like this:
#####################
domain hostA.xyz.abc.net
search xyz.abc.net
nameserver xxx.xx.xx.xx
nameserver xxx.xx.xx.xy
############################
If I remove resolve.conf ,swlist works fine
Thanks for your suggestions
Animesh
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 01:58 AM
04-15-2002 01:58 AM
Re: dns client
I believe your domain in your /etc/resolv.conf should be xyz.abc.net instead of hostA.xyz.abc.net.
Hope this helps. Regards.
Steven Sim Kok Leong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 02:06 AM
04-15-2002 02:06 AM
Re: dns client
Thanks but it does not help :(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 02:08 AM
04-15-2002 02:08 AM
Re: dns client
Modify your /etc/nsswitch.conf:
hosts: files [NOTFOUND=continue] dns
Also, try restarting your swagentd:
# swagentd -r
Hope this helps. Regards.
Steven Sim Kok Leong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 09:15 AM
04-15-2002 09:15 AM
SolutionI think your order in resolv.conf file for name server lookup is not proper.
Please do following .
nslookup to your host and see if dns ruturns anything?
May be your hostname entry is not in DNS database. Please update DNS database and ten try to do swlist.
Hope that helps.
You do not need to do anything with nsswitch.conf becasue if you put the hosts entry first , it will not look for DNS unless yur host finds nothing in /etc/hosts....
I am sure your hostname entry is not in DNS or else DNS order you need to change in your resolv.conf file.
-pap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 09:25 AM
04-15-2002 09:25 AM
Re: dns client
You don't need a domain line in resolv.conf. The search line effectively set the domain(s). I would remove the domain line & leave the search line as is.
Also the search order in the nsswitch.conf is important. If you have files first ensure the entry in the hosts file matches the host & doamin parts in the resolv.conf file.
Also you should check the DNS servers to insure you're in there. enter nslookup interactively by not specifying a host then enter
server DNS_server_ip
Then enter your host name & do reverse lookup by entering your host IP as ell. If either returns not found then have the DNS admins correct the entry.
HTH,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 09:29 AM
04-15-2002 09:29 AM
Re: dns client
You need either search or domain line but not both.
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 07:01 PM
04-15-2002 07:01 PM
Re: dns client
For availability and security reasons, I would personally prefer to set usage of /etc/hosts file before usage of the DNS servers in /etc/nsswitch.conf, i.e. use /etc/hosts for resolving critical hosts such as the local server and DNS for resolving non-critical hosts such as clients.
Since your swlist works when resolv.conf was not in place, your /etc/hosts file is already populated correctly with your host-to-ip entry.
Imagine the scenerio that your DNS servers could not be contacted over the network , your swlist (and swinstall, swremove as well) will likely fail in the following scenerios:
1) when DNS server is down
2) when router is down
3) when in single-user or maintenance mode
Apart for availability reasons, from the security aspect, relying on /etc/hosts for translating host-to-ip for critical hosts reduce the chances of your system receiving illegitimate entries e.g.: spoofed DNS replies via
1) poisoned DNS cache
2) man-in-middle attacks
3) spoofed DNS servers
Hope this helps. Regards.
Steven Sim Kok Leong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 07:41 PM
04-15-2002 07:41 PM
Re: dns client
good suggestion.
But my question is when DNS server is down why
swlist not picking up the hostname from /etc/hosts?
Yesterday the hostname was not there in dns databse and after putting entry in dns swlist started working but when dns is not available as you mentioned swlist will not work.
And the reverse lookup is also not implemented in our dns server.Is that the reason?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2002 07:53 PM
04-15-2002 07:53 PM
Re: dns client
>> But my question is when DNS server is down why
swlist not picking up the hostname from /etc/hosts?
1) check /etc/hosts file whether the host entry is there:
1.2.3.4 hostA hostA.xyz.com
2) check /etc/nsswitch.conf:
hosts: files [NOTFOUND=continue] dns
This will ensure that /etc/hosts is read before the DNS server is used to resolve the host names.
Hope this helps. Regards.
Steven Sim Kok Leong