HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: DNS for stand alone database server
Operating System - HP-UX
1835104
Members
2504
Online
110076
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
Forums
Discussions
Discussions
Discussions
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
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
11-26-2002 09:24 AM
11-26-2002 09:24 AM
DNS for stand alone database server
I am unsure if I should be posting here or in the sysadmin...
I have a 11.00 database and app server that I want to have the ability to resolve dns. Right now the dns local name server and dns resolver values are empty. We use novell dns for our network.
I am assuming I need to add the novell dns server to the dns resolver field. What else do I need to do? Are there entries in nsswitchlconf or hosts or resolv.conf.
Recommendations on the order of nss?
TIA
Doug
I have a 11.00 database and app server that I want to have the ability to resolve dns. Right now the dns local name server and dns resolver values are empty. We use novell dns for our network.
I am assuming I need to add the novell dns server to the dns resolver field. What else do I need to do? Are there entries in nsswitchlconf or hosts or resolv.conf.
Recommendations on the order of nss?
TIA
Doug
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2002 09:35 AM
11-26-2002 09:35 AM
Re: DNS for stand alone database server
I would have a small /etc/hosts files with the local host, loopback, and a few often accessed hosts in it. You then set /etc/resolv.conf to your DNS server. My order for /etc/nsswitch.conf would be FILES then DNS.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2002 12:46 PM
11-26-2002 12:46 PM
Re: DNS for stand alone database server
Hi Doug,
For lightning-fast response, I would also recommend setting up your server as either a caching-only nameserver or a stealth secondary for your zones. You would then list the server itself as the first resolver. We do this with our high-volume SMTP servers, and it improves performance considerably.
It also ensures that DNS changes are propagated to your server instead of having to maintain static records in /etc/hosts. Depending on the size of your environment, though, it may be easier just to do like Clay noted and put the commonly resolved names in /etc/hosts. And like Clay noted, you should have at a minimum localhost and your machine's own name in /etc/hosts.
If you don't go with caching-only or stealth secondary, note that you should probably list files first then dns in /etc/nsswitch.conf.
Cheers,
Jim
For lightning-fast response, I would also recommend setting up your server as either a caching-only nameserver or a stealth secondary for your zones. You would then list the server itself as the first resolver. We do this with our high-volume SMTP servers, and it improves performance considerably.
It also ensures that DNS changes are propagated to your server instead of having to maintain static records in /etc/hosts. Depending on the size of your environment, though, it may be easier just to do like Clay noted and put the commonly resolved names in /etc/hosts. And like Clay noted, you should have at a minimum localhost and your machine's own name in /etc/hosts.
If you don't go with caching-only or stealth secondary, note that you should probably list files first then dns in /etc/nsswitch.conf.
Cheers,
Jim
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP