home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.domains
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!gatekeeper.es.dupont.com!wind.es.dupont.com!minnich
- From: minnich@wind.es.dupont.com (Mike Minnich)
- Subject: 2-level forwarders
- Message-ID: <1992Jul30.183536.22451@es.dupont.com>
- Sender: news@es.dupont.com (USENET News System)
- Nntp-Posting-Host: wind.es.dupont.com
- Organization: DuPont Experimental Station
- Distribution: na
- Date: Thu, 30 Jul 1992 18:35:36 GMT
- Lines: 32
-
- I've got a question around the use of the "forwarder" mode of bind.
-
- Let's say I have a bind server that can talk to the Internet, and several
- other bind servers responsible for various subdomains that cannot:
-
- [internet]
- |
- |
- bind server #1
- (primary foo.com)
- (secondary a.foo.com)
- (secondary b.foo.com)
- |
- |
- [other gateways]
- |
- |
- bind server #2 bind server #3 ...
- (primary a.foo.com) (primary b.foo.com)
- (secondary foo.com) (secondary foo.com)
- (forwarder bind server #1) (forwarder bind server #1)
-
- Initial testing shows that server #2 resolves
- queries within b.foo.com by sending a recursive query to server #1 if
- the complete answer is not cached in #2. One would expect that since
- #2 is secondary for foo.com it has knowledge of the NS records
- and therefore ought to ask #3 directly.
-
- Is there an alternative configuration that would achieve the desired effect?
-
- --
- Mike Minnich minnich@wind.es.dupont.com
-