Date: Sun, 19 May 1996 21:07:58 -0600 From: Nate Williams <nate@sri.MT.net> To: hackers@FreeBSD.org Subject: DNS question Message-ID: <199605200307.VAA04583@rocky.sri.MT.net>
next in thread | raw e-mail | index | archive | help
Thanks to everyone for showing me how to have control of our
sub-classed C network using the:
Classless in-addr.arpa delegation
In any case, I even got my ISP to set this up. Seems that they got a
whole bunch of addresses are were told they have to break them out into
smaller chunks, and the demand was great enough from all of us to make
them actually implement this.
OK, so they're setup to do the dirty work for us, but things don't seem
to be working correctly. I've tenatively set things up on two FreeBSD
boxes and munged on the files to have it appear that one box is the
primary for the entire class C, and the other box is the primary for the
sub-class, using the information from the above RFC.
Rather than boring everyone to death with *all* the detail, let me
summarize as best as I can.
gateway:/etc/namedb/new # nslookup
Default Server: localhost.sri.MT.net
Address: 127.0.0.1
> 206.127.76.97
Server: localhost.sri.MT.net
Address: 127.0.0.1
Name: ns.mt.sri.com
Address: 206.127.76.97
Aliases: 97.76.127.206.in-addr.arpa
> gateway:/etc/namedb/new # host 206.127.76.97
Host not found, try again.
And, using 'dnswalk' (Thanks John) there isn't any PTR records (see
results of 'host'), but nslookup can do reverse DNS.
"gateway" - Master site (Owner of the class C)
====================================
named.boot
----------
primary 76.127.206.in-addr.arpa Class-C.rev
secondary 96.76.127.206.in-addr.arpa 10.5.5.67 206.127.76.96
Class-C.rev
-----------
@ IN SOA gateway.sri.MT.net. admin.gateway.sri.MT.net. (
..
;
; Name Servers
;
IN NS gatway.sri.MT.net.
..
;
; 32 addresses (-1) for SRI-Montana
96 IN NS trout.sri.MT.net.
IN NS ns.mt.sri.com.
97 IN CNAME 97.96.76.127.206.in-addr.arpa.
....
So, 'gateway' is the primary for the entire class C, and 'trout' is the
primary for the subnet.
"trout"-Sub-net master (Owner of 32 IP #'s in the class C)
====================================
named.boot
----------
primary 96.76.127.206.in-addr.arpa sri.rev
secondary 76.127.206.in-addr.arpa 204.182.243.1 206.127.76.rev
sri.rev
-------
@ IN SOA trout.sri.MT.net. nate.trout.sri.MT.net. (
..
IN NS trout.sri.MT.net.
IN PTR networkname.mt.sri.com.
IN A 255.255.255.32
; I'm unsure of the relevance of the above two lines, but they are part
; of the RFC
;
;;; Permanent machines
;
;96 - All zero's address
97 IN PTR ns.mt.sri.com.
;98 IN PTR *.mt.sri.com.
;99 IN PTR *.mt.sri.com.
100 IN PTR rocky.mt.sri.com.
....
So, that should be enough information to let people recreate the
problem. Any clues? I'm certainly no DNS wizard, and the only reason
I'm this far along is because everyone else has been so helpful.
Thanks!
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605200307.VAA04583>