Thank you Demi,
I appreciate your reply.
Not sure I have a leg to stand on eith them, the old standard reply I got when
I contacted them.
"No one else is having problems, only you"
I do wonder what the recursor do on transient failures, it is never guaranteed
one will always get a reply. A pac
On 04/05/2020 13:41, Remi Gacogne via Pdns-users wrote:
I don't know how bind does resolve but we are doing the right thing
here, we get a delegation to two NS (mail1.alestra.net.mx. and
dns.alestra.net.mx.) for s-s.mx. from the mx. zone, and both of these
servers fail to respond to the first req
On 5/1/20 10:31 PM, Sergio Cesar via Pdns-users wrote:
> Thus the question remains: what do I need to change in the recursor
> configuration to make it work as bind does and resolve even tough it
> looks like an issue at their end?
I don't know how bind does resolve but we are doing the right thin
On Mon, May 04, 2020 at 07:05:48AM -0500, Sergio P Cesar wrote:
> It is not a guessing game, the recursor fail to resolve.
You initial email did not specify which name(s) were queried. Only
later in the thread you list an example. Only with yor latest reply
you tell something about your config.
It is not a guessing game, the recursor fail to resolve.
The only change to the default config in an attempt to have the recursor
not cache the failure and query again is
packetcache-servfail-ttl=0
quiet=no
The servers in question are
DNS: dns.alestra.net.mx 207.248.224.75
On Fri, May 01, 2020 at 11:31:21AM -0500, Sergio P Cesar via Pdns-users wrote:
> I am new with pdns, just installed a resolver 4.3.0-rc2 to learn and all
> seems to work but stumbled into an issue I cant resolve.
>
> My mailserver failed to deliver email to a few domains, in tracking it I
> found
