more bind questions

[Steve Holmes]

I think dig is eventually gonna take the place of nslookup.  When I
run nslookup on my slackware 8 boxes, I get a response like 'nslookup
is deprecated and may soon be phased out' or something to that
effect.  Plus I noticed that dig gives me a lot more information.

On Sat, May 04, 2002 at 09:57:29PM -0500, Gregory Nowak wrote:
> Hi,
> 
> I used nslookup on the unix box I have access to which is a sun-os 5.7 machine. The nslookup appears to be more advanced there then it is on my slackware 8 box. 
> 
> Anyway, I couldn't get the "set server=ns1.dhs.org" option to work (it returned with an error). So, I looked at the man page for nslookup, and it said I can find out about a host using a specific dns server from a command line. Knowing that dhs.org has 2 servers ns1.dhs.org, and ns2.dhs.org, I typed in the following on the command line on the sun-os box where I have the ssh account.
> 
> "nslookup mydomain.dhs.org ns1.dhs.org"
> "nslookup linserver.mydomain.dhs.org ns1.dhs.org"
> 
> and I got no answer with either example. I had to hit ctrl+c after a while. Querying ns2.dhs.org twice as done above with ns1.dhs.org produced failure as well. Judging that nslookup worked in the same way on my box (there is no man page), I envoked it exactly as mentioned, and got the following results.
> 
> "Server:         ns1.dhs.org
> Address:        63.175.98.30#53
> 
> Non-authoritative answer:
> *** Can't find "mydomain".dhs.org: No answer
>  "
> 
> So, it looks like the name servers at dhs.org don't know that mydomain.dhs.org exists. What can I do about it? If anyone out there who is reading this and using dhs.org as well could provide any comments, that would be wonderful. Thanks.
> Greg
> 
> 
> On Sat, May 04, 2002 at 03:33:00PM -0400, Cecil H. Whitley wrote:
> > Hi,
> > Some answers and a couple more questions.
> > 
> > > I'm not sure I understand. The next level up is dhs.org. >Since they
> > aren't running any dns services for me but are >just my domain provider, I
> > don't see how they fit in.
> > Name resolution is more of a chain than a direct process.  For example, to
> > get to your web server from a host ppp01.stuff.com a dns server for
> > stuff.com would do the following:
> > 
> > query it's root.cache for ns for .org
> > query .org for ns for dhs.org
> > query dhs.org for ns for mydomain.dhs.org
> > query ns.mydomain.dhs.org for the host ip for www.mydomain.dhs.org
> > 
> > Therefore, dhs.org has to run a dns, that's how they provide you a
> > sub-domain.  Typically they have both an "a" record and a "ns" record for
> > your dns's.  Everything else for your sub-domain is provided by your own
> > dns.  However, a nslookup query for www.mydomain.dhs.org sent to ns.dhs.org
> > should come back with an answer.  Reverse entries however are not that
> > simple.  The dns entries for those reffering queries to your dns are
> > typically in the dns of your isp or even their provider.  Reverse entries
> > work on the ip address and are therefore reffered to the "owner" of that
> > particular class address for resolution.
> > Regards,
> > Cecil
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup