Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!alpha.sky.net!news.sprintlink.net!new-news.sprintlink.net!newsfeed.internetmci.com!in2.uu.net!EU.net!Germany.EU.net!Dortmund.Germany.EU.net!nntp.gmd.de!news.rwth-aachen.de!news.ruhr-uni-bochum.de!news.uni-stuttgart.de!uni-regensburg.de!newsserv.uni-bayreuth.de!news.tu-chemnitz.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: DNS QUESTION Date: 7 Apr 1996 01:44:45 GMT Organization: Private BSD site, Dresden Lines: 38 Message-ID: <4k76md$er6@uriah.heep.sax.de> References: <Dp7MAL.ELC@online.tmx.com.au> <4k1l49$krb@uriah.heep.sax.de> <xZjy4MD4F99aez2@borki.zug.use.ch> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.3 BORKI@zug.use.ch (Reto Burkhalter) writes: > JW> > How can I make our NameServer respond Authortatively for a domain name > JW> > owned by someone else? > JW> > JW> Declare it to be a primary (ugly!), or a secondary (better). > That's not enogh: The owner of the domain has to delegate the > authority to you (He has to add an ' IN NS ' entry and point > to you as an authoritve nameserver. Wrong. This is only true if you are also interested in getting his nameserver traffic on your bill. :-) For example, the delegated nameserver of the zone of my employer doesn't even publish an NS record for himself, in order to save expensive traffic and have it handled by our ISP instead. All you need to make sure is that the people you are interested in will also actually *use* your shadowing secondary server. This is not so uncommon practice, btw. I'm generally shadowing all the zones that i've got in my default search order, to make name lookups faster, and avoid DNS hangs when mistyping a name. (This includes the appropriate reverse-lookup zones.) Administering DNS can sometimes be rather tricky, but those tricks might save you *alot* of traffic if you do it right, or cause you *huge* amounts of traffic if you've got it wrong. That's why i normally refuse to answer this type of questions in Usenet, and refer to ``DNS and BIND'' instead: people ought to know what they are doing. Shooting in your foot is really easy with DNS. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)