Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wild-carded DNS Enumeration #4

Open
GoogleCodeExporter opened this issue Sep 20, 2015 · 0 comments
Open

Wild-carded DNS Enumeration #4

GoogleCodeExporter opened this issue Sep 20, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Wild-carded DNS enumeration should be possible and would be a useful feature.  
If its already been determined that the DNS is wildcard, then various queries 
are resolving into the same resource record, i.e.

abc.foo.com == A ==> 10.0.0.1
xyz.foo.com == A ==> 10.0.0.1
fff.foo.com == A ==> 10.0.0.1
.
.
.

Make note of that as:

*.foo.com? == A ==> 10.0.0.1

and anything that doesn't resolve into 10.0.0.1, it isn't a wildcard entry, 
continuing our example:

abc.foo.com == A ==> 10.0.0.1
xyz.foo.com == A ==> 10.0.0.1
fff.foo.com == A ==> 10.0.0.1
db.foo.com == A ==> 192.168.0.123
orf.foo.com == A ==> 10.0.0.1
iwd.foo.com == A ==> 10.0.0.1

.
.
.

Once the enumeration finishes, you could output something like:

*.foo.com? == A ==> 10.0.0.1
db.foo.com == A ==> 192.168.0.123

Original issue reported on code.google.com by rsrip...@gmail.com on 31 Dec 2011 at 10:52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant