home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!sh.wide!wnoc-tyo-news!ccut!wsclark!lab!lab!canning
- From: canning@apollo3.apollo3.ntt.JP (John M. Canning)
- Newsgroups: comp.sys.apollo
- Subject: BSD named questions
- Message-ID: <34a.e6psp@lab.ntt.jp>
- Date: 27 Aug 92 08:12:56 GMT
- Sender: news@lab.ntt.jp
- Distribution: comp
- Organization: none
- Lines: 33
-
-
- I've just enabled the name sever daemon (named) on two of our
- Apollo workstations. I set them up as caching name servers with
- pointers to our primary and secondary name servers. This works well
- and we can now translate host names that aren't in our /etc/hosts
- file.
-
- Unfortunately, NTT is such a huge place that the primary and
- secondary name servers don't have all the latest info about all the
- workstations throughout the company. Is there a way to enter some
- local correction info so that when a translation fails, it can look in
- the local file? Or better yet, check the local file first and if
- nothing was found, then query the remote name server? In reading the
- documentation, it seems that the /etc/hosts file system and the remote
- name server are mutually exclusive systems.
-
- Another question: one of the "named" servers correctly appends our
- local domain name (.ntt.jp) to the requests that need it, but the
- other doesn't. The configuration files (named.boot, named.ca, and
- named.local) are identical on both machines. What controls the
- appending of the local domain name?
-
- - John Canning
-
- --
- //////////\\\\\\\\\\//////////\\\\\\\\\\//////////\\\\\\\\\\//////////\\\\\\\\
- Dr. John M. Canning
- s-mail: Naito Group e-mail: canning@apollo3.ntt.jp
- NTT Basic Research Laboratories tel: (0422)-59-4640
- 3-9-11 Midori-cho fax: (0422)-59-2178
- Musashino-shi, Tokyo 180 JAPAN (outside Japan:
- change leading 0 to 81)
- //////////\\\\\\\\\\//////////\\\\\\\\\\//////////\\\\\\\\\\//////////\\\\\\\\
-