rob@cs.aukuni.ac.nz (Rob Burrowes ) (04/09/91)
Our domain is cs.aukuni.ac.nz and the server(s) look after addresses
130.216.32.x through 130.216.39.x. These being subnets 32 - 39 of 130.216.
The domain aukuni.ac.nz is looks after all other subnets of 130.216.
My problem is obtaining the hostname from the address using the IN-ADDR.ARPA
domain. How do we tell aukuni.ac.nz's BIND server and our BIND server that
request for the hostname of say 130.216.34.2 should be directed to the
cs.aukuni.ac.nz. server while requests for 130.216.1.2 should be handled by
the aukuni.ac.nz server. Currently aukuni.ac.nz's server attemps to handle
such requests and of course fails.
2.
What is the line "sortlist 10.0.0.0" in the named.boot file for? I couldn't
see any doc which would tell me. (It was in an example named.boot file).
rob@cs.aukuni.ac.nz
Rob Burrowes
--
Rob Burrowes rob@cs.aukuni.ac.nz.
System Admin
Computer Science Dept., Auckland University, Private Bag, Auckland, New Zealand
--
New administrater uofa.jcurran@SH.CS.NET (John Curran) (04/10/91)
-------- From: Rob Burrowes <waikato.ac.nz!aukuni.ac.nz!rob@decwrl.dec.com> > Our domain is cs.aukuni.ac.nz and the server(s) look after addresses > 130.216.32.x through 130.216.39.x. These being subnets 32 - 39 of 130.216. > > The domain aukuni.ac.nz is looks after all other subnets of 130.216. > > My problem is obtaining the hostname from the address using the IN-ADDR.ARPA > domain. How do we tell aukuni.ac.nz's BIND server and our BIND server that > request for the hostname of say 130.216.34.2 should be directed to the > cs.aukuni.ac.nz. server while requests for 130.216.1.2 should be handled by > the aukuni.ac.nz server. Currently aukuni.ac.nz's server attemps to handle > such requests and of course fails. Always fun. Presuming that you're using a 255.255.255.0 subnet mask, then you can delegate nameservice for each associated 216.130.IN-ADDR.ARPA subdomain to cs.aukuni.ac.nz. In the zone file for 216.130.IN-ADDR.ARPA on aukuni.ac.nz: 32 IN NS cs.aukuni.ac.nz. 33 IN NS cs.aukuni.ac.nz. 34 IN NS cs.aukuni.ac.nz. 35 IN NS cs.aukuni.ac.nz. 36 IN NS cs.aukuni.ac.nz. 37 IN NS cs.aukuni.ac.nz. 38 IN NS cs.aukuni.ac.nz. 39 IN NS cs.aukuni.ac.nz. and then setup cs.aukini.ac.nz as primary for each of these subdomains and create the appropriate zone files. You should not make cs.aukini.ac.nz a primary for the 216.130.IN-ADDR.ARPA domain, but only the subdomains: In the named.boot file for cs.aukini.ac.nz: primary 32.216.130.IN-ADDR.ARPA named.cs-32-inaddr.db primary 33.216.130.IN-ADDR.ARPA named.cs-33-inaddr.db primary 34.216.130.IN-ADDR.ARPA named.cs-34-inaddr.db ... If you are using a subnet mask of less than 24 bits, this system will still work (although you have delegate multiple IN-ADDR domains for each IP subnet). If you are using a subnet mask with greater than 24 bits, then each IN-ADDR delegation actually reflects a "block" of IP subnets; hopefully, the IP subnets have been passed out in matching blocks.. :-) > What is the line "sortlist 10.0.0.0" in the named.boot file for? I couldn't > see any doc which would tell me. (It was in an example named.boot file). There's a few words regarding the sortlist directive in man/named.8. It is used to order in which A records appear in replies. If you have multiple IP addresses on many hosts, you may use sortlist to encourage the world to use interfaces on one network over another. /John
karrer@bernina.ethz.ch (Andreas Karrer) (04/11/91)
rob@cs.aukuni.ac.nz (Rob Burrowes ) writes: >Our domain is cs.aukuni.ac.nz and the server(s) look after addresses >130.216.32.x through 130.216.39.x. These being subnets 32 - 39 of 130.216. I assume your subnet mask is 255.255.255.0. >The domain aukuni.ac.nz is looks after all other subnets of 130.216. >My problem is obtaining the hostname from the address using the IN-ADDR.ARPA >domain. How do we tell aukuni.ac.nz's BIND server and our BIND server that >request for the hostname of say 130.216.34.2 should be directed to the >cs.aukuni.ac.nz. server while requests for 130.216.1.2 should be handled by >the aukuni.ac.nz server. Currently aukuni.ac.nz's server attemps to handle >such requests and of course fails. The problem is that the DNS has no concept of IP subnetting. I guess in your case you could have a SOA field for each subnet, e.g. the cs.aukuni.ac.nz servers would have 8 SOA RR's as in: $ORIGIN 32.216.130.in-addr.arpa. @ IN SOA .... in their reverse tables, whereas the aukuni.ac.nz servers would have authority SOA RR's for the other 246 subnets. Clumsy, but manageable. But then, what do you do if your subnet mask is 255.255.255.192 as ours? +----------- Andi Karrer, Communication Systems, ETH Zuerich, Switzerland karrer@bernina.ethz.ch karrer@czheth5a.bitnet /S=karrer/OU=bernina/O=ethz/PRMD=SWITCH/ADMD=ARCOM/C=CH/
Christopher-Vance@adfa.oz.au (Christopher JS Vance) (04/12/91)
In article <1991Apr11.090926.24784@bernina.ethz.ch> karrer@bernina.ethz.ch (Andreas Karrer) writes: | rob@cs.aukuni.ac.nz (Rob Burrowes ) writes: | | >Our domain is cs.aukuni.ac.nz and the server(s) look after addresses | >130.216.32.x through 130.216.39.x. These being subnets 32 - 39 of 130.216. | The problem is that the DNS has no concept of IP subnetting. I guess in your | case you could have a SOA field for each subnet, e.g. the cs.aukuni.ac.nz | servers would have 8 SOA RR's as in: | | $ORIGIN 32.216.130.in-addr.arpa. | @ IN SOA .... | | in their reverse tables, whereas the aukuni.ac.nz servers would have authority | SOA RR's for the other 246 subnets. Clumsy, but manageable. But you only need to delegate the ones not served by aukuni.ac.nz. The undelegated subnets are already part of the parent zone, and are already handled adequately by aukuni.ac.nz. There is no requirement of symmetry. Rob already has his DNS working properly now. -- Christopher
rob@cs.aukuni.ac.nz (Rob Burrowes ) (04/12/91)
>>rob@cs.aukuni.ac.nz (Rob Burrowes ) writes: (me) >>Our domain is cs.aukuni.ac.nz and the server(s) look after addresses >>130.216.32.x through 130.216.39.x. These being subnets 32 - 39 of 130.216. >>The domain aukuni.ac.nz is looks after all other subnets of 130.216. >>My problem is obtaining the hostname from the address using the IN-ADDR.ARPA >>domain. How do we tell aukuni.ac.nz's BIND server and our BIND server that >>request for the hostname of say 130.216.34.2 should be directed to the >>cs.aukuni.ac.nz. server while requests for 130.216.1.2 should be handled by >>the aukuni.ac.nz server. Currently aukuni.ac.nz's server attemps to handle Thanks to everyone who replied. $origin x.216.130.in-addr.arpa. RMD=SWITCH/ADMD=ARCOM/C=CH/ @ SOA ... for each of the subnets and had aukuni.ac.nz.'s servers put NS records in for each subnet. and it all seems to be working. In karrer@bernina.ethz.ch (Andreas Karrer) writes: >But then, what do you do if your subnet mask is 255.255.255.192 as ours? In RFC 1101 I read of a scheme for naming of nets and subnets using PTR RR's eg. 0.0.216.130.IN-ADDR.ARPA IN PTR aukuni.ac.nz. IN A 255.255.255.0 0.33.216.130.IN-ADDR.ARPA. IN PTR cs-grad.cs.aukuni.ac.nz. Perhaps by extending this to include NS records eg. 0.0.216.130.IN-ADDR.ARPA IN PTR aukuni.ac.nz. IN A 255.255.255.0 IN NS ccu1.aukuni.ac.nz 0.33.216.130.IN-ADDR.ARPA. IN PTR cs-grad.cs.aukuni.ac.nz. IN NS cs18.cs.aukuni.ac.nz. etc. That way a 255.255.255.192 subnet could specify nameservers. Reverse address searches would then follow the same sort of search outlined in rfc 1101 and having found the net or subnet look for NS RR's. -- Rob Burrowes rob@cs.aukuni.ac.nz. System Admin Computer Science Dept., Auckland University, Private Bag, Auckland, New Zealand -- New administrater uofa.
Mark.Berryman@Mvb.Saic.Com (MUMPS Wizard) (04/14/91)
We solved this particular problem by having a program that periodically polls appropriate domain servers within the company for all of their type A records and builds the master file for the reverse address pointers. This data is then served to the outside world by the primary servers and internally by any server that wishes to set itself up as a secondary for it. There are, of course, enough filters so that only type A's that are within one of the company networks are used and the master file is only updated if something changes. Mark Berryman Mark.Berryman@Mvb.Saic.Com
gah@hood.hood.caltech.edu (Glen Herrmannsfeldt) (04/14/91)
Regarding reverse lookups for sub 24bit subnets.... We recently had a similar problem, in that our group was given aouthority for certain addresses on the main network, as well as our own subnets. I wanted reverse lookup authority for those addresses. It was actually 50 addresses. I had the net admin. put in CNAME records, pointing to a subdomain of the applicable in-addr domain. Specifically, origin 4.215.131.in-addr.arpa 151 CNAME 151.hood note that no period after either. This adds the current domain to each entry. I always thouht that the required periods after fully qualified names (such as PTR names) were dumb, but it works nice here. Anyway, then I got authority for hood.4.215.131.in-addr.arpa, and everything works fine. If you want to see it, nslookup set debug set type=ptr 171.4.215.131.in-addr.arpa There was some discussion before doing this, about how fast it was, and whether there were other ways. Since the primary for 215.131.in-addr.arpa is secondary for us, I think it is all cached, anyway. Another suggestion was to put NS records in for all of them. This may have worked, but I was worried about overflowing some table of NS records. named should be designed for lots of CNAMEs, but not necessarily for lots of NS's. Anyway, it works, and no complaints. -- glen