<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
On 03-Aug-22 10:53, <a class="moz-txt-link-abbreviated" href="mailto:bind-users-request@lists.isc.org">bind-users-request@lists.isc.org</a> wrote:<br>
<blockquote type="cite"
cite="mid:mailman.1138.1659538413.56945.bind-users@lists.isc.org">#
cat resolv.conf <br>
<br>
</blockquote>
<blockquote type="cite"
cite="mid:mailman.1138.1659538413.56945.bind-users@lists.isc.org">My
server is 23.123.122.146. That IPv6 addr is my ATT router.<br>
</blockquote>
<p><br>
</p>
<p>You don't want to do that. The ATT router will not know how to
resolve internal names. There is no guarantee that your client
resolver will try nameservers in order. If you want a backup, run
a second instance of named.<br>
</p>
<p>As for the intermittent issues with resolving external names,
that's frequently a case of hitting different nameservers. Or a
firewall.<br>
</p>
<p>Get rid of the ATT router first. Then as suggested, a packet
trace will show what happens (if it still does - it could be that
the ATT router's resolver is at fault). <br>
</p>
<p>Intermediate step would be to use dig.<br>
</p>
<pre class="moz-signature" cols="72">Timothe Litt
ACM Distinguished Engineer
--------------------------
This communication may not represent the ACM or my employer's views,
if any, on the matters discussed.
</pre>
</body>
</html>