Strang name resolution behavior

[Stefan Puiu]

Could it be that the hosts in mydomain.local. that you want to use are
also defined in /etc/hosts? Because in that case the nameserver would
not be queried.

So you're saying that with query logging enabled, BIND doesn't report
any incoming queries when you try the commands/programs which fail to
resolve?

I re-read your initial mail and it's not clear from it - is resolution
failing from the host running the nameserver? Or from linux hosts that
are configured to use that nameserver? Are you querying the nameserver
using host/dig from that same machine, or from another Linux box on
the network?

Stefan.

On 4/19/06, Dr. Harry Knitter <harry at knitter-edv-beratung.de> wrote:
> Am Mittwoch, 19. April 2006 08:52 schrieb Stefan Puiu:
> > What do you have in /etc/resolv.conf? If that file points to a
[...]
>
> nameserver <IP of my nameserver>
> search <mydomain.local>
>
> > You also might want to check /etc/nsswitch.conf, especially the
> > 'hosts' directive - I have 'files dns' there, that is, first check
> > /etc/hosts and then the nameservers in /etc/resolv.conf.
> >
>
> same seqence as yours
>
> > You could check to see what's happening by running tcpdump or ethereal
> > in the background when trying the 'ping' command, and then see what
> > nameserver gets actually queried. Then you can look in your
> > configuration and try to find out what's wrong.
> >
>
> From the logs it seems that bind isn´t reached at all by the queries of the
> programs that fail resolving.
>
> > HTH,
> > Stefan.
> >
>
>
> Regards
>
> Harry
>