Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.sdsmt.edu!nntp.uac.net!news.tufts.edu!blanket.mitre.org!news.mathworks.com!newsfeed.internetmci.com!torn!nott!nntp.igs.net!usenet From: cskinner@bml.ca (Chris K. Skinner) Newsgroups: comp.unix.bsd.freebsd.misc,list.freebsd-questions,local.freebsd.questions Subject: Re: FreeBSD 2.1 Documentation and Installation of "Everything" to 2.1 Gig drive. Date: Thu, 30 May 1996 04:45:58 GMT Organization: Bytown Marine Limited, Nepean/Kanata, Ont, Canada Lines: 123 Message-ID: <4oj99s$6ml@nntp.igs.net> NNTP-Posting-Host: ttya07.ott.igs.net X-Newsreader: Forte Free Agent 1.0.82 Hi. Latest update: Samba permits partial then, later, full browse and functionality. >cc of this news msg was given to >"Jordan K. Hubbard" <jkh@FreeBSD.org> via e-mail for FYI >anecdotal purposes and for further questions below... With samba files left as last reported in my previous news article, and a bit more tinkering with DNS config files for the reverse .IN-ADDR.ARPA stuff seems to, eventually, have all of samba operational now. I was proceeding to try to get nslookup to not have that the default server was unix.bml.ca (our LAN stuff) with an address of 0.0.0.0. on the nslookup startup. Step 1 was to tinker with the "named" setup config files. Step 2 was to kill the existing "named" process and re- start a new one to test the changes. Within step 2, I found that the named-re-start produced the following diagnostic messages that WERE _NOT_ previously visible on the console when "named" was started automatically at boot time: unix.bml.ca named[262] starting named .... LOCAL-951116.090057 Thu Nov 16 09:00:57 1995 jkh@westhill.cdrom.com /usr/src/usr.sbin/named named[262] ... ZONE "0.0.127.IN-ADDR.ARPA" (file localhost.rev) has no NS RRs found at ZONE top. named[262] ... ZONE "0.0.10.IN-ADDR.ARPA" (file named.rev) has no NS RRs found at ZONE top. (or messages of very similar wordings). When "named" started, it complained that the reverse lookup tables did not have a Name Server Resource Record for the top of the given zone for both of the two .IN-ADDR.ARPA references that I had given in the /etc/namedb/named.boot config file. My problem was that I had a dummy host as the top of the zone/origins of both of the files, and at a reverse lookup offset of 1.0, I put my unix box as the name server. To correct this, I changed the origin to be the unix box "unix.bml.ca." instead of the dummy "bml.ca" and changed all the IP address relative offsets by -1 from their previous values--ie., start at 0.0, then 1.0, then 2.0, then 3.0 and up. I still get that the default server is unix.bml.ca with address 0.0.0.0, but samba nmbd seems to announce the machine shares to other machines who are running tcp/ip. Host name "UNIX" with comment "Samba 1.9.14" appears on the Dos/WFWG 3.11 connect network drive browse dialog. The first time when I click on this list box entry for host "UNIX" the Dos/Windows computer went into hour glass mode for 30 seconds or so, then reported that "Network Busy" as the result, and listed no share names in the shared directory list box at the bottom of the dialog. Further tinkering with the "named" _forward_ lookup config tables and the root servers config file seems to have overcome this last hurdle: now clicking on the host "UNIX" gives immediate response of the available share names! Getting named's config files in better shape, fixed samba's final troubled areas. The prior samba config process that I undertook that followed closely the teaching of the man pages for all of smbd and nmbd and the inetd.conf config files turned out all to be required and good. That samba config'ing overcame any botch-ups of my own making and that of the install software from my various runnings of the sysinstall process from boot floppy or hard disk. Finally, one 'problem' remaining is that of the nslookup still giving that the default NS of unix.bml.ca displaying an address of 0.0.0.0 Can anybody able to tell me if the nslookup of FreeBSD 2.1.0 Jan'96 is supposed to have 0.0.0.0 as a viable displayed default NS address, when the NS's address is really 10.0.0.1? The good 10.0.0.1 address is reported by nslookup when "nslookup unix.bml.ca" is executed--so I still don't know if this is right or not... Things that I am considering doing: try the automated hosts to named config perl script that produces both forward and reversed lookup config files for named. The www site "DNS Tools" at http://www.dns.net/dnsrd/tools.html has this h2n script: * h2n to generate forward and reverse zone files from /etc/hosts; described in the cricket book. ftp://ftp.uu.net/published/oreilly/nutshell/dnsbind/dns.tar.Z ftp://ftp.is.co.za/networking/ip/dns/cricketbook/dns.tar.Z dnswalk and makezones are other programs that I'm considering trying out that are from the same www page source. >Possible bug considerations: Why didn't the named startup at boot time not display the helpful/meaningful diagnostic messages that happened when manual startup was done?--or if logged elsewhere, then perhaps they should be elevated in priority and be displayed/logged similar to other console error/warning messages? TIA. Regards, Chris K. Skinner.