OT: DNS (was: Re: MenuEze on Linux?)

[Bill Campbell]

On Wed, Mar 15, 2006, Fairlight wrote:
>Is it just me, or did Bill Campbell say:
>> 
>> You're *STILL* using the deprecated nslookup :-).
>
>I have dig on all the servers I regularly use.  I even use it a fair amount
>of the time.  I don't use it for PTR lookups because, even though I've
>known the reverse syntax since '90, it's a PITA to type the address with
>the octets reversed...slows me down for some reason.  So if I'm going to be
>doing a series involving a numeric lookup, yeah, I tend to use nslookup.
>You can use nslookup on a straight IP and it will automagically do the
>reversal for you and do a PTR lookup.  Dig isn't that bright.  I tried it.

dig -x 192.136.111.7 

>Besides, dig's output is -way- to friggin' verbose, IMHO.  Over a screen to
>give you what you really want, which is the one line with the actual
>resolution on a single A record?  Ugh.  Not fond of it.

Personally I use the djbdns tools, dnsip, dnsname, dnsmx, dnsqr, etc.
Their output is very clean and simple to parse

dnsip lists.celestial.com
192.136.111.52 

dnsname 192.136.111.52
diablo.celestial.com

dnsqr any lists.celestial.com
255 lists.celestial.com:
80 bytes, 1+2+0+0 records, response, noerror
query: 255 lists.celestial.com
answer: lists.celestial.com 167496 MX 10 diablo.celestial.com
answer: lists.celestial.com 167496 MX 100 mx4.celestial.com

dnsqr a lists.celestial.com
1 lists.celestial.com:
53 bytes, 1+1+0+0 records, response, noerror
query: 1 lists.celestial.com
answer: lists.celestial.com 81154 A 192.136.111.52

dnsmx lists.celestial.com
10 diablo.celestial.com
100 mx4.celestial.com

>> The PTR for the IP points to the primary name of the machine
>> while lists.celestial.com is a role name which may move from
>> machine to machine.
>> 
>> I could use a CNAME for it as well, but generally avoid them.
>
>I understand where you're coming from on role vs physical.  The CNAME
>shouldn't help though, if I've got my head on half-straight.  If it was a
>pointer to diablo, then it would resolve to the diablo machine anyway.  The
>problem is that lynx apparently uses gethostbyaddr() on the peer address
>when displaying the page location information.  A or CNAME, makes no
>difference if the peer IP is the same.  It'd still come back diablo.
>
>Yes, I'm still using the depricated lynx, too.  *grin*

Have you tried the ``links'' browser?  It's a text browser that
does frames and some things that lynx doesn't.

Bill
--
INTERNET:   bill at Celestial.COM  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676

A child can go only so far in life without potty training.  It is not
mere coincidence that six of the last seven presidents were potty
trained, not to mention nearly half of the nation's state legislators.
		-- Dave Barry