Re: ,Re: caching does not seem to be working for internal view

2022-08-04 Thread Paul Kosinski via bind-users
On Wed, 3 Aug 2022 15:10:39 -0400 Timothe Litt wrote: > Hmm.  Your resolv.conf says that it's written by NetworkManager. > > What I suggested should have stopped it from updating resolv.conf. > > See >

Re: caching does not seem to be working for internal view

2022-08-03 Thread Lee
On 8/3/22, Robert Moskowitz via bind-users wrote: > thanks Greg. Yes I need to figure out how to troubleshoot this. But > here is some stuff: > > # cat resolv.conf > # Generated by NetworkManager > search attlocal.net htt-consult.com > nameserver 23.123.122.146 > nameserver 2600:1700:9120:4330::1

Re: caching does not seem to be working for internal view

2022-08-03 Thread Greg Choules via bind-users
Hi Robert. Turn on query logging by doing "rndc querylog". You should see a message saying that has been done in "named.log", to where each query will now be logged. If you have views, part of the query log will contain which view was matched. So this will tell you two things: 1. If the

Re: caching does not seem to be working for internal view

2022-08-03 Thread Robert Moskowitz
This is boarderline not thinking on my part. OF COURSE those FQDNs resolve fast; they are in local ZOne files. No lookup needed. Sheesh. "Slow down, you move to fast.  Got to make the Mornin' last!"  :) On 8/3/22 14:43, Robert Moskowitz wrote: Perhaps this is only caching the zones in the

Re: ,Re: caching does not seem to be working for internal view

2022-08-03 Thread Timothe Litt
Hmm.  Your resolv.conf says that it's written by NetworkManager. What I suggested should have stopped it from updating resolv.conf. See

Re: caching does not seem to be working for internal view

2022-08-03 Thread Robert Moskowitz
Perhaps this is only caching the zones in the Internal View, not all public stuff looked up by internal clients? I say this because I get fast responses to internal servers, but slow if at all to external ones. Grasping here because my search foo is weak and I can't find where it is defined

Re: ,Re: caching does not seem to be working for internal view

2022-08-03 Thread Robert Moskowitz
On 8/3/22 12:59, Timothe Litt wrote: Try echo -e "[main]\ndns=none" > /etc/NetworkManager/conf.d/no-dns.conf systemctl restart NetworkManager.service Same content in resolv.conf.  BTW this is on Centos7. Timothe Litt ACM Distinguished Engineer -- This

Re: ,Re: caching does not seem to be working for internal view

2022-08-03 Thread Robert Moskowitz
On 8/3/22 13:10, Anand Buddhdev wrote: On 03/08/2022 18:36, Robert Moskowitz wrote: Hi Robert, [snip] ARGH! I want the IPv6 addr from my firewall/gateway.  But I don't want that IPv6 nameserver! Calm down. Just add "PEERDNS=no" in your ifcfg-eth0 file. This way, the resolv.conf file

Re: ,Re: caching does not seem to be working for internal view

2022-08-03 Thread Anand Buddhdev
On 03/08/2022 18:36, Robert Moskowitz wrote: Hi Robert, [snip] ARGH! I want the IPv6 addr from my firewall/gateway.  But I don't want that IPv6 nameserver! Calm down. Just add "PEERDNS=no" in your ifcfg-eth0 file. This way, the resolv.conf file will only contain your specified DNS

Re: ,Re: caching does not seem to be working for internal view

2022-08-03 Thread Timothe Litt
Try echo -e "[main]\ndns=none" > /etc/NetworkManager/conf.d/no-dns.conf systemctl restart NetworkManager.service Timothe Litt ACM Distinguished Engineer -- This communication may not represent the ACM or my employer's views, if any, on the matters discussed. On

Re: ,Re: caching does not seem to be working for internal view

2022-08-03 Thread Robert Moskowitz
On 8/3/22 11:35, Timothe Litt wrote: On 03-Aug-22 10:53, bind-users-requ...@lists.isc.org wrote: # cat resolv.conf My server is 23.123.122.146.  That IPv6 addr is my ATT router. You don't want to do that.  The ATT router will not know how to resolve internal names.  There is no guarantee

,Re: caching does not seem to be working for internal view

2022-08-03 Thread Timothe Litt
On 03-Aug-22 10:53, bind-users-requ...@lists.isc.org wrote: # cat resolv.conf My server is 23.123.122.146.  That IPv6 addr is my ATT router. 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

Re: caching does not seem to be working for internal view

2022-08-03 Thread Robert Moskowitz via bind-users
thanks Greg.  Yes I need to figure out how to troubleshoot this. But here is some stuff: # cat resolv.conf # Generated by NetworkManager search attlocal.net htt-consult.com nameserver 23.123.122.146 nameserver 2600:1700:9120:4330::1 My server is 23.123.122.146.  That IPv6 addr is my ATT

Re: caching does not seem to be working for internal view

2022-08-03 Thread Greg Choules via bind-users
Hi Robert. May we see the file /etc/resolv.conf and your BIND configuration? It's difficult to guess what might be going on with only a small snippet of information. If you "ping somewhere" (or "ssh a-server", or whatever) the OS will consult resolv.conf to determine where to send DNS queries. If