<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 23/06/2021 08:54, Cheikh Dieng
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADCGpEgzR1djZ7+Ni+Udr+i8keaH5WO7RJVV1XCVkAUmWcvMGA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Very Thanks,
<div><br>
</div>
<div><font size="4">It's clear for me. For dnsdist i need HA
pour my Powerdns.</font></div>
<div><br>
</div>
</div>
</blockquote>
<p>And how are you achieving HA of your dnsdist?</p>
<p>The normal, recommended approach for authoritative DNS resilience
is to have multiple nameservers, listed as separate NS records.
dnsdist is best deployed in special situations, such as the need
to preprocess requests and send them to different destinations.</p>
<p>There's not a problem deploying dnsdist as such: it's just adding
unnecessary complexity, and is an additional layer to manage and
debug.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CADCGpEgzR1djZ7+Ni+Udr+i8keaH5WO7RJVV1XCVkAUmWcvMGA@mail.gmail.com">
<div dir="ltr">
<div>>>The delegation is done at the parent level, yes.
However the delegated domain still needs to contain NS records
and a SOA record for its own zone:<br>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div>Yes, this is some details</div>
</blockquote>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px"><span
style="margin:0px;padding:0px;border:0px;font-variant-numeric:inherit;font-variant-east-asian:inherit;font-stretch:inherit;font-size:10.6667px;line-height:inherit;font-family:Calibri,Arial,Helvetica,sans-serif;vertical-align:baseline;color:rgb(0,0,0)">...</span><span
style="margin:0px;padding:0px;border:0px;font-variant-numeric:inherit;font-variant-east-asian:inherit;font-stretch:inherit;font-size:10.6667px;line-height:inherit;font-family:Calibri,Arial,Helvetica,sans-serif;vertical-align:baseline;color:rgb(0,0,0)">
<div
style="margin:0px;padding:0px;border:0px;font:inherit;vertical-align:baseline;color:inherit"><a
href="http://cloud.lfpw.dsna.fr" moz-do-not-send="true">cloud.lfpw.dsna.fr</a>
3600 IN NS <a
href="http://ns.cloud.lfpw.dsna.fr"
moz-do-not-send="true">ns.cloud.lfpw.dsna.fr</a>.</div>
</span></blockquote>
</div>
</blockquote>
<p><br>
</p>
<p>(1) That NS record disagrees with the delegation NS records.
They need to match.<br>
</p>
<p>(2) As far as I can see, you don't have any A record for
"ns.cloud.lfpw.dsna.fr" in your "cloud.lfpw.dsna.fr" zone, which
means your NS record won't resolve.<br>
</p>
<p>But there are worse problems.</p>
<p>Firstly, lfpw.dsns.fr and cloud.lfpw.dsna.fr are both delegated
to "vitre.cena.fr." but that nameserver does not answer to either
of those domains. Either contact that nameserver operator and get
them to fix it - or change your delegation so you don't use that
nameserver.</p>
<p>Secondly, cloud.lfpw.dsna.fr is delegated to
vip-in.cloud.lfpw.dsna.fr, which has a glue record address of
195.83.98.243. (Glue records are used when the nameserver's name
is inside the domain being delegated: that is, the nameserver
vip-in.cloud.lfpw.dsna.fr is within cloud.lfpw.dsna.fr)<br>
</p>
<p>However that nameserver does not respond:</p>
$ dig +norec @195.83.98.243 cloud.lfpw.dsna.fr. soa<br>
<font face="monospace"><br>
; <<>> DiG 9.10.6 <<>> +norec
@195.83.98.243 cloud.lfpw.dsna.fr. soa<br>
; (1 server found)<br>
;; global options: +cmd<br>
</font>
<p><font face="monospace">;; connection timed out; no servers could
be reached</font></p>
<p><br>
</p>
<p>If you delegate a domain to two nameservers, and both of those
nameservers are not responding, then your domain is completely
broken. You must fix at least one of those problems for it to
start working; and preferably fix both of those problems to have
some resilience.<br>
</p>
<p>I think I will drop out of this thread now. I've tried to
explain the problem three times, and it seems my explanations are
not clear enough, so I will let someone else try. Also, this
isn't really a powerDNS question, but more one of understanding
DNS in general.<br>
</p>
<p>Regards,</p>
<p>Brian.<br>
</p>
</body>
</html>