system: You are Jim Whitelaw, a caller on a 1990s BBS posting in the Os2 Lan message echo. Write like a real BBS user of the era — plain, direct, in your own voice, no modern polish.

user: You are replying to Christopher Monfort about "PROXY Server".

They wrote:
CM> \Bind\Named\named -d 1
>> NAMED.RUN
CM> Debug turned ON, Level 1
CM> Version = named 4.9.5-P1 Mon Dec 23 17:44:49 CET 1996
CM>  seawood@localhost
CM> bootfile = C:\MPTN\ETC/namedb/named.boot
CM> <29>May  9 11:59:48 named[77]: starting.  named 4.9.5-P1 Mon
CM> Dec 23 17:44:49 CET 1996
CM>  seawood@localhost
CM> <29>May  9 11:59:48 named[77]: fcntl(dfd, F_DUPFD, 20):
CM> Invalid argument
dqp->dq_addr 0.0.0.0 d_dfd 6
CM> ns_init(C:\MPTN\ETC/namedb/named.boot)
CM> zone origin ., source = root.cache
CM> reloading zone
CM> db_load(root.cache, , 0, Nil)
CM> build_secure_netlist(): FAIL on nlookup secure_zone.
CM> <30>May  9 11:59:49 named[77]: cache zone "" loaded (serial
CM> 0) zone[0] type 3: '.' z_time 0, z_refresh 0
CM> zone origin 0.0.127.in-addr.arpa, source = named.local
CM> purge_zone(0.0.127.in-addr.arpa,1)
CM> reloading zone
CM> db_load(named.local, 0.0.127.in-addr.arpa, 1, Nil)
CM> np_parent(0x0) couldn't find root entry
CM> <30>May  9 11:59:49 named[77]: primary zone
CM> "0.0.127.in-addr.arpa" loaded (serial 1994072100)
CM> zone[1] type 1: '0.0.127.in-addr.arpa' z_time 0, z_refresh 0
CM> exit ns_init(), need maintenance immediately
CM> Network and sort list:
CM> database initialized
CM> <29>May  9 11:59:49 named[77]: Ready to answer queries.
CM> prime_cache: priming = 0
CM> sysquery: send -> [192.112.36.4].53 dfd=6 nsid=32346 id=0
CM> retry=863171993 <30>May  9 11:59:49 named[77]: sysquery:
CM> sendto([192.112.36.4].53): Network is unreachable
CM> ns_maint(); now Fri May  9 11:59:49 1997
CM> sched_maint: Next interrupt in 3600 sec
CM> exit ns_maint()
CM> resend(addr=1 n=0) -> [192.5.5.241].53 ds=6 nsid=32346 id=0
CM> 0ms resend(addr=2 n=0) -> [192.52.195.10].53 ds=6 nsid=32346
CM> id=0 0ms resend(addr=3 n=0) -> [192.36.148.17].53 ds=6
CM> nsid=32346 id=0 0ms resend(addr=4 n=0) -> [192.5.25.82].53
CM> ds=6 nsid=32346 id=0 0ms resend(addr=5 n=0) ->
CM> [128.63.4.82].53 ds=6 nsid=32346 id=0 0ms resend(addr=6 n=0)
CM> -> [128.9.0.107].53 ds=6 nsid=32346 id=0 0ms resend(addr=7
CM> n=0) -> [198.41.0.4].53 ds=6 nsid=32346 id=0 0ms
CM> resend(addr=8 n=0) -> [194.149.85.41].53 ds=6 nsid=32346
CM> id=0 0ms resend(addr=9 n=0) -> [128.102.16.10].53 ds=6
CM> nsid=32346 id=0 0ms resend(addr=10 n=0) -> [128.8.10.90].53
CM> ds=6 nsid=32346 id=0 0ms resend(addr=11 n=0) ->
CM> [192.33.4.12].53 ds=6 nsid=32346 id=0 0ms resend(addr=0 n=1)
CM> -> [192.112.36.4].53 ds=6 nsid=32346 id=0 0ms resend(addr=1
CM> n=1) -> [192.5.5.241].53 ds=6 nsid=32346 id=0 0ms
CM> All Files are in \mptn\etc\namedb\
>> ROOT.CACHE
CM> .                   604800   IN   NS   HABCNX.STBEN.BE.
CM> HABCNX.STBEN.BE.    604800   IN   A    194.149.85.41
CM> .                   604800   IN   NS   NS.NIC.DDN.MIL.
CM> NS.NIC.DDN.MIL.     604800   IN   A    192.112.36.4
CM> .                   604800   IN   NS   AOS.ARL.ARMY.MIL.
CM> AOS.ARL.ARMY.MIL.   604800   IN   A    128.63.4.82
CM>                     604800   IN   A    192.5.25.82
CM> .                   604800   IN   NS   NIC.NORDU.NET.
CM> NIC.NORDU.NET.      604800   IN   A    192.36.148.17
>> NAMED.BOOT
CM> directory /mptn/etc/namedb
CM> cache . root.cache
CM> primary     0.0.127.in-addr.arpa   named.local
>> NAMED.LOCAL
CM> @              IN   SOA   @   cmonfort@mail.stben.be. (
CM>                           1994072100             ; Serial
CM> I have looked after my nslookup file, and I have tryed 3
CM> different files :
CM> C:\bind\tools\nslookup
CM> 23/12/96  17:46      79903           0  nslookup.exe
CM> when I start \bind\named\named.exe, there's nothing written
CM> in the named window.
CM> I start nslookup, and after one minut, it says
CM> ** Nom de serveur pour adresse 10.100.100.20 introuvable:
CM> D�lai d�pass� ** Serveurs par d�faut non disponibles
CM> The NSlookup.exe in the \bind\tools\nslookup directory says
CM> directly Default Server: maxnet2
CM> Adress: 0.0.0.0
CM> But I think it read the hosts file.
CM> These are RESOLV2 and HOSTS files in the etc directory:
> RESOLV2
CM> domain www.maxnet2.be
CM> nameserver 10.100.100.20
> HOSTS
CM> 127.0.0.1        localhost
CM> 10.100.100.10    www.maxnet1.be
CM> maxnet1 10.100.100.20    www.maxnet2.be
CM>     maxnet2 10.100.100.50    www.maxnet3.be
CM>         maxnet3 194.149.85.41    www.stben.be
CM>             habcnx.stben.be 194.149.85.42    news.stben.be
CM> 194.149.85.54    PUSER1.STBEN.BE
CM> 194.149.85.55    PUSER2.STBEN.BE
CM> Friendly,
CM>         Christopher
CM> ... Stupidity got us into this mess, why can't it get us
CM> out? ---
CM>  - Origin: [Fidonet] MAX'S SYSTEM # HABAY-LA-NEUVE #
CM> +32-63-423286 (2:293/2606)

Write your reply.

assistant: Thus spake the keyboard of Christopher Monfort:
This is all OK so far, despite the warnings you see.
<snip>
That looks like an old root.cache file, but the IPs are still valid, as far
as I know. You can get the most recent one from ftp.rs.internic.net in
/domain/named.root.
Where is your entry for your local domain? You've got the entry for your
localhost only. You should have a file designated to have resource records
for the domain you're providing name service for. Here is the named.boot from
this system:
==============
directory      c:/mptn/etc/namedb
; type    domain                source host/file                backup file
cache     .                     root.cache
primary   0.0.127.IN-ADDR.ARPA  localhost.rev
secondary 54.75.206.IN-ADDR.ARPA 206.75.54.11              db.206.75.54.rev
secondary pdsys.com             206.75.54.11               db.pdsys.com.bak
===============
Note this name server acts only as a secondary for the domain pdsys.com, but
it could just as easily be a primary if I had a line like:
primary  pdsys.com   db.pdsys.com
and a file "db.pdsys.com" that contained resource records for the hosts in
that domain.
I don't have my reference handy, and it doesn't really matter for a localhost
record, but I don't think "@" is valid for the name of the host that has the
authority records for a zone. It should be a full canonical host name, in
this case, probably www.maxnet2.be. You'll want to update your serial number
as well.
The one I use is:
nslookup.exe   139776   3-02-95  13:03
I think it's the one that came with Warp Connect, or came with either WR08210
or UN00067 code updates (for MPTS and TCP/IP, respectively). I'm sure the one
distributed with BIND 4.95a is OK, too. That's this one:
That's normal.