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

Fairlight fairlite at fairlite.com
Wed Mar 15 11:36:07 PST 2006


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.

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.

> 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*

mark->


More information about the Filepro-list mailing list