HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- named fails after installing patch kit
Operating System - Tru64 Unix
1827849
Members
1924
Online
109969
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
01-08-2004 01:25 AM
01-08-2004 01:25 AM
named fails after installing patch kit
Hello all,
My bind software was working fine till I installed patch kit 8 for digital unix 4.0f,
After installing patches, the patch installer gave the message to run
/usr/sbin/named-bootconf < /etc/namedb/named.boot > /etc/namedb/named.conf
i did the same and also
rcmgr set BIND_SERVERARGS -c /etc/namedb/named.conf
Then after that the named service is starting, and though it is resolving few other master domains, and all slave domains, but it is not resolving our main master domain of which this server is the main domain controller.
I also see some errors for the main domain's configuration file. Why have these errors arrived after installing patch kit ( which has upgraded the bind version.)
But same configuration files when I copy on a linux with bind 8.x.x it works perfectly.
How do I run the same new converted zone files on this upgraded digital unix.
Regards,
Naresh.
My bind software was working fine till I installed patch kit 8 for digital unix 4.0f,
After installing patches, the patch installer gave the message to run
/usr/sbin/named-bootconf < /etc/namedb/named.boot > /etc/namedb/named.conf
i did the same and also
rcmgr set BIND_SERVERARGS -c /etc/namedb/named.conf
Then after that the named service is starting, and though it is resolving few other master domains, and all slave domains, but it is not resolving our main master domain of which this server is the main domain controller.
I also see some errors for the main domain's configuration file. Why have these errors arrived after installing patch kit ( which has upgraded the bind version.)
But same configuration files when I copy on a linux with bind 8.x.x it works perfectly.
How do I run the same new converted zone files on this upgraded digital unix.
Regards,
Naresh.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2004 05:45 AM
01-08-2004 05:45 AM
Re: named fails after installing patch kit
first have you checked if the started bind/named process is still the updated one. the given command converts the old named.conf syntax to the new one required for newer versions.
1. What happened if you use the old config file?
2. What is the difference within the file after the convertion?
3. Is the Linux version also the same version as the Tru64 bind? (exact version, not 8.*)
1. What happened if you use the old config file?
2. What is the difference within the file after the convertion?
3. Is the Linux version also the same version as the Tru64 bind? (exact version, not 8.*)
Help() { FirstReadManual(urgently); Go_to_it;; }
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2004 08:07 PM
01-09-2004 08:07 PM
Re: named fails after installing patch kit
Yes, this converted file made from digital unix only I used in linux and bind version on both machines is 8.x.x.
Also the binary changes after installing the patch kit.
How do I know what has gone wrong
Also the binary changes after installing the patch kit.
How do I know what has gone wrong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2004 08:13 PM
01-11-2004 08:13 PM
Re: named fails after installing patch kit
question is if it the exact version and not if the first major-number matches....
Help() { FirstReadManual(urgently); Go_to_it;; }
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP