Re: DNS again

2016-06-04 Thread Reindl Harald
Am 04.06.2016 um 14:40 schrieb jpff: Thank you -- did not realise the /etc/default/unbound file existed. It was set to forward. Will remind me how I prefer instllatins from source for critical programs. Unbound installed from Debian Whezzy nonsense - you don't need to compile anything from

Re: DNS again

2016-06-04 Thread Benny Pedersen
On 2016-06-04 07:56, Patrick Ben Koetter wrote: ACk for unbound. ACK for better dns books to newcommers like me :) Is is a very versatile, fast and stable recursive nameserver. We run it as Recursive DNS at ISPs where, for example at one location, it serves +20 million customers. #/etc/bi

Re: DNS again

2016-06-04 Thread jpff
Thank you -- did not realise the /etc/default/unbound file existed. It was set to forward. Will remind me how I prefer instllatins from source for critical programs. Unbound installed from Debian Whezzy On Sat, 4 Jun 2016, Tom Hendrikx wrote: On 03-06-16 18:19, jpff wrote: X-Originating-<%

Re: DNS again

2016-06-04 Thread jpff
Mailserver is in this house, running Debian. On Fri, 3 Jun 2016, Andy Balholm wrote: I was wondering if your mail server is an on-premises physical machine, or something hosted in a data center somewhere. If it’s in a data center, what data center? On Jun 3, 2016, at 10:47 AM, John wrot

Re: DNS again

2016-06-04 Thread Reindl Harald
Am 04.06.2016 um 11:41 schrieb Tom Hendrikx: On 03-06-16 18:19, jpff wrote: X-Originating-<%= hostname %>-IP: [217.155.197.248] OK I expect to get flamed but anyway I as still seeing the occasional URIBL_BLOCKED 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was

Re: DNS again

2016-06-04 Thread Tom Hendrikx
On 03-06-16 18:19, jpff wrote: > X-Originating-<%= hostname %>-IP: [217.155.197.248] > > OK I expect to get flamed but anyway > > I run a couple of mailers, one of which is small with ~5 users. For > years I ran dnsmasq which was easy to set up and only gave occasional > troubles with the RB

Re: DNS again

2016-06-03 Thread Patrick Ben Koetter
* Reindl Harald : > > > Am 03.06.2016 um 18:40 schrieb Benny Pedersen: > >On 2016-06-03 18:33, Andy Balholm wrote: > >>I was using unbound as a local resolver. All queries were going to > >>127.0.0.1, and there was no forwarding set up. > > > >that disqullify unbound then > > please stop spreadi

Re: DNS again

2016-06-03 Thread Reindl Harald
Am 03.06.2016 um 18:40 schrieb Benny Pedersen: On 2016-06-03 18:33, Andy Balholm wrote: I was using unbound as a local resolver. All queries were going to 127.0.0.1, and there was no forwarding set up. that disqullify unbound then please stop spreading bullshit unbound works perfectly as r

Re: DNS again

2016-06-03 Thread Andy Balholm
I was wondering if your mail server is an on-premises physical machine, or something hosted in a data center somewhere. If it’s in a data center, what data center? > On Jun 3, 2016, at 10:47 AM, John wrote: > > The mail server is my machine with no other server, unless I have > misunderstood

Re: DNS again

2016-06-03 Thread Daniel J. Luke
On Jun 3, 2016, at 12:51 PM, Daniel J. Luke wrote: >> if the first hop in dns is 127.0.0.1 it works > > that's not how +trace works oh, nevermind - you are right. It will query for the root servers from your configured resolvers. -- Daniel J. Luke

Re: DNS again

2016-06-03 Thread Daniel J. Luke
On Jun 3, 2016, at 12:30 PM, Benny Pedersen wrote: > dig +trace ipv4.google.com > > if the first hop in dns is 127.0.0.1 it works that's not how +trace works from the manpage: When tracing is enabled, dig makes iterative queries to resolve the name being looked up. It wil

Re: DNS again

2016-06-03 Thread Benny Pedersen
On 2016-06-03 18:33, Andy Balholm wrote: I was using unbound as a local resolver. All queries were going to 127.0.0.1, and there was no forwarding set up. that disqullify unbound then

Re: DNS again

2016-06-03 Thread Andy Balholm
I was using unbound as a local resolver. All queries were going to 127.0.0.1, and there was no forwarding set up. Andy

Re: DNS again

2016-06-03 Thread Benny Pedersen
On 2016-06-03 18:23, Andy Balholm wrote: Where is your mail server hosted. URIBL blocks queries from some cloud providers (including DigitalOcean) unless you have a subscription. For a while I had a mail server hosted on DO, and I was paying more for my URIBL subscription than for my hosting. h

Re: DNS again

2016-06-03 Thread Benny Pedersen
On 2016-06-03 18:19, jpff wrote: I as still seeing the occasional URIBL_BLOCKED do your homework :=) dig +trace ipv4.google.com if the first hop in dns is 127.0.0.1 it works make sure /etc/resolv.conf only have one single line with nameserver 127.0.0.1 nothing more nothing less dig is pa

Re: DNS again

2016-06-03 Thread Andy Balholm
Where is your mail server hosted. URIBL blocks queries from some cloud providers (including DigitalOcean) unless you have a subscription. For a while I had a mail server hosted on DO, and I was paying more for my URIBL subscription than for my hosting. Andy

DNS again

2016-06-03 Thread jpff
X-Originating-<%= hostname %>-IP: [217.155.197.248] OK I expect to get flamed but anyway I run a couple of mailers, one of which is small with ~5 users. For years I ran dnsmasq which was easy to set up and only gave occasional troubles with the RBL lookups being rejected from my ISP (hi Zen!