Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Networking
User Name
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.


  Search this Thread
Old 07-03-2004, 08:31 AM   #1
LQ Newbie
Registered: Jun 2004
Location: Austria
Distribution: SuSE
Posts: 5

Rep: Reputation: 0
Unhappy weird name resolution problem

Hello BIND experts,
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

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,

Old 07-04-2004, 07:47 AM   #2
LQ Newbie
Registered: Jun 2004
Location: Austria
Distribution: SuSE
Posts: 5

Original Poster
Rep: Reputation: 0
Lightbulb name resolution problem solved

Thanks to a newsgroup post from David Efflandt in reply to my query the problem is solved:

Starting from SuSE 9.1 the doman .local does no longer work - for reasons only known by SuSE. Based upon David's recommendation I have changed to the domain .home and things now do work. Unfortunately it appears as if this behaviour is not - or at least not very well - documentd by SuSE

So - if you try to set up a private domain at home with bind do NOT USE .local

Best regards,



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
weird, weird problems with logitech precision USB gamepad ikataii Linux - Hardware 4 10-14-2005 05:31 AM
Weird with screen resolution using NVIDIA javb Linux - Laptop and Netbook 1 02-06-2005 07:43 PM
Weird, weird apache2 problem atheist Debian 1 09-17-2004 09:26 PM
weird kernel problem and fs mount problem intense Slackware 5 03-16-2004 01:36 PM
Weird problem glock19 Linux - General 1 02-12-2002 08:25 AM > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 02:19 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration