<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Try</p>
<p>echo -e "[main]\ndns=none" >
/etc/NetworkManager/conf.d/no-dns.conf<br>
systemctl restart NetworkManager.service<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>
<div class="moz-cite-prefix">On 03-Aug-22 12:36, Robert Moskowitz
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:17fdb4c1-7bde-b0ef-03ea-d4dd675a1fa2@htt-consult.com">
<br>
<br>
On 8/3/22 11:35, Timothe Litt wrote:
<br>
<blockquote type="cite">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"># cat resolv.conf
<br>
<br>
My server is 23.123.122.146. That IPv6 addr is my ATT router.
<br>
</blockquote>
<br>
<br>
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>
<br>
As for the intermittent issues with resolving external names,
that's frequently a case of hitting different nameservers. Or a
firewall.
<br>
<br>
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>
<br>
</blockquote>
<br>
Thank you for your advice. my ifcfg-eth0 has:
<br>
<br>
DEVICE="eth0"
<br>
BOOTPROTO=none
<br>
ONBOOT="yes"
<br>
TYPE="Ethernet"
<br>
NAME="eth0"
<br>
MACADDR=02:67:15:00:00:02
<br>
MTU=1500
<br>
DNS1=23.123.122.146
<br>
GATEWAY="23.123.122.158"
<br>
IPADDR="23.123.122.146"
<br>
NETMASK="255.255.255.240"
<br>
IPV6INIT="yes"
<br>
<br>
And I am ASSuMEing that it is that IPV6INIT that is providing that
IPv6 addr in resolv.cat. So I added:
<br>
<br>
DNS2=192.168.224.2
<br>
<br>
And now:
<br>
<br>
# cat /etc/resolv.conf
<br>
# Generated by NetworkManager
<br>
search attlocal.net htt-consult.com
<br>
nameserver 23.123.122.146
<br>
nameserver 192.168.224.2
<br>
nameserver 2600:1700:9120:4330::1
<br>
<br>
ARGH!
<br>
<br>
I want the IPv6 addr from my firewall/gateway. But I don't want
that IPv6 nameserver!
<br>
<br>
So I added the IPv6 address for my server. I had not done this as
ATT has said there is no assurance with the IPv6 addresses may
change. So I added:
<br>
<br>
DNS3=2600:1700:9120:4330::49
<br>
<br>
and now:
<br>
<br>
# cat /etc/resolv.conf
<br>
# Generated by NetworkManager
<br>
search attlocal.net htt-consult.com
<br>
nameserver 23.123.122.146
<br>
nameserver 192.168.224.2
<br>
nameserver 2600:1700:9120:4330::1
<br>
# NOTE: the libc resolver may not support more than 3 nameservers.
<br>
# The nameservers listed below may not be recognized.
<br>
nameserver 2600:1700:9120:4330::49
<br>
<br>
Sigh. I have to take that dynamic IPv6 assignment. But I want to
stop it pushing into my resolv.conf.
<br>
<br>
</blockquote>
</body>
</html>