Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 2 subscribers
  • Views 2137 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DNS failing today

SalishSwede
My systems have largely ground to a halt due to DNS problems that began sometime in the last 12 hrs.

This is what I'm seeing in the logs.


[FONT=monospace]2013:10:05-00:02:05  wahine named[4579]: error (unexpected RCODE SERVFAIL) resolving  '162.179.17.209.in-addr.arpa/PTR/IN': 209.135.99.3#53 [/FONT]
[FONT=monospace]2013:10:05-00:02:06  s_local_asl@wahine named: Last message 'error (unexpected RC' repeated 1  times, supressed by syslog-ng on wahine.ravennasprings.com [/FONT]
[FONT=monospace]2013:10:05-00:02:06  wahine named[4579]: lame server resolving '164.179.17.209.in-addr.arpa'  (in '179.17.209.in-addr.arpa'?): 139.142.2.3#53 [/FONT]
[FONT=monospace]2013:10:05-00:02:07  wahine named[4579]: error (unexpected RCODE SERVFAIL) resolving  '164.179.17.209.in-addr.arpa/PTR/IN': 209.135.99.3#53 [/FONT]
[FONT=monospace]2013:10:05-00:02:09  s_local_asl@wahine named: Last message 'error (unexpected RC' repeated 1  times, supressed by syslog-ng on my.domain.com [/FONT]
[FONT=monospace]2013:10:05-00:20:04  wahine named[4579]: error (unexpected RCODE REFUSED) resolving  '146.115.155.206.in-addr.arpa/PTR/IN': 216.12.0.7#53 [/FONT]
[FONT=monospace]2013:10:05-00:20:04  wahine named[4579]: lame server resolving  '146.115.155.206.in-addr.arpa' (in '115.155.206.in-addr.arpa'?):  204.70.57.242#53 [/FONT]
[FONT=monospace]2013:10:05-00:20:05  wahine named[4579]: error (unexpected RCODE REFUSED) resolving  '146.115.155.206.in-addr.arpa/PTR/IN': 216.12.0.7#53 [/FONT]


Any ideas?


This thread was automatically locked due to age.
Parents
  • 0
    Hi, Dougga,

    There's no rDNS PTR record for either of the IPs in your first post and 139.142.2.3 is indeed a lame server, so that all looks good to me.  Are you configured like DNS Best Practice?  Did you try #1 in Rulz.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Hi, Dougga,

    There's no rDNS PTR record for either of the IPs in your first post and 139.142.2.3 is indeed a lame server, so that all looks good to me.  Are you configured like DNS Best Practice?  Did you try #1 in Rulz.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Cookie Information Banner