- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- upgrade the BIND from 8.1.2. to 9.2.0
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
06-29-2005 01:18 PM
06-29-2005 01:18 PM
Jun 29 17:51:36 ns1 named[25971]: client 120.130.33.17#3434: updating zone 'stone.com.tw/IN': update failed: 'RRset exists (value dependent)' prerequisite not satisfied (NXRRSET)
Jun 29 17:51:36 ns1 named[25971]: client 120.130.33.17#3437: update 'stone.com.tw/IN' denied
Jun 29 17:52:40 ns1 named[22404]: lame server resolving 'conmart.co.tl' (in 'co.tl'?): 113.155.150.208#53
Jun 29 17:52:43 ns1 named[22404]: lame server resolving '187.111.229.203.in-addr.arpa' (in '111.229.203.in-addr.arpa'?): 203.238.128.24#53
Jun 29 17:52:43 ns1 named[22404]: lame server resolving '187.111.229.203.in-addr.arpa' (in '111.229.203.in-addr.arpa'?): 103.238.128.22#53
Jun 29 17:52:46 ns1 named[22404]: lame server resolving 'conmart.co.tl' (in 'co.tl'?): 163.209.15.208#53
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2005 05:52 PM
06-29-2005 05:52 PM
SolutionThe second message ( lame server resolving ) indicates that named has learned from a
nameserver that a particular domain is served by a particular
nameserver. When asked, however, that nameserver denies all
knowledge of the particular domain. This means that the server is not an authoritive server for the domain 'conmart.co.tl' .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2005 03:02 PM
06-30-2005 03:02 PM
Re: upgrade the BIND from 8.1.2. to 9.2.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2005 05:25 PM
06-30-2005 05:25 PM
Re: upgrade the BIND from 8.1.2. to 9.2.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2005 05:36 PM
06-30-2005 05:36 PM
Re: upgrade the BIND from 8.1.2. to 9.2.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2005 09:39 PM
06-30-2005 09:39 PM
Re: upgrade the BIND from 8.1.2. to 9.2.0
logging {
category lame-servers {
null;
};
};
This will log the messages of category lame-servers to the channel null , which will actually log that messages nowhere.