Very odd behavior out of local_unbound+named
- Reply: Tomasz CEDRO : "Re: Very odd behavior out of local_unbound+named"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 10 Jan 2022 23:00:23 UTC
For local DNS lookup the local_unbound+named on 192.168.11.254 works but for any other machine that has 192.168.11.254 as a nameserver nothing is getting resolved. The very odd part of this is remote used to work but stopped working all the sudden without any configuration changes to 192.168.11.254 or even logging into it. 192.168.11.254 is up and running and has the following in the named.conf: listen-on { 127.0.0.1; 192.168.11.254; }; Which is unmodified since the time it stopped working. Here is the ifconfig for .254: aryeh@server% ifconfig -a vtnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE> ether 00:a0:98:61:83:b8 inet 192.168.11.254 netmask 0xffffff00 broadcast 192.168.11.255 media: Ethernet 10Gbase-T <full-duplex> status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> Here is the resolve.conf for the machine that fails to resolve: search lan.fnwe.net. nameserver 192.168.11.254 nameserver 192.168.11.1 When queried directly with the host(1) command 254 can look stuff up: Desktop@neomarx% host google.com 192.168.11.254 Using domain server: Name: 192.168.11.254 Address: 192.168.11.254#53 Aliases: google.com has address 172.217.165.142 google.com has IPv6 address 2607:f8b0:4006:808::200e google.com mail is handled by 10 aspmx.l.google.com. google.com mail is handled by 40 alt3.aspmx.l.google.com. google.com mail is handled by 20 alt1.aspmx.l.google.com. google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 50 alt4.aspmx.l.google.com. The uname -a for .254 is: FreeBSD server 12.1-RELEASE-p3 FreeBSD 12.1-RELEASE-p3 r359374 GENERIC amd64 The ifconfig and uname for the host attempting to resolve google.com is: Desktop@neomarx% ifconfig -a re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 00:d8:61:78:d4:9c inet 192.168.11.20 netmask 0xffffff00 broadcast 192.168.11.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> Desktop@neomarx% uname -a FreeBSD neomarx 13.0-STABLE FreeBSD 13.0-STABLE #1 stable/13-n247310-7959799d93c: Fri Sep 17 10:44:21 EDT 2021 root@neomarx:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org