Closed tbaschak closed 6 years ago
Hey @tbaschak , sorry for the late reply, for some reason GitHub is not sending me email notifications anymore, so now I am going manually through all the issues of all my projects :(
I am looking at this right now
It's interesting to notice the different responses between IPv4 and IPv6. I got consistently b4-mia
ove v6 and b2-mia
over v4.
However, example:
Forcing IPv6 on a host with proper IPv6 configuration
$ python3 nsidenumerator.py b.root-servers.net -6 -q
b'b4-mia'
Forcing IPv6 on a sad host without IPv6:
$ python3 nsidenumerator.py b.root-servers.net -6 -q
Traceback (most recent call last):
File "nsidenumerator.py", line 189, in <module>
main()
File "nsidenumerator.py", line 127, in main
source_port=sport, port=args.dport)
File "/usr/lib/python3/dist-packages/dns/query.py", line 238, in udp
s.sendto(wire, destination)
OSError: [Errno 101] Network is unreachable
btw, feel free to close the issue if there's nothing else you want to address :)
Also, sorry for not seeing your PR. Again, issues with GitHub notifications :(
Awesome thanks for adding this! Thats all I was looking for was just a way to force resolution over v4 or v6!
No worries about missing a github notification, this wasn't a critical issue or anything :-)
This is a fabulous utility.
Since DNS resolution is supported for target, it might be handy to have a
-4
and-6
options to force IPv4 or IPv6 for the target.My output:
I was wondering which protocol this hit, so I had run again each time for the v4 and v6 addresses.