Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!moxie!texbell!root From: root@texbell.sbc.com (Greg Hackney) Newsgroups: comp.sys.ncr Subject: Re: TCP/IP Message-ID: <490@texbell.sbc.com> Date: 25 Sep 90 23:30:43 GMT References: <90266.153616TEMNGT23@ysub.ysu.edu> Organization: Southwestern Bell Lines: 40 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: -------- ; 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 --------- ; 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