You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found out during a challenge on HackTheBox that when the DNS resolution is pointing to localhost (127.0.0.1), fierce is not able to perform a zone transfert even if zone transfert is possible with dig.
It could happen in a real engagement too.
I updated the code in my PR
The text was updated successfully, but these errors were encountered:
thibon
added a commit
to thibon/fierce
that referenced
this issue
Aug 22, 2022
Hello,
Found out during a challenge on HackTheBox that when the DNS resolution is pointing to localhost (127.0.0.1), fierce is not able to perform a zone transfert even if zone transfert is possible with dig.
It could happen in a real engagement too.
I updated the code in my PR
The text was updated successfully, but these errors were encountered: