- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- bind - unexpected RCODE (SERVFAIL)
Operating System - Linux
1819694
Members
3478
Online
109605
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
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
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
тАО10-30-2008 10:59 PM
тАО10-30-2008 10:59 PM
bind - unexpected RCODE (SERVFAIL)
rpm -q bind
bind-9.3.4-1.23
this is caching dns server, and working(resolving queries) fine.
from /etc/named.conf
forward first;
forwarders { ISP_NS1_IP; ISP_NS2_IP; 4.2.2.2; };
now
# tail -f /var/log/mesages
unexpected RCODE (SERVFAIL) resolving 'stats.surfaid.ihost.com/AAAA/IN': ISP_NS1_IP#53
unexpected RCODE (SERVFAIL) resolving 'stats.surfaid.ihost.com/AAAA/IN': 4.2.2.2#53
unexpected RCODE (SERVFAIL) resolving 'stats.surfaid.ihost.com/AAAA/IN': ISP_NS2_IP#53
FORMERR resolving 'stats.surfaid.ihost.com/AAAA/IN': 64.238.216.230#53
FORMERR resolving 'stats.surfaid.ihost.com/AAAA/IN': 209.235.30.142#53
FORMERR resolving 'stats.surfaid.ihost.com/AAAA/IN': 66.179.173.211#53
unexpected RCODE (SERVFAIL) resolving 'data.coremetrics.com/AAAA/IN': ISP_NS2_IP#53
unexpected RCODE (SERVFAIL) resolving 'data.coremetrics.com/AAAA/IN': 4.2.2.2#53
unexpected RCODE (SERVFAIL) resolving 'data.coremetrics.com/AAAA/IN': ISP_NS1_IP#53
FORMERR resolving 'data.coremetrics.com/AAAA/IN': 64.238.216.230#53
FORMERR resolving 'data.coremetrics.com/AAAA/IN': 209.235.30.142#53
lame server resolving 'data.coremetrics.com' (in 'data.coremetrics.com'?): 66.179.173.211#53
whats "unexpected RCODE (SERVFAIL)" means ?
whats "FORMERR resolving" means ?
Regards
bind-9.3.4-1.23
this is caching dns server, and working(resolving queries) fine.
from /etc/named.conf
forward first;
forwarders { ISP_NS1_IP; ISP_NS2_IP; 4.2.2.2; };
now
# tail -f /var/log/mesages
unexpected RCODE (SERVFAIL) resolving 'stats.surfaid.ihost.com/AAAA/IN': ISP_NS1_IP#53
unexpected RCODE (SERVFAIL) resolving 'stats.surfaid.ihost.com/AAAA/IN': 4.2.2.2#53
unexpected RCODE (SERVFAIL) resolving 'stats.surfaid.ihost.com/AAAA/IN': ISP_NS2_IP#53
FORMERR resolving 'stats.surfaid.ihost.com/AAAA/IN': 64.238.216.230#53
FORMERR resolving 'stats.surfaid.ihost.com/AAAA/IN': 209.235.30.142#53
FORMERR resolving 'stats.surfaid.ihost.com/AAAA/IN': 66.179.173.211#53
unexpected RCODE (SERVFAIL) resolving 'data.coremetrics.com/AAAA/IN': ISP_NS2_IP#53
unexpected RCODE (SERVFAIL) resolving 'data.coremetrics.com/AAAA/IN': 4.2.2.2#53
unexpected RCODE (SERVFAIL) resolving 'data.coremetrics.com/AAAA/IN': ISP_NS1_IP#53
FORMERR resolving 'data.coremetrics.com/AAAA/IN': 64.238.216.230#53
FORMERR resolving 'data.coremetrics.com/AAAA/IN': 209.235.30.142#53
lame server resolving 'data.coremetrics.com' (in 'data.coremetrics.com'?): 66.179.173.211#53
whats "unexpected RCODE (SERVFAIL)" means ?
whats "FORMERR resolving" means ?
Regards
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2008 01:13 AM
тАО10-31-2008 01:13 AM
Re: bind - unexpected RCODE (SERVFAIL)
Search for DNSSEC in the BIND documentation.
Debian GNU/Linux for the Enterprise! Ask HP ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2008 05:28 AM
тАО10-31-2008 05:28 AM
Re: bind - unexpected RCODE (SERVFAIL)
you have probably disabled queries from the world and only allowed from your
local network. you can:
- allow queries to the zone in the zone "data.coremetrics.com" statement (allow_query)
- allow queries from the whole world to your nameserver and allow recuesion only from your lan
- run authoritative-only nameserver on different IP that knows this zone and has recursion disabled
I recommend the last option. For the option 2, don't forget to disable recursion from the internet - it may cause you problems.
local network. you can:
- allow queries to the zone in the zone "data.coremetrics.com" statement (allow_query)
- allow queries from the whole world to your nameserver and allow recuesion only from your lan
- run authoritative-only nameserver on different IP that knows this zone and has recursion disabled
I recommend the last option. For the option 2, don't forget to disable recursion from the internet - it may cause you problems.
a warrior never quits
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2008 10:29 AM
тАО10-31-2008 10:29 AM
Re: bind - unexpected RCODE (SERVFAIL)
It seems that your server had problems contacting the DNS server for tats.surfaid.ihost.com or resolving it's IPV6 (AAAA) address. I saw messages like this on mail servers with IPV6 enabled for the MTA.
See also RFC 4074:
http://www.ietf.org/rfc/rfc4074.txt
See also RFC 4074:
http://www.ietf.org/rfc/rfc4074.txt
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
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