![]() ![]() What could be the reason? I was reading this. flags: qr rd ra QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 >HEADER<<- opcode: QUERY, status: SERVFAIL, id: 58716 (without +trace) returns: > DiG 9.8.1-P1 > Works perfectly fine and returns the right answer. The two categories you would be interested now are resolver and queries (see BIND9 logging).Here is the main problem: dig +trace You could configure your BIND for more verbose logging, but it's recommend to separate the files per category, as some of the categories are really excessive. Because by default only the errors gets logged, there wouldn't appear a log line telling you this. It's also possible that the problem was solved immediately by simply moving to the next authoritative name server: there should always be at least two, in case one fails. The amount of occasions from 1 to 4 times for each also suggests the same. ![]() dig 133.61.208.88. it has probably been temporary. If there's no error now (confirmed by e.g. These entries were parsed from the syslog file on your recursive name server. Using aggregate zones instead of many separate might help see Using SORBS. SORBS may refuse queries if there are too many in too short period. ![]() IN queries to check against SORBS Listings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |