Loaded, but not

[Tuc at T-B-O-H]

> 
> Tuc at T-B-O-H wrote:
> >>Tuc at T-B-O-H wrote:
> >>
> >>>Hi,
> >>>
> >>>	Now that I solved the other issue, I'm working on the next one.
> >>>
> >>>	When I go to load some zones, they claim to load, but don't...
> >>>
> >>>soekris# date
> >>>Fri Jan  6 21:08:33 EST 2006
> >>>soekris# /etc/rc.d/named stop
> >>>Stopping named.
> >>>soekris# /etc/rc.d/named start
> >>>Starting named.
> >>>soekris# rndc dumpdb
> >>>soekris# date
> >>>Fri Jan  6 21:08:51 EST 2006
> >>>
> >>>soekris# grep named /var/log/spool
> >>>Jan  6 21:08:38 soekris named[24297]: shutting down
> >>>Jan  6 21:08:38 soekris named[24297]: stopping command channel on 127.0.0.1#953
> >>>Jan  6 21:08:38 soekris named[24297]: stopping command channel on ::1#953
> >>>Jan  6 21:08:38 soekris named[24297]: no longer listening on 127.0.0.1#53
> >>>Jan  6 21:08:38 soekris named[24297]: exiting
> >>>Jan  6 21:08:43 soekris named[24539]: starting BIND 9.3.1 -u bind -t /var/named
> >>>Jan  6 21:08:43 soekris named[24539]: found 1 CPU, using 1 worker thread
> >>>Jan  6 21:08:43 soekris named[24539]: loading configuration from '/etc/namedb/na
> >>>med.conf'
> >>>Jan  6 21:08:43 soekris named[24539]: listening on IPv4 interface lo0, 127.0.0.1
> >>>#53
> >>>Jan  6 21:08:43 soekris named[24539]: command channel listening on 127.0.0.1#953
> >>>Jan  6 21:08:43 soekris named[24539]: command channel listening on ::1#953
> >>>Jan  6 21:08:43 soekris named[24539]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded seria
> >>>l 20051218
> >>>Jan  6 21:08:43 soekris named[24539]: master/db.192.168.3:4: no TTL specified; u
> >>>sing SOA MINTTL instead
> >>>Jan  6 21:08:43 soekris named[24539]: zone 3.168.192.in-addr.arpa/IN: loaded ser
> >>>ial 2006010506
> >>>Jan  6 21:08:43 soekris named[24539]: 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.ARPA/IN: loaded serial 20051218
> >>>Jan  6 21:08:43 soekris named[24539]: 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.INT/IN: loaded serial 20051218
> >>>Jan  6 21:08:43 soekris named[24539]: running
> >>>Jan  6 21:08:48 soekris named[24539]: dumpdb started
> >>>Jan  6 21:08:48 soekris named[24539]: dumpdb complete
> >>>
> >>>
> >>>
> >>>	What/where are my zones??
> >>>
> >>
> 
> They're all there. What were you looking for?
>
	Ok. And it looks like that if I do an nslookup for it, it
resolves it... But if I do other things that should be resolving it, it
doesn't.  

	Like right now (I'm not where I can use the 192.X.X) if I do a "w",
I get :

soekris# time w
10:20PM  up 3 days, 12:53, 1 user, load averages: 0.27, 0.13, 0.10
USER             TTY      FROM              LOGIN@  IDLE WHAT
tuc              p0       10.2.0.1          1:11AM     - w
0.016u 0.024s 0:00.04 75.0%     20+345k 0+0io 0pf+0w

	If I load the zone :

zone "0.2.10.in-addr.arpa" {
        type master;
        file "master/db.10.2.0";
}

;
;SOA Record
;
0.2.10.in-addr.arpa. IN SOA soekris.tucs-beachin-obx-house.com. postmaster.soekris.tucs-beachin-obx-house.com.  (
        2006010506      ; Serial
        10800           ; Refresh after 3 hours
        3600            ; Retry after 1 hour
        86400   ; Expire after 1 day
        86400 ) ; Minimum TTL of 1 day
;
; NS Records
;
0.2.10.in-addr.arpa.            IN NS soekris.tucs-beachin-obx-house.com.
;
; PTR
;
1.0.2.10.in-addr.arpa.          IN PTR vjofnvpn.tucs-beachin-obx-house.com.
2.0.2.10.in-addr.arpa.          IN PTR soekrisvpn.tucs-beachin-obx-house.com.


Jan  9 22:22:31 soekris named[24539]: loading configuration from '/etc/namedb/named.conf'
Jan  9 22:22:31 soekris named[24539]: master/db.10.2.0:4: no TTL specified; using SOA MINTTL instead
Jan  9 22:22:31 soekris named[24539]: zone 0.2.10.in-addr.arpa/IN: loaded serial 2006010506


soekris# time w
10:22PM  up 3 days, 12:55, 1 user, load averages: 0.02, 0.08, 0.08
USER             TTY      FROM              LOGIN@  IDLE WHAT
tuc              p0       10.2.0.1          1:11AM     - w
0.007u 0.038s 0:08.45 0.3%      110+670k 0+0io 0pf+0w


	It seems to take longer, but still isn't seeming to resolve.

		Thanks, Tuc 
> Danny
> 
> >>What's in the file?: /etc/namedb/named.conf that it loaded?
> >>
> >>Danny
> >>
> > 
> > options {
> >         directory       "/etc/namedb";
> >         pid-file        "/var/run/named/pid";
> >         dump-file       "/var/dump/named_dump.db";
> >         statistics-file "/var/stats/named.stats";
> >         listen-on       { 127.0.0.1; };
> > };
> > 
> > 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.ARPA" 
> > {
> >         type master;
> >         file "master/localhost-v6.rev";
> > };
> > 
> > // RFC 1886 -- deprecated
> > 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.INT" {
> >         type master;
> >         file "master/localhost-v6.rev";
> > };
> > 
> > zone "3.168.192.in-addr.arpa" {
> >         type master;
> >         file "master/db.192.168.3";
> > };
> > 
> > 
> > 		Tuc/TBOH
> > 
> > 
> > 
> 
>