- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- DNS: host unreachable resolving
Operating System - HP-UX
1820484
Members
2255
Online
109624
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
05-25-2010 08:49 PM
05-25-2010 08:49 PM
Hello,
I'm running bind 9.3.2.4 over HP-UX B.11.23. I got the next errors under named.log file:
25-May-2010 13:54:46.448 lame-servers: info: lame server resolving 'dnsnatl0.datl.voicestream.us.gprs' (in 'VOICESTREAM.US.gprs'?): 216.155.160.111#53
25-May-2010 13:54:46.882 lame-servers: info: lame server resolving 'dnsnatl0.datl.voicestream.us.gprs' (in 'VOICESTREAM.US.gprs'?): 216.155.160.111#53
25-May-2010 13:55:24.915 lame-servers: info: lame server resolving 'gprsnsext1.proximus.be.gprs' (in 'proximus.be.gprs'?): 213.181.60.1#53
25-May-2010 13:55:24.915 lame-servers: info: lame server resolving 'gprsnsext2.proximus.be.gprs' (in 'proximus.be.gprs'?): 213.181.60.1#53
25-May-2010 13:55:25.367 lame-servers: info: lame server resolving 'gprsnsext1.proximus.be.gprs' (in 'proximus.be.gprs'?): 213.181.60.2#53
25-May-2010 13:55:25.368 lame-servers: info: lame server resolving 'gprsnsext2.proximus.be.gprs' (in 'proximus.be.gprs'?): 213.181.60.2#53
25-May-2010 14:05:47.491 lame-servers: info: host unreachable resolving '31.4.19.172.in-addr.arpa/PTR/IN': 2001:500:3::42#53
25-May-2010 14:05:48.773 lame-servers: info: host unreachable resolving 'U.ARIN.NET/A/IN': 2001:500:31::108#53
25-May-2010 14:05:49.220 lame-servers: info: host unreachable resolving '31.4.19.172.in-addr.arpa/PTR/IN': 2001:500:14:6050:ad::1#53
25-May-2010 14:05:50.441 lame-servers: info: host unreachable resolving 'W.ARIN.NET/A/IN': 2001:503:a83e::2:30#53
25-May-2010 14:05:50.441 lame-servers: info: host unreachable resolving 'W.ARIN.NET/AAAA/IN': 2001:503:a83e::2:30#53
25-May-2010 14:05:50.442 lame-servers: info: host unreachable resolving 'X.ARIN.NET/A/IN': 2001:503:a83e::2:30#53
In according with your experience, Could you give me any clue about why i got "host unreachable" for IPv6?
Regards,
CHristian Aguilar
I'm running bind 9.3.2.4 over HP-UX B.11.23. I got the next errors under named.log file:
25-May-2010 13:54:46.448 lame-servers: info: lame server resolving 'dnsnatl0.datl.voicestream.us.gprs' (in 'VOICESTREAM.US.gprs'?): 216.155.160.111#53
25-May-2010 13:54:46.882 lame-servers: info: lame server resolving 'dnsnatl0.datl.voicestream.us.gprs' (in 'VOICESTREAM.US.gprs'?): 216.155.160.111#53
25-May-2010 13:55:24.915 lame-servers: info: lame server resolving 'gprsnsext1.proximus.be.gprs' (in 'proximus.be.gprs'?): 213.181.60.1#53
25-May-2010 13:55:24.915 lame-servers: info: lame server resolving 'gprsnsext2.proximus.be.gprs' (in 'proximus.be.gprs'?): 213.181.60.1#53
25-May-2010 13:55:25.367 lame-servers: info: lame server resolving 'gprsnsext1.proximus.be.gprs' (in 'proximus.be.gprs'?): 213.181.60.2#53
25-May-2010 13:55:25.368 lame-servers: info: lame server resolving 'gprsnsext2.proximus.be.gprs' (in 'proximus.be.gprs'?): 213.181.60.2#53
25-May-2010 14:05:47.491 lame-servers: info: host unreachable resolving '31.4.19.172.in-addr.arpa/PTR/IN': 2001:500:3::42#53
25-May-2010 14:05:48.773 lame-servers: info: host unreachable resolving 'U.ARIN.NET/A/IN': 2001:500:31::108#53
25-May-2010 14:05:49.220 lame-servers: info: host unreachable resolving '31.4.19.172.in-addr.arpa/PTR/IN': 2001:500:14:6050:ad::1#53
25-May-2010 14:05:50.441 lame-servers: info: host unreachable resolving 'W.ARIN.NET/A/IN': 2001:503:a83e::2:30#53
25-May-2010 14:05:50.441 lame-servers: info: host unreachable resolving 'W.ARIN.NET/AAAA/IN': 2001:503:a83e::2:30#53
25-May-2010 14:05:50.442 lame-servers: info: host unreachable resolving 'X.ARIN.NET/A/IN': 2001:503:a83e::2:30#53
In according with your experience, Could you give me any clue about why i got "host unreachable" for IPv6?
Regards,
CHristian Aguilar
Christian Aguilar
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2010 03:47 AM
05-26-2010 03:47 AM
Solution
Hello Christian,
a) Lame server warning means that name servers that are specified as authoritative in this domain's zone actually are not authoritative. If it is your domain, then check name servers.
b) Or, remote name servers that are supposed to be authoritative for these domains are not.
When your server tries to resolve host names
in those domains, the DNS servers do not respond as expected, and you get the "lame server" message in your log.
c) About "host unreachable" issue,
take a look at nice explanations like:
http://www.ietf.org/rfc/rfc4074.txt
d) Overall, Nothing to worry about, more
an annoyance than anything else.
You can disable the logging of lame
server messages in /etc/named.conf;
logging {
category lame-servers{ null; };
};
Cheers,
VK2COT
a) Lame server warning means that name servers that are specified as authoritative in this domain's zone actually are not authoritative. If it is your domain, then check name servers.
b) Or, remote name servers that are supposed to be authoritative for these domains are not.
When your server tries to resolve host names
in those domains, the DNS servers do not respond as expected, and you get the "lame server" message in your log.
c) About "host unreachable" issue,
take a look at nice explanations like:
http://www.ietf.org/rfc/rfc4074.txt
d) Overall, Nothing to worry about, more
an annoyance than anything else.
You can disable the logging of lame
server messages in /etc/named.conf;
logging {
category lame-servers{ null; };
};
Cheers,
VK2COT
VK2COT - Dusan Baljevic
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP