weird name resolution problem w/ bind

Newsgroup,
I do have a strange behaviour of bind (version 9.2.3 running on SuSE
9.1,
kernel 2.6.5-7.75-smp) as follows:

ping hp8550 (hp8550 is a local networked printer) from a ssh window
(putty) times out without resolving the name yielding an error message
as follows:

ping: unknown host hp8550

This is also the case if started with the FQDN (ping
hp8550.xxxxx.local) to
resolve for the IP address:
ping: unknown host hp8550.xxxxx.local

nslookup hp8550 from the same ssh console returns the correct FQDN
together
with the IP-number as follows:

Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 192.168.xx.1
Address: 192.168.xx.1#53

Name: hp8550.xxxxx.local
Address: 192.168.xx.64

Same ping from a XP cmd window of a local PC connected to the local
domain
works without any problems: ping hp8550 resolves to the correct IP and
pings.



All external pings (i.e. hosts not in the local domain) with domain
names
resolve for the IP address and work as expected regardless whether
from XP
or ssh window. You can substitute bind with telnet, ftp, etc - all do
not
resolve correctly if executed from the ssh console.
BTW the same is true for the linux console

Setup is as follows:
authoritative bind for the domain xxxxx.local with "forwarders ..." to
the
ISP's name servers with "forward first". Restricted to allow queries
from
the local subnet + loopback and listening on dedicated local subnet
address
(192.168.xx.1) plus loopback.

At the moment I am clueless and would appreciate any suggestion.

Many thanks and best regards,

Klaus


Klaus A. Kreil

On 3 Jul 2004 14:15:38 -0700, Klaus A. Kreil <(E-Mail Removed)> wrote:
> Newsgroup,
> I do have a strange behaviour of bind (version 9.2.3 running on SuSE
> 9.1,
> kernel 2.6.5-7.75-smp) as follows:
>
> ping hp8550 (hp8550 is a local networked printer) from a ssh window
> (putty) times out without resolving the name yielding an error message
> as follows:
>
> ping: unknown host hp8550
>
> This is also the case if started with the FQDN (ping
> hp8550.xxxxx.local) to
> resolve for the IP address:
> ping: unknown host hp8550.xxxxx.local

The ".local" domain popularly used with older SuSE versions does not work
with SuSE 9.1, because it is reserved for something else (multicast?). So
you need to use some name other than "local" for your local domain.

When I changed my local bind9 zones and checked over apache and smtp, The
only thing that tripped me up on an older SuSE box, was a variable for
postfix that caused some fetchmail to be lost when it tried to relay
through localhost.local which no longer existed.

--
David Efflandt - All spam ignored http://www.de-srv.com/

David Efflandt <(E-Mail Removed)> wrote:
> On 3 Jul 2004 14:15:38 -0700, Klaus A. Kreil <(E-Mail Removed)> wrote:
>> Newsgroup,
>> I do have a strange behaviour of bind (version 9.2.3 running on SuSE
>> 9.1,
>> kernel 2.6.5-7.75-smp) as follows:
>>
>> ping hp8550 (hp8550 is a local networked printer) from a ssh window
>> (putty) times out without resolving the name yielding an error message
>> as follows:
>>
>> ping: unknown host hp8550
>>
>> This is also the case if started with the FQDN (ping
>> hp8550.xxxxx.local) to
>> resolve for the IP address:
>> ping: unknown host hp8550.xxxxx.local

> The ".local" domain popularly used with older SuSE versions does not work
> with SuSE 9.1, because it is reserved for something else (multicast?). So
> you need to use some name other than "local" for your local domain.

> When I changed my local bind9 zones and checked over apache and smtp, The
> only thing that tripped me up on an older SuSE box, was a variable for
> postfix that caused some fetchmail to be lost when it tried to relay
> through localhost.local which no longer existed.

David,
where the hell did you get that information from or was it only with fetchmail ? I could not find anything about it despite searching for quiet some time. Do you know whether this is a SuSE only issue or something to do with the latest bind release?

Anyway - I have changed local to home and that did the trick. I would not even have guessed that that might have contributed to the problem.

Many thanks for your help. It was a quick and simple change and it only took 2 minutes to resolve.

Best regards,

Klaus