TEMNGT23@ysub.ysu.edu (Lou Anschuetz) (09/24/90)
OK, I have WIN TCP/IP installed and functioning on my tower 32/700. I can telnet in and out successfully using source routing. What I need to know how to do is to tell the NCR to use the name server located on another machine, and how to tell the NCR to use a default router address for anything not in /etc/hosts.... Help - I'm real new to TCP/IP Lou Anschuetz aka temngt23@ysu.edu or temngt23@ysub.bitnet
root@texbell.sbc.com (Greg Hackney) (09/24/90)
In article <90266.153616TEMNGT23@ysub.ysu.edu> TEMNGT23@ysub.ysu.edu (Lou Anschuetz) writes: >OK, I have WIN TCP/IP installed and functioning on my tower 32/700. >I can telnet in and out successfully using source routing. What I >need to know how to do is to tell the NCR to use the name server >located on another machine I don't think that NCR's WIN-TCP package supports nameservice yet. The INTRO(3&4) networking manual pages refer to the RESOLVER(3&4) manual pages, which are not in the manual. There is a /usr/etc/named file, but I couldn't find any supportive documentation. The "bind" (Berkeley Internet Name Domain server) source code is available for free via FTP on uunet.uu.net. It can be made to compile and run on NCR's WIN TCP/IP, and I am using it. However it appears that most of NCR's networking utilities, i.e. rlogin, ftp, telent, are not linked with the resolver libraries, therefore will only work with /etc/host entries. I'm not if NCR's sendmail was built to use nameservice, as I use Smail3 instead. > and how to tell the NCR to use a default > router address for anything not in /etc/hosts.... If you have a router that is an internet gateway, you can put a line in /etc/rc1.d/S86win that says: /usr/etc/route add default router_name 0 If you are just talking about email routing, normally your nameserver feature will determine addresses sites not in /etc/hosts. If you don't have nameservice, then the normal thing to do is to configure /usr/lib/sendmail.cf to forward SMTP mail to an email gateway machine. -- Greg
root@texbell.sbc.com (Greg Hackney) (09/26/90)
In article <90266.153616TEMNGT23@ysub.ysu.edu> TEMNGT23@ysub.ysu.edu (Lou Anschuetz) writes: >need to know how to do is to tell the NCR to use the name server >located on another machine Normally, one way to do it is to put entries in the file /etc/resolv.conf. Assuming your domain is "ysu.edu" and the primary and secondary nameservers are ysub.ysu.edu and opus.ysu.edu, the file would consist of: domain ysu.edu nameserver 192.55.234.10 nameserver 192.55.234.13 NCR's /usr/etc/named does work, so another way is to declare yourself as an unofficial secondary nameserver for your own machine's use: ----</etc/named.boot>---- ; type domain source host/file capture file cache . /etc/root.cache secondary ysu.edu 192.55.234.10 192.55.234.13 /etc/ysu.bak secondary 55.192.IN-ADDR.ARPA 192.55.234.10 192.55.234.13 /etc/ysu.rev.bak -----</etc/root.cache>---- ; Initial cache data for root domain servers. ; . 99999999 IN NS NS.NASA.GOV. 99999999 IN NS NS.NIC.DDN.MIL 99999999 IN NS C.NYSER.NET. 99999999 IN NS BRL-AOS.ARPA 99999999 IN NS A.ISI.EDU. ; Prep the cache (hotwire the addresses). Order does not matter NS.NASA.GOV. 99999999 IN A 128.102.16.10 NS.NIC.DDN.MIL. 99999999 IN A 192.67.67.53 C.NYSER.NET. 99999999 IN A 128.213.5.17 BRL-AOS.ARPA. 99999999 IN A 128.20.1.2 A.ISI.EDU. 99999999 IN A 26.3.0.103 Then, execute /usr/etc/named manually as root, or reboot the system. -- Greg