> In T::R, the keys that you use in the hash are all treated as regexes. In
> effect you're saying "if you look up a value using a key that matches this
> regex, then return this value". An added complication is that the key/value
> pairs are _ordered_ (the underlying object is an array, not a has
On Wed, May 09, 2001 at 05:04:23PM +0100, David Cantrell wrote:
> I've been made redundant. Anyone want an Evil Programmer?
>
> http://www.cantrell.org.uk/david/cv
funky server set up:
[steve@webcache steve]$ telnet www.cantrell.org.uk 80
Trying 195.149.50.61...
Connected to plough.barn
yone
manages to keep in-addr.arpa up to date (1). It makes no difference
in nomal operation, so there is no earthly reason for nslookup to
insist upon it.
Of course, *real* men would be doing a `perl -MNet::DNS -e ...'
--
Steve Keay
1) ever tried to get a US ISP to configure reverse DNS for a /25?
> > Yes, it's useful. I like nslookup. (Plus I feel that dig is pretty verbose,
> > but maybe there's a flag to control that that I've been too lazy to look
> > for.)
>
> I guess it depends on application. If you need to know the nuts and bolts
> of a query, use dig. If you only need a quick re
