Re: named



In article <BSori.20133$13.4552@xxxxxxxxxxxxxxx!nnrp1.uunet.ca>,
Clever Monkey <spamtrap@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Bartlomiej F. Tajchman wrote:
I have a problem with configuration of bind under MacOS control. I have
a correct zone file, I can ask bind for this domain, by
host/dig/nslookup commands. Answers are OK, I have trace of query in
logs. But when I try to use ping/ssh and every other I got "ping: cannot
resolve [domainname]: Unknown host.

In resolv.conf I have myself 127.0.0.1.

How can I solve this issue?

The BSD resolver has never worked for me with a server line of 12.0.0.1.
I always use the local IP address of the nameserver, even on the box
itself.

Interesting. This is a bug that existed for many years (it's even
mentioned in the "DNS & BIND" book), but I thought it had been fixed in
most flavors of Unix years ago. I'm very surprised that OS X still has
it.

If your machine gets its IP dynamically, you can put:

nameserver 0.0.0.0

in /etc/resolv.conf, and this will automatically use the local IP
address. Or just leave out the "nameserver" line entirely, as this is
the default.

--
Barry Margolin, barmar@xxxxxxxxxxxx
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
.



Relevant Pages

  • Re: Nameserver
    ... >I'd like to set up BIND locally to resolve names between machines on my ... >primary nameserver. ... configure your local machines to point to this box as their DNS server. ... Or you can read the DNS HOWTO at The Linux Documentation Project ...
    (RedHat)
  • RE: Here is how to fix your nameserver - was Re: BIND update?
    ... Subject: Here is how to fix your nameserver - was Re: BIND update? ... I myself haven't used the BIND port in the ports ... BIND has 2 parts, there's a set of libraries, usually referred ...
    (FreeBSD-Security)
  • BIND: lokale hosts werden nicht =?ISO-8859-15?Q?aufgel=F6st?=
    ... ich setze BIND 9.3.1 unter SuSE 10 ein. ... Ich würde also das Problem bei der Konfiguration des Nameservers vermuten, wenn nicht "host" und "nslookup" problemlos das täten, was man ... nameserver 192.168.57.1 ... GUT_Vankann.domain.local: bad owner name (check-names) ...
    (de.comp.os.unix.networking.misc)
  • Re: Bind on Fedora.
    ... shows up ok in webmin. ... > nslookup should have returned 2 lines that indicate which server and port ... > force it to query the fedora server, assuming that bind is actually ... > nameserver 192.168.0.1¹ ...
    (linux.redhat)