Date: Sun, 14 Dec 1997 17:38:48 -0500 (EST) From: Dan Jacobowitz <drow@drow.net> To: Jim Shankland <jas@flyingfox.com> Cc: hackers@FreeBSD.ORG Subject: Re: weird IP address Message-ID: <Pine.BSF.3.96.971214173517.29424A-100000@mars.abcinternet.net> In-Reply-To: <199712142040.MAA25208@biggusdiskus.flyingfox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 14 Dec 1997, Jim Shankland wrote: > Marc Slemko <marcs@znep.com> writes: > > > I am saying you can use whatever IP you want for a nameserver > > when registering a domain via the InterNIC and they will not > > trying to figure out if you are authorized to use it. The > > InterNIC will list that nameserver in the DNS for that domain, > > will add a glue record for the nameserver, and will create a > > host record. You can't have multiple host records for one IP, > > though. > > Back when domain registration was free, InterNIC would actually > check the name servers you named, making sure that they were reachable > and had proper NS and SOA records for your new domain. If not, your > registration was put on hold until you fixed things. > > Now that they're charging money for the service, evidently they > can no longer afford to do this :-(. It strikes me as a little odd that InterNIC puts reverse DNS for the nameservers on their root servers - in fact, judging by my past experiences, I could ahve sworn that they did not. (In fact, hgaving just gone to check a few others, they do not) Apparently they only do so if no other NS is responsible for ther reverse range specified! Go figure. An InterNIC bug?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971214173517.29424A-100000>