Re: named
- From: The Natural Philosopher <a@xxx>
- Date: Tue, 31 Jul 2007 12:14:00 +0100
Bartlomiej F. Tajchman wrote:
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.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.
In resolv.conf I have myself 127.0.0.1.
How can I solve this issue?
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...
Mmm. On Linux I merely have nameserver 127.0.0.1
Now I wonder...I have seen this before years ago when SUN first started replacing things with the netinfo stuff..
When you do your ping, or whatever,does it comes straight back and tell you it can't resolve?or does it hang around for about half a minute and then say so?
From man 5 resolver
The resolver is a set of routines in the C library resolv(3) that provide
access to the Internet Domain Name System (DNS). A resolver configura-
tion file contains information used to specify parameters for a DNS
resolver client. The file contains a list of keywords with values that
provide various types of resolver information.
Mac OS X supports a DNS search strategy that may involve multiple DNS
resolver clients. See the SEARCH STRATEGY section below for an overview
of multi-client DNS search.
Each DNS client is configured using the contents of a single configura-
tion file of the format described below, or from a property list supplied
from some other system configuration database. Note that the
/etc/resolv.conf file, which contains configuration for the default (or
"primary") DNS resolver client, is maintained automatically by Mac OS X
and should not be edited manually. Changes to the DNS configuration
should be made by using the Network Preferences panel.
That may be an issue..
Try entering name servers in the 'graphical way' by configuring TCP/IP
.
Best regards,
Bart.
- Follow-Ups:
- Re: named
- From: The Natural Philosopher
- Re: named
- References:
- Prev by Date: Re: Can't authenticate in NetInfo Manager
- Next by Date: Re: New iMac keyboards
- Previous by thread: Re: named
- Next by thread: Re: named
- Index(es):
Relevant Pages
|
