Skip to content

Zone transfert not working when DNS is badly configured #40

@thibon

Description

@thibon

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions