On Fri, Apr 17, 2020 at 12:45 PM Tim Daneliuk <tun...@tundraware.com> wrote:
> On 4/17/20 10:17 AM, julien soula wrote: > > On Fri, Apr 17, 2020 at 09:56:21AM -0500, Tim Daneliuk wrote: > >> On 4/17/20 9:50 AM, Bob Harold wrote: > >>> > >>> Agree, that's odd, and not what the man page says. Any chance that > there is some other DNS helper running, like resolved, nscd, dnsmasq, etc? > >> > >> Nope. This is vanilla FreeBSD with vanilla bind running. > >> > >>> 'dig' should tell you what address it used, at the bottom of the > output - what does it say? > >> > >> > >> > >> ;; Query time: 0 msec > >> ;; SERVER: ::1#53(::1) > >> ;; WHEN: Fri Apr 17 09:53:51 CDT 2020 > >> ;; MSG SIZE rcvd: 83 > >> > >> > >> Does the SERVER line indicate it's trying to get to the local instance > via > >> IPV6 or is this just standard notation? (This is an IPV4 only > environment). > > > > "::1" is locahost in IPv6. It is not the same as 127.0.0.1 . A least, > > you should add this IP to trustedhosts to check if it works. > > > > best regard, > > > > > Aha! That was it. What is curious to me is that bind uses this even in > the absence > of any IPV6 in the environment. > > Problem solved. Thanks all! > > > > -- > > ---------------------------------------------------------------------------- > Tim Daneliuk tun...@tundraware.com > PGP Key: http://www.tundraware.com/PGP/ > > As a separate issue: Check the logs to see if BIND is trying to use IPv6 to resolve queries. Look for messages like: address not available resolving .... with some IPv6 address I have to start named with the "-4" option on my servers that do not yet have IPv6 connectivity. -- Bob Harold
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
