- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- BIND v4.9.7 (PHNE_20618)
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
Discussions
Discussions
Forums
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
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
тАО07-17-2000 04:50 AM
тАО07-17-2000 04:50 AM
BIND v4.9.7 (PHNE_20618)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2000 05:58 AM
тАО07-17-2000 05:58 AM
Re: BIND v4.9.7 (PHNE_20618)
Swremove the patch. Read the text, and see if it is applicable to you environment and make changes if necessay, before reinstalling the patch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2000 06:51 AM
тАО07-17-2000 06:51 AM
Re: BIND v4.9.7 (PHNE_20618)
Defect Description:
PHNE_20618:
1. JAGac40451 / SR8606125060:
Boundary conditions are not handled properly.
Resolution:
The boundary conditions have been addressed.
2. JAGaa57264 / SR5003446138:
BIND 4.9.7 running as internal nameserver
and forwarding queries to external nameserver
fails when the lookup address has a CNAME
record with a higher TTL than its corresponding
A record.
Resolution:
The query packet header was not properly framed.
Now a proper header is sent in the query packet.
This was happening with queries to the internet to sites like yahoo.com and cnn.com that use round-robin responses. Once I installed the patch, these sites were accessible on a reliable basis again. Now it's just the hosts_to_named script that's misbehaving.
I DO know better than to blindly apply patches.. Been burned before!! :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2000 01:33 PM
тАО07-19-2000 01:33 PM
Re: BIND v4.9.7 (PHNE_20618)
I don't know if this is applicable or not but I installed the patch to to my test system, I have a script that runs the host_to_named conversion and at the end restart named, the problem I had was in the restart of named that was takeing a long time due to the fact that the bin 4.9.7 doesn't like host names with "_" in them. I had to add to my named.boot file a ignore statement to get over these errors. Hope this helps
Donald Branch
IBJ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2000 02:08 PM
тАО07-19-2000 02:08 PM
Re: BIND v4.9.7 (PHNE_20618)
The script that I am referring to is the hosts_to_named. I ran sdiff on it and the older version and found the difference. They added a routine called getip() that verifies that the IP address octets are between 0 and 255 inclusive (in case an address is typo'd). It creates a file, the cat's it through this awk routine. I went back to using the previous version of the script and it runs in about 5 minutes, instead of 2 hours. I just make sure that I don't type an IP address!!! :-) Not worth the extra 1 hr 55 minutes of runtime.