ced@bcstec.uucp (Charles Derykus) (10/04/90)
I have several questions regarding nameserver:
(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.
Nameserver Node Domain
--------------- ------
cabbage vegetable
parsley herb.vegetable
carrot underground.vegetable
can "carrot" ask "cabbage" to reverse translate an I.P. in
"herb.vegetable" and if so, how?
We have gotten it to work only by specifying in the named.boot
on carrot a line like the one below where 192.33.72.10 is the
I.P. of parsley
secondary 72.33.192.in-addr-arpa 192.33.72.10 herb.bak
In other words, carrot seems to have to know that parsley is
authoratative for the herb.vegetable domain and doesn't seem to be
able to pull it down from a server such as cabbage in a higher
domain.
(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.
in the primary's named.boot:
primary 207.128.in-addr.arpa herb.207.128.in-addr.arpa
primary 79.33.192.in-addr.arpa herb.79.33.192.in-addr.arpa
in the secondary's named.boot: (primary's I.P. is 128.207.254.44)
secondary 207.128.in-addr.arpa 128.207.254.44
secondary 79.33.192.in-addr.arpa 128.207.254.44
Does nameservice break if these separate reverse files exceed some
limit- either in number of files or memory capacity- as the
"named.rev" file apparently does?
Thanks for listening. Any help greatly appreciated.
Charles DeRykus Internet: ced@bcstec.boeing.com
Boeing Computer Services UUCP: ...!uunet!bcstec!ced
Renton, WA. M/S 6R-37 (206) 938-4520 (home)
(206) 234-9223peiffer@cs.umn.edu (Tim Peiffer (The Net Guy)) (10/06/90)
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