- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: named error message: sysquery:nlookup error on...
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
тАО04-04-2006 10:15 PM
тАО04-04-2006 10:15 PM
named error message: sysquery:nlookup error on ?
I have DNS configured for a local Intranet, but there is no connnection to the Internet.
Is the system trying to query a non-existant root name server ?
The system is operating normally as far as I can tell, but it would be usefull to remove the cause of this error message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 11:25 PM
тАО04-04-2006 11:25 PM
Re: named error message: sysquery:nlookup error on ?
Please post exact error message and /etc/ntp.conf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 03:02 AM
тАО04-05-2006 03:02 AM
Re: named error message: sysquery:nlookup error on ?
"falpha named [9681]:sysquery: nlookup error on?"
ntp.conf: attached file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 07:29 PM
тАО04-05-2006 07:29 PM
Re: named error message: sysquery:nlookup error on ?
nslookup has nothing to do with ntp (/etc/ntp.conf) but rather with /etc/resolv.conf and named. So, /etc/namedb/* conf files are involved.
You can also have a $HOME/.nslookuprc file.
Hope this will help you.
Regards,
VINCENT Jean-Marc
HP France
Groupe Support Unix
Tru64(tm) UNIX Technical Consultant - Tru64(tm) UNIX Ambassador HP France
+33 1 5762-8861
jean-marc.vincent@hp.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 11:03 PM
тАО04-05-2006 11:03 PM
Re: named error message: sysquery:nlookup error on ?
I thought it wasn't NTP related, but since Valdimir asked for the file, I posted it anyway.
I will attach the /etc/named files, and the resolv.conf later today.
(I do not have a .nslookuprc file anywhere as far as I know, but I will check this out as well.)
I emptied out the named.ca, as I did not want it to contact unreachable root name servers, this may be the cause.
Looking through the O' Reilly Albitz & Liu book has not given me any clues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 11:30 PM
тАО04-05-2006 11:30 PM
Re: named error message: sysquery:nlookup error on ?
I agree with Jean-Marc. It has to do with name server, not time server (I was configuring time server while writting answer to you, so I missed the point).
Of course, we need to know more about named configuration.
I wiil see that after you post required files.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2006 03:17 AM
тАО04-06-2006 03:17 AM
Re: named error message: sysquery:nlookup error on ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2006 03:39 AM
тАО04-12-2006 03:39 AM
Re: named error message: sysquery:nlookup error on ?
However, as I am only building an Intranet DNS, I don't want the system trying to probe the root nameservers.
Hence I had removed the entries from the file.
So my question should be: How do I configure DNS bind so that it operates on an Intranet, without trying to probe root or other external nameservers ? (and without it throwing a series of error messages ?)