Re: Name Service error but resolver is working

I appreciate your help on this. I have visited http://dnsviz.net, rerun the analysis, and followed the DNS tree from root to leaf. I see this: DNSKEYalg=8, id=203262048 bit DNSKEYalg=8, id=21342048 bits (secure) DSdigest alg=2 (secure) DNSKEYalg=8, id=21342048 bits (secure) DNSKEYalg=8, id=3

Re: Name Service error but resolver is working

> On Nov 8, 2018, at 10:01 AM, Viktor Dukhovni > wrote: > > My analysis is that some of upstream providers have broken DNSSEC > implementations that don't handle NSEC3 properly or at all, and > therefore "authenticated denial of existence" is not working for > your domain. > > If the problem

Re: Name Service error but resolver is working

> On Nov 8, 2018, at 9:52 AM, James B. Byrne wrote: > > We have been experiencing an prolonged outage at our off-site dns > location. The two NS in question are located there. The > establishment of NS at multiple location was intended to handle this > sort of situation. We are dealing with th

Re: Name Service error but resolver is working

> > People are telling you the answer, and you're refusing to listen, I > find this puzzling, unless you're no longer getting email from the > list (which seems plausible). I am afraid that my comprehension of what has been written is limited. I regret the defect but there it is. > Every MTA

Re: Name Service error but resolver is working

> On Nov 7, 2018, at 6:08 PM, Viktor Dukhovni > wrote: > > Your DNS is broken. Fix it! At the .CA level you have: > > harte-lyne.ca. IN NS dns04.harte-lyne.ca. ; AD=0 > harte-lyne.ca. IN NS dns03.harte-lyne.ca. ; AD=0 > harte-lyne.ca. IN NS dns01.harte-lyne.ca. ; AD=0 > harte-lyne.ca.

Re: Name Service error but resolver is working

> On Nov 7, 2018, at 5:14 PM, James B. Byrne wrote: > > I do not know what is going on here: > > This is found in the maillog on inet17 > > Nov 7 16:40:21 inet17 postfix/smtpd[79991]: NOQUEUE: reject: RCPT > from unknown[216.185.71.31]: 450 4.1.2 > : Recipient address > rejected: Domain not fo

Re: Name Service error but resolver is working

I do not know what is going on here: This is found in the maillog on inet17 Nov 7 16:40:21 inet17 postfix/smtpd[79991]: NOQUEUE: reject: RCPT from unknown[216.185.71.31]: 450 4.1.2 : Recipient address rejected: Domain not found; from=<> to= proto=ESMTP helo= But this is what I get when I run di

Re: Name Service error but resolver is working

On 7 Nov 2018, at 15:27, James B. Byrne wrote: Neither dns02 nor dns04 are listed in the /etc/resolv.conf file on the affected services. That does not necessarily mean they are not being tried. They are half of your authoritative nameservers and they aren't working, so unless the nameserver(

Re: Name Service error but resolver is working

> On Nov 7, 2018, at 3:27 PM, James B. Byrne wrote: > > Neither dns02 nor dns04 are listed in the /etc/resolv.conf file on the > affected services. > > With respect to Viktor's answer. > > My understanding is that: in the absence of a specified MX record then > the A RR is supposed to be use

Re: Name Service error but resolver is working

On Wed, November 7, 2018 12:22, Paul wrote: > Hi > > Maybe related to some of your NS not responding certainly from the UK > that is > > dig  -t a mx31.harte-lyne.ca  @dns01.harte-lyne.ca  OK > > dig  -t a mx31.harte-lyne.ca  @dns02.harte-lyne.ca     No > response > > dig  -t a mx31.ha

Re: Name Service error but resolver is working

Hi Maybe related to some of your NS not responding certainly from the UK that is dig  -t a mx31.harte-lyne.ca  @dns01.harte-lyne.ca  OK dig  -t a mx31.harte-lyne.ca  @dns02.harte-lyne.ca No response dig  -t a mx31.harte-lyne.ca  @dns03.harte-lyne.ca   several seconds to respond dig  -

Re: Name Service error but resolver is working

>> 50DFB12B2F7 7501 Tue Nov 6 17:22:42 MAILER-DAEMON >> (delivery temporarily suspended: Host or domain name not found. >> Name service error for name=mx31.harte-lyne.ca type=MX: Host not >> found, try again) On Wed, November 7, 2018 11:30, Wietse Venema wrote: >> I do not understand what t

Re: Name Service error but resolver is working

On Wed, Nov 07, 2018 at 11:06:08AM -0500, James B. Byrne wrote: > 50DFB12B2F7 7501 Tue Nov 6 17:22:42 MAILER-DAEMON > (delivery temporarily suspended: Host or domain name not found. Name > service error for name=mx31.harte-lyne.ca type=MX: Host not found, try > again) Note that the lookup i

Re: Name Service error but resolver is working

James B. Byrne: > On our IMAP service host I am seeing messages in the mailq similar to > the following: > > 50DFB12B2F7 7501 Tue Nov 6 17:22:42 MAILER-DAEMON > (delivery temporarily suspended: Host or domain name not found. Name > service error for name=mx31.harte-lyne.ca type=MX: Host not

RE: Name Service error but resolver is working

It's probably backscatter: http://www.postfix.org/BACKSCATTER_README.html -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of James B. Byrne Sent: Wednesday, November 7, 2018 11:06 AM To: postfix-us...@cloud9.net Subject: Name