Date: Wed, 15 Aug 2007 02:01:10 -0500 From: Derek Ragona <derek@computinginnovations.com> To: Nicholas Wieland <nicholas.wieland@gmail.com>, freebsd-questions@freebsd.org Subject: Re: Local domain with Bind Message-ID: <6.0.0.22.2.20070815015421.02690b68@mail.computinginnovations.com> In-Reply-To: <41FB0507-8216-416A-86FB-F3A1CE56D753@gmail.com> References: <41FB0507-8216-416A-86FB-F3A1CE56D753@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 06:44 PM 8/14/2007, Nicholas Wieland wrote:
>Hi *, I have a problem setting up Bind9, and I really don't
>understand what's wrong with my configuration.
>
>luna# uname -a
>FreeBSD luna.subbacultcha.local 6.2-RELEASE FreeBSD 6.2-RELEASE #0:
>Fri Jan 12 10:40:27 UTC 2007 root@dessler.cse.buffalo.edu:/usr/
>obj/usr/src/sys/GENERIC i386
>
>
>
>luna# cat /etc/namedb/named.conf
>acl "subbacultcha" {
> 192.168.0.0/24;
> localnets;
>};
>
>options {
> directory "/etc/namedb";
> pid-file "/var/run/named/pid";
> dump-file "/var/dump/named_dump.db";
> statistics-file "/var/stats/named.stats";
>
> allow-query {
> "subbacultcha";
> };
>
> forwarders {
> 208.67.222.222;
> 208.67.220.220;
> };
>
>};
>
>logging {
>
> channel named_log {
> syslog named;
> severity debug 3;
> print-category yes;
> print-time yes;
> print-severity yes;
> };
>
> category default { named_log; };
> category xfer-in { named_log; };
> category xfer-out { named_log; };
> category unmatched { named_log; };
>
>};
>
>zone "." {
> type hint;
> file "named.root";
>};
>
>zone "0.0.127.IN-ADDR.ARPA" {
> type master;
> file "master/localhost.rev";
>};
>
>// RFC 3152
>zone
>"1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARP A" {
> type master;
> file "master/localhost-v6.rev";
>};
>
>zone "subbacultcha.local" {
> type master;
> file "/etc/namedb/subbacultcha.local";
>};
>
>zone "0.168.192.in-addr.arpa" {
> type master;
> file "/etc/namedb/revp.0.168.192";
>};
>
>
>
>luna# cat /etc/namedb/subbacultcha.local
>subbacultcha.local. IN SOA ns.subbacultcha.local.
>root.subbacultcha.local (
> 200708111 ; serial
> 3H ; refresh
> 1H ; retry
> 1W ; expire
> 1D ) ; minimum
>
>subbacultcha.local. IN NS
>ns.subbacultcha.local.
> IN A 192.168.0.2
>mail.subbacultcha.local. IN MX 10
>mail.subbacultcha.local.
>subbacultcha.local. IN MX 10
>mail.subbacultcha.local.
>
>localhost IN A 127.0.0.1
>
>luna CNAME
>subbacultcha.local.
>hg CNAME
>subbacultcha.local.
>
>
>
>luna# cat /etc/namedb/revp.0.168.192
>$TTL 1D
>
>@ IN SOA subbacultcha.local.
>root.subbacultcha.local. (
> 20070811 ; serial
> 3H ; refresh
> 1H ; retry
> 1W ; expire
> 1D ; minimum
> )
>
> IN NS ns.subbacultcha.local.
> IN PTR mail.subbacultcha.local.
> IN PTR hg.subbacultcha.local.
> IN PTR subbacultcha.local.
>
>
>
>This is the problem from another machine on the lan (192.168.0.3):
>
>ngw@chienandalusia ~$ dig subbacultcha.local
>
>; <<>> DiG 9.3.4 <<>> subbacultcha.local
>;; global options: printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30754
>;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
>
>;; QUESTION SECTION:
>;subbacultcha.local. IN A
>
>;; ANSWER SECTION:
>subbacultcha.local. 86400 IN A 192.168.0.2
>
>;; AUTHORITY SECTION:
>subbacultcha.local. 86400 IN NS ns.subbacultcha.local.
>
>;; Query time: 8 msec
>;; SERVER: 192.168.0.2#53(192.168.0.2)
>;; WHEN: Wed Aug 15 01:39:26 2007
>;; MSG SIZE rcvd: 69
>
>
>ngw@chienandalusia ~$ ping subbacultcha.local
>ping: cannot resolve subbacultcha.local: Unknown host
>
>
>ngw@chienandalusia ~$ ping 192.168.0.2
>PING 192.168.0.2 (192.168.0.2): 56 data bytes
>64 bytes from 192.168.0.2: icmp_seq=0 ttl=64 time=0.743 ms
>
>
>When I ping the domain nothing happens in logs ...
>
>Thanks for every suggestion, I'm *sure* I'm missing something obvious
>here ...
This looks like the DNS settings on your other server, chienandalusia
(192.168.0.3), is not setup correctly. Check /etc/resolv.conf on this
server, and be sure the first nameserver is:
nameserver 192.168.0.2
In fact on this server you should have only that entry, as your server at
192.168.0.2 should forward any other unknown DNS requests upstream to the
forwarders.
-Derek
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.2.20070815015421.02690b68>