AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Servfail unexpected rcode resolving12/14/2023 ![]() ![]() Google's 8.8.8.8 resolves this domain properlyīy the way, the server is firewalled so no harm in allowing recursion from all sources. ![]() I see those errors in logfile: Dec 22 11:53:02 router2.lan named: skipping nameserver '' because it is a CNAME, while resolving 'Dec 22 11:53:02 router2.lan named: SERVFAIL unexpected RCODE resolving '63.249.66.124#53ĭec 22 11:53:02 router2.lan named: skipping nameserver '' because it is a CNAME, while resolving 'Dec 22 11:53:02 router2.lan named: skipping nameserver '' because it is a CNAME, while resolving 'Dec 22 11:53:02 router2.lan named: SERVFAIL unexpected RCODE resolving '63.249.66.124#53ĭec 22 11:53:02 router2.lan named: skipping nameserver '' because it is a CNAME, while resolving 'Dec 22 11:53:02 router2.lan named: skipping nameserver '' because it is a CNAME, while resolving '(that domain is not mine) This particular part seems to contains "(REFUSED)", others have "(SERVFAIL)", and this appears in same time when server becomes unavailable.I have a recursive caching BIND/named setup and it does not want to resolve some domains. A dedicated server goes down around twice a day, all sites become unavailable, plesk, etc.Īt the same time interval I get in /var/logs/messages these errors:
0 Comments
Read More
Leave a Reply. |