Re: DNS resolution issue

2016-09-27 Thread Eric Abrahamsen
Axb writes: > On 09/27/2016 03:46 PM, David Jones wrote: >> >>> /etc/resolv.conf has just got: >> >>> nameserver 173.203.4.9 >>> nameserver 173.203.4.8 >> >>> Unless something is borked in Rackspace's networking config (certainly >>> not impossible), I don't know why that would ever end up pointi

Re: DNS resolution issue

2016-09-27 Thread Matus UHLAR - fantomas
On 27.09.16 11:46, Eric Abrahamsen wrote: My logs are full of runs like this: dns: sendto() to [127.0.0.1]:53 failed: Connection refused, failing over to [::1]:53 dns: sendto() to [::1]:53 failed: Connection refused, failing over to [127.0.0.1]:53 Matus UHLAR - fantomas writes: this means

Re: DNS resolution issue

2016-09-27 Thread Axb
On 09/27/2016 03:46 PM, David Jones wrote: /etc/resolv.conf has just got: nameserver 173.203.4.9 nameserver 173.203.4.8 Unless something is borked in Rackspace's networking config (certainly not impossible), I don't know why that would ever end up pointing to localhost. Setup BIND, unbo

Re: DNS resolution issue

2016-09-27 Thread David Jones
>/etc/resolv.conf has just got: >nameserver 173.203.4.9 >nameserver 173.203.4.8 >Unless something is borked in Rackspace's networking config (certainly >not impossible), I don't know why that would ever end up pointing to >localhost. Setup BIND, unbound, or PowerDNS recursor on localhost and do

Re: DNS resolution issue

2016-09-27 Thread Eric Abrahamsen
Matus UHLAR - fantomas writes: > On 27.09.16 11:46, Eric Abrahamsen wrote: >>I found some posts on the web indicating that, if spamd is having >>trouble doing DNS resolution, it's probably because of a bum entry in >>/etc/resolv.conf. I don't think that's the case here, though, so I'm >>coming to

Re: DNS resolution issue

2016-09-27 Thread Matus UHLAR - fantomas
On 27.09.16 11:46, Eric Abrahamsen wrote: I found some posts on the web indicating that, if spamd is having trouble doing DNS resolution, it's probably because of a bum entry in /etc/resolv.conf. I don't think that's the case here, though, so I'm coming to the list... My logs are full of runs li

DNS resolution issue

2016-09-26 Thread Eric Abrahamsen
I found some posts on the web indicating that, if spamd is having trouble doing DNS resolution, it's probably because of a bum entry in /etc/resolv.conf. I don't think that's the case here, though, so I'm coming to the list... My logs are full of runs like this: dns: sendto() to [127.0.0.1]:53 fa