Strange Name Server Problem - SOLVED

[Odhiambo Washington]

On 20 April 2017 at 21:48, Odhiambo Washington <odhiambo at gmail.com> wrote:

> I have a server running FreeBSD 11.0-STABLE.
>
> I am a little stumped why my local caching bind instance doesn't answer
> queries. I have then opted to run bind on port 5353 and unbound on port 53.
> I still experience the same problem!
>
> root at waridi:/usr/local/etc/unbound # sockstat -l | grep named
> bind     named      50877 20 tcp4   192.168.27.254:5353   *:*
> bind     named      50877 21 tcp4   127.0.0.1:5353        *:*
> bind     named      50877 22 tcp4   127.0.0.1:953         *:*
> bind     named      50877 23 tcp6   ::1:953               *:*
> bind     named      50877 512 udp4  192.168.27.254:5353   *:*
> bind     named      50877 513 udp4  192.168.27.254:5353   *:*
> bind     named      50877 514 udp4  192.168.27.254:5353   *:*
> bind     named      50877 515 udp4  127.0.0.1:5353        *:*
> bind     named      50877 516 udp4  127.0.0.1:5353        *:*
> bind     named      50877 517 udp4  127.0.0.1:5353        *:*
> root at waridi:/usr/local/etc/unbound # sockstat -l | grep unb
> unbound  unbound    51296 3  udp4   127.0.0.1:53          *:*
> unbound  unbound    51296 4  tcp4   127.0.0.1:53          *:*
> unbound  unbound    51296 5  udp4   192.168.27.254:53     *:*
> unbound  unbound    51296 6  tcp4   192.168.27.254:53     *:*
> unbound  unbound    51296 10 udp4   *:29712               *:*
> unbound  unbound    51296 11 udp4   *:28511               *:*
> unbound  unbound    51296 13 udp4   *:35511               *:*
> unbound  unbound    51296 14 udp4   *:19644               *:*
> unbound  unbound    51296 15 udp4   *:22549               *:*
> unbound  unbound    51296 16 udp4   *:30714               *:*
> unbound  unbound    51296 17 udp4   *:11907               *:*
> unbound  unbound    51296 18 udp4   *:50834               *:*
> root at waridi:/usr/local/etc/unbound #
>
> Name resolution takes so long because it has to happen via the ISPs DNS
> Servers, which are the 3rd and 4th options in /etc/resolv.conf
>
> I am actually lost as to where to start looking.
>


It turns out that bind was trying to resolve the names against IPv6
addresses.
It's only today (20180130) that I figured this out by running nslookup and
looking at what bind was logging.
I installed bind-9.11 with IPv6 disabled and now my name lookups is fast!
As I had wanted.


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."