> -Original Message-
> From: bind-users On Behalf Of Alex
> I'm leaning towards that, too. The problem persists even when using
> the provider's DNS servers. I thought for sure I'd see some verifiable
> info from other people having problems with cable, such as from
> dslreports, etc,
Hi,
On Sun, Sep 30, 2018 at 1:19 PM @lbutlr wrote:
>
> On 30 Sep 2018, at 09:59, Alex wrote:
> > It also tends to happen in bulk - there may be 25 SERVFAILs within the
> > same second, then nothing for another few minutes.
>
> That really makes it seem like either you modem or you ISP is
On 30 Sep 2018, at 09:59, Alex wrote:
> It also tends to happen in bulk - there may be 25 SERVFAILs within the
> same second, then nothing for another few minutes.
That really makes it seem like either you modem or you ISP is interfering
somehow, or is simply not able to keep up.
--
'Who's
Hi,
> > Sep 29 14:33:54 mail03 postfix/dnsblog[3290]: warning:
> > dnsblog_query: lookup error for DNS query
> > 123.139.28.66.dnsbl.sorbs.net: Host or domain name not found. Name
> > service error for name=123.139.28.66.dnsbl.sorbs.net type=A: Host
> > not found, try again
> >
> > I'd really be
On Sep 26, 2018, at 07:52, Jukka Pakkanen wrote:
> Still Symantec "enterprise support technician" claims the problem is on our
> DNS servers, and as a "proof" send the chapter 4.1.1 of the RFC1035, where it
> is stated that "code 2 = server failure", and this should prove that our
> servers
Hi there,
On Sun, 30 Sep 2018, Alex wrote:
Sep 29 14:33:54 mail03 postfix/dnsblog[3290]: warning:
dnsblog_query: lookup error for DNS query
123.139.28.66.dnsbl.sorbs.net: Host or domain name not found. Name
service error for name=123.139.28.66.dnsbl.sorbs.net type=A: Host
not found, try again
6 matches
Mail list logo
