Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!olivea!apple!agate!shelby!msi.umn.edu!cs.umn.edu!peiffer From: peiffer@cs.umn.edu (Tim Peiffer (The Net Guy)) Newsgroups: comp.protocols.tcp-ip Subject: Re: Nameservice questions Message-ID: <1990Oct6.035625.29037@cs.umn.edu> Date: 6 Oct 90 03:56:25 GMT References: <465@bcstec.UUCP> Organization: University of Minnesota, Minneapolis - CSCI Dept. Lines: 42 In article <465@bcstec.UUCP> ced@bcstec.uucp (Charles Derykus) writes: > (1) Can nameservice resolve reverse translation queries "up the tree" > towards the root domain if the domains of the requested node and > the requesting node are at the same level, e.g. [...} > can "carrot" ask "cabbage" to reverse translate an I.P. in > "herb.vegetable" and if so, how? Yes, you can forward unresolved entries (those not in your domain or in your secondary zones) by using the forwarding construct in named.boot. ; forward name-service request when we can't (won't) handle them forwarders first_forwarder_ipaddr second_forwarder_ipaddr > (2) A named.rev with multiple $ORIGIN lines worked fine on out primary > nameserver for a while but then the secondary nameserver starting > breaking. The only way we get it working now is by specifying separate > reverse translation files for each $ORIGIN line, e.g. I do not really understand. I would answer your question with no. The in-addr.arpa domain is rather unusual and should be treated differently than most others. The declaration in named.boot specifies service for a particular domain. I think that your declaration would break unless it were of the following form: named.boot ---------- primary 207.128.in-addr.arpa. herb.file_name herb.file_name ---------- $ORIGIN 254.207.128.in-addr.arpa. 44 IN PTR parsley.herb.blah.blah. $ORIGIN 253.207.128.in-addr.arpa. 1 IN PTR oregano.herb.blah.blah. Tim -- ----------- Tim Peiffer peiffer@cs.umn.edu or Computer Science Dept ..!rutgers!umn-cs!peiffer University of Minnesota