[125469] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Tracking down reverse for ip

daemon@ATHENA.MIT.EDU (Scott Howard)
Sat Apr 17 01:28:18 2010

In-Reply-To: <y2k6eb799ab1004152252sbedb5de6sbfed7b73722276e8@mail.gmail.com>
Date: Fri, 16 Apr 2010 22:28:04 -0700
From: Scott Howard <scott@doc.net.au>
To: James Hess <mysidia@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Thu, Apr 15, 2010 at 10:52 PM, James Hess <mysidia@gmail.com> wrote:

> On Thu, Apr 15, 2010 at 3:59 PM, William Pitcock
> <nenolod@systeminplace.net> wrote:
> > For someone who is a CCNA, Mikrotik Certified Whatever, etc, etc, etc,
> > you really should know how to use dig(1).
>
> Certifications usually only suggest certain skills or knowledge they
> were designed to validate,  and sometimes might fail even at that;
> dig(1) or detailed DNS knowledge  is not scoped within either of those
> certs, as far as I know..
>

Whilst that's almost certainly right, I had a lot of trouble finding a
google search that _didn't_ return something relevant as it's first hit
(such as ARIN's whois, or one of several guides on how to use dig/etc for
reverse DNS).

Of course, they don't teach google in any certification I've come across
either, but...

  Scott

home help back first fref pref prev next nref lref last post