Re: DNSSEC NSEC howto

[John Bond <john.r.bond () gmail com>]

On 25 February 2011 05:31, David Fifield <david () bamsoftware com> wrote:
> $ sudo ./nmap --datadir . -sS localhost -p53 --script=dns-nsec-enum --script-args dns-nsec-enum.domains={example.com}
> PORT   STATE SERVICE
> 53/tcp open  domain
> | dns-nsec-enum:
> |       hosts for example.com:
> |
> |       bulbasaur.example.com:example.com:A:NS:SOA:RRSIG:NSEC:DNSKEY
> |       charmander.example.com:bulbasaur.example.com:A:RRSIG:NSEC
> |       dugtrio.example.com:charmander.example.com:A:RRSIG:NSEC
> |       gyarados.example.com:dugtrio.example.com:A:RRSIG:NSEC
> |       ns.example.com:gyarados.example.com:A:RRSIG:NSEC
> |       snorlax.example.com:ns.example.com:A:RRSIG:NSEC
> |_      vulpix.example.com:snorlax.example.com:A:RRSIG:NSEC
Just in case people dont know how do interprit this the, assume each
field is seperated by ':' the second field is the domain and the third
field to the end are the dns recors that exist for thet domain i.e. if
a file tmp contains
 |       bulbasaur.example.com:example.com:A:NS:SOA:RRSIG:NSEC:DNSKEY
 |       charmander.example.com:bulbasaur.example.com:A:RRSIG:NSEC
 |       dugtrio.example.com:charmander.example.com:A:RRSIG:NSEC
 |       gyarados.example.com:dugtrio.example.com:A:RRSIG:NSEC
 |       ns.example.com:gyarados.example.com:A:RRSIG:NSEC
 |       snorlax.example.com:ns.example.com:A:RRSIG:NSEC
 |_      vulpix.example.com:snorlax.example.com:A:RRSIG:NSEC
then:
cut -d: -f 2- tmp | sed 's/:/ has the following DNS Entries:      /'
example.com has the following DNS Entries:      A:NS:SOA:RRSIG:NSEC:DNSKEY
bulbasaur.example.com has the following DNS Entries:    A:RRSIG:NSEC
charmander.example.com has the following DNS Entries:   A:RRSIG:NSEC
dugtrio.example.com has the following DNS Entries:      A:RRSIG:NSEC
gyarados.example.com has the following DNS Entries:     A:RRSIG:NSEC
ns.example.com has the following DNS Entries:   A:RRSIG:NSEC
snorlax.example.com has the following DNS Entries:      A:RRSIG:NSEC
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/