- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- DNS side effects
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-08-2002 05:54 AM
04-08-2002 05:54 AM
DNS side effects
I add a DNS in the panel DNS resolver list of the system.
After this, when I invoke aCC (the compiler), I have the foloowing message :
ERROR: NAMESERVER IS DOWN!!
TRY AGAIN WHEN IT IS UP!!
the DNS is a valid address (194.2.0.20)
any idea.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 06:35 AM
04-08-2002 06:35 AM
Re: DNS side effects
Where did you add this? in /etc/resolv.conf? did you check your /etc/nsswitch.conf file?
Try pinging dns server.
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 06:45 AM
04-08-2002 06:45 AM
Re: DNS side effects
nslookup $(/usr/bin/hostname)
If this fails, then either the nameserver is not responding (down) or the nameserver does not know your hostname. In both cases, this is a bad thing for many applications so create (or change) /etc/nsswitch.conf to resolve important hostnames from /etc/hosts first, then using DNS as a last resort. nsswitch.conf would have a hosts line like this:
hosts: files[NOTFOUND=continue UNAVAIL=continue] dns [NOTFOUND=return UNAVAIL=continue TRYAGAIN=return]
This will improve the reliability (and performance) of your system by reducing the dependence on a DNS server to run various programs. Your local hostname MUST always be there, plus any important hosts (and LAN printers) that you may need.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 06:48 AM
04-08-2002 06:48 AM
Re: DNS side effects
I don't know in which file is stored this information.
I just used SAM/Networking&communications/dns(bind)/dns resolver
and add my dns ip address which is 194.2.0.20 which i can ping
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 06:54 AM
04-08-2002 06:54 AM
Re: DNS side effects
OK when you use sam for that it goes in to one file /etc/resolv.conf.
As Bill says first change your nsswitch.conf file and use file as first resolvere.
Your dns server might be up but may be named daemon is down on that server. But if you have files first on your /etc/nsswitch.conf then atleast it works for your hostname.
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 06:55 AM
04-08-2002 06:55 AM
Re: DNS side effects
It seems that your name resolution service is not properly configured
1. You have to check your /etc/resolv.conf file for proper name server in order. try to ping each of the name server in order whether they are responding.
Then do nslookup for your machine name.
2. Look for /etc/nsswitch.conf file. Check the order for host name resolution order. It should be dns..... depending upon your configuration.
hopefully the things will be working fine.
Also if trying above two steps , you are not able to resolv your problem, change the order in /etc/nsswitch.conf by putting "files" first then dns......
for that you need to have entry for host name in /etc/hosts with correct IP address.....and chck for /etc/rc.config.d/netconf file.
Thanks,
-pap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 06:56 AM
04-08-2002 06:56 AM
Re: DNS side effects
1. Do a nslookup for the server name , iot will resolve etiher using DNS or /etc/hosts , most likely in you case it is the /etc/hosts .
2. In case you have /etc/resolv.conf please add the following :
nameserver < IP ADRESSS for the DNS>
Now check by nslookup localhost name ,
You should be good to go as you can already ping it .
Manoj Srivastava
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 06:57 AM
04-08-2002 06:57 AM
Re: DNS side effects
Script started on Mon Apr 8 14:59:30 2002
root@messira:/tmp # nslookup $(/usr/bin/hostname)
*** Warning - the local domain is not set.
*** Either hostname should be a domain name,
*** the domain should be specified in /etc/resolv.conf,
*** or the shell variable LOCALDOMAIN should be set.
Name Server: ns-cache0.oleane.net
Address: 194.2.0.20
Trying DNS
Trying NIS
looking up FILES
Name: messira
Address: 192.168.200.42
Aliases: messira.corobor.com
root@messira:/tmp # exit
script done on Mon Apr 8 14:59:53 2002
something is wrong ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 07:08 AM
04-08-2002 07:08 AM
Re: DNS side effects
nameserver 194.2.0.20
/etc/nsswitch.conf : does not exist
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 07:10 AM
04-08-2002 07:10 AM
Re: DNS side effects
Share and Enjoy! Ian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 07:10 AM
04-08-2002 07:10 AM
Re: DNS side effects
edit /etc/resolv.conf file. It sould look like this
domain your_domainname.com
nameserver ip_of_dns_server
nameserver ip_of_dns_server2
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 07:28 AM
04-08-2002 07:28 AM
Re: DNS side effects
corobor.com
I set the default domain name to
corobor.com
/etc/resolv.conf contains
domain corobor.com
nameserver 194.2.0.20
I still got error message when invoking compiler (aCC or cc)
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2002 10:46 AM
04-08-2002 10:46 AM
Re: DNS side effects
hosts: files [conditions...] NIS ... DNS
(man nsswitch.conf for details on syntax)
I didn't know it was possible to run without one....