antonyfanta / dnsenum

Automatically exported from code.google.com/p/dnsenum
0 stars 1 forks source link

--dnsenum option is not fully used. #1

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. ./dnsenum.pl --dnsserver localhost -v my_domain.com
2. In my /etc/resoslv.conf I have a public DNS Server
3. my_domain.com exists only in my localhost DNS Server.

What is the expected output? What do you see instead?
If --dnsserver option is used, my public DNS server in /etc/resolv.conf
should not be used. I think it is. 

What version of the product are you using? On what operating system?
I am using dnsenum.pl version 1.2 on backtrack beta 4.

Please provide any additional information below.
My Public DNS Server is not used for A, NS and MX resolution, but it is for
AXFR transfert to resolve ns.my_domain.com (probably line 728). So zone
transfert fails because my_domain.com is not know by public DNS server.

Original issue reported on code.google.com by billdang...@gmail.com on 13 Feb 2009 at 4:42

GoogleCodeExporter commented 8 years ago
first: sorry for my late reply, i have missed the notification

from "perldoc dnsenum.pl":
--dnsserver <server>    Use this DNS server to perform all A, NS and MX queries,
                        the AXFR and PTR queries are sent to the domain’s NS servers.

As you have stated normaly it should not be used, to correct this we must save 
the IP
addresses of the NS servers so we do not resolve them again for AXFR queries.

I am in my way to add some options, exemple: --noaxfr Skip axfr queries.

thanks for you feedback.  

Original comment by tixxdz@gmail.com on 8 May 2009 at 10:56