HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- About DNS forward
Operating System - HP-UX
1833401
Members
3218
Online
110052
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
06-04-2001 07:52 PM
06-04-2001 07:52 PM
About DNS forward
I have a internal DNS server which is running on HPUX 10.20. The server is configured as "root" server. Now, i am going to config the server to forward dns request to other dns server which are located in other sub-network. Could you tell me how to config the forwarder and what i need to do in '/etc/named.boot' file?
Thanks
Thanks
I love it!!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2001 11:01 PM
06-04-2001 11:01 PM
Re: About DNS forward
An entry like this will help
thanks
forwarders 139.130.4.4 203.50.1.75
slave
thanks
forwarders 139.130.4.4 203.50.1.75
slave
we can solve anything!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2001 01:32 AM
06-05-2001 01:32 AM
Re: About DNS forward
If the named daemon will not start
If the named daemon is not running, follow the steps below:
Step 1. On the DNS server for the NCPM subdomain, make sure you have a file called /etc/named.boot.
Step 2. If your host is on an isolated subnet, make sure you are using an /etc/named.data/db.cache file that contains the root name servers for your domain. If your subnet is located behind a firewall, you cannot reach the root name servers for the Internet, and named will not start up correctly unless it can contact a root name server.
Step 3. Issue the ping command to make sure the name server for the NCPM domain can contact the root name servers. If ping fails, there may be a problem with your network or your network connections. See Installing and Administering LAN/9000 Software for troubleshooting information.
Step 4. Read the last few entries in the syslog file (usually /var/adm/syslog/syslog.log) to see if named logged any errors. Startup problems and syntax errors in the DNS database files are usually logged by syslog.
Step 5. Issue the following command to restart named with debugging on:
/usr/sbin/sig_named debug 2
Examine the file /var/tmp/named.run to see what is happening when named starts up. For an explanation of DNS debugging output, see DNS and BIND , by Paul Albitz and Cricket Liu, published by O'Reilly and Associates.
Be sure to turn named debugging off when you have found the problem. Otherwise, the /var/tmp/named.run file will grow large, and named performance will suffer. To turn named debugging off, issue the following command:
/usr/sbin/sig_named debug 0
If the named daemon is not running, follow the steps below:
Step 1. On the DNS server for the NCPM subdomain, make sure you have a file called /etc/named.boot.
Step 2. If your host is on an isolated subnet, make sure you are using an /etc/named.data/db.cache file that contains the root name servers for your domain. If your subnet is located behind a firewall, you cannot reach the root name servers for the Internet, and named will not start up correctly unless it can contact a root name server.
Step 3. Issue the ping command to make sure the name server for the NCPM domain can contact the root name servers. If ping fails, there may be a problem with your network or your network connections. See Installing and Administering LAN/9000 Software for troubleshooting information.
Step 4. Read the last few entries in the syslog file (usually /var/adm/syslog/syslog.log) to see if named logged any errors. Startup problems and syntax errors in the DNS database files are usually logged by syslog.
Step 5. Issue the following command to restart named with debugging on:
/usr/sbin/sig_named debug 2
Examine the file /var/tmp/named.run to see what is happening when named starts up. For an explanation of DNS debugging output, see DNS and BIND , by Paul Albitz and Cricket Liu, published by O'Reilly and Associates.
Be sure to turn named debugging off when you have found the problem. Otherwise, the /var/tmp/named.run file will grow large, and named performance will suffer. To turn named debugging off, issue the following command:
/usr/sbin/sig_named debug 0
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