Re: named

Barry Margolin pisze:
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.

Unfortunately, no success...


Machine is 192.168.1.15. Results after querying about domain:

lisa:~ root# dig test.lisa.tld @192.168.1.15

; <<>> DiG 9.3.4 <<>> test.lisa.tld @192.168.1.15
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39436
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;test.lisa.tld. IN A

;; ANSWER SECTION:
test.lisa.tld. 86400 IN A 192.168.1.15

;; AUTHORITY SECTION:
lisa.tld. 86400 IN NS ns.lisa.tld.

;; ADDITIONAL SECTION:
ns.lisa.tld. 86400 IN A 192.168.1.15

;; Query time: 0 msec
;; SERVER: 192.168.1.15#53(192.168.1.15)
;; WHEN: Tue Jul 31 11:21:11 2007
;; MSG SIZE rcvd: 80


Answer is OK.

But next:

lisa:~ root# ping test.lisa.tld
ping: cannot resolve test.lisa.tld: Unknown host


It doesn't work.

In /etc/resolv.conf I've tried nameserver 192.168.1.15, nameserver 127.0.0.1, nameserver 0.0.0.0 and without any nameserver. Still misfortune...



Best regards,
Bart.
.

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)
  • Re: /etc/resolv.conf with 3 nameservers
    ... nameserver Internet address of a name server that the ... I think the problem is that once your first server responds with a "domain not found", that's considered an answer to your query. ... If you were to disable the DNS server on 10.0.1.201, then it would use xxx.xxx.xxx.xxx or yyy.yyy.yyy.yyy to resolve the query. ...
    (freebsd-questions)
  • 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)