search

kgretzky / evilginx2

Standalone man-in-the-middle attack framework used for phishing login credentials along with session cookies, allowing for the bypass of 2-factor authentication
BSD 3-Clause "New" or "Revised" License
10.62k stars 1.92k forks source link

dial tcp: lookup acme-v02.api.letsencrypt.org: Temporary failure in name resolution #749

Closed sethfaulkner closed 2 years ago

sethfaulkner commented 2 years ago

DO NOT ASK FOR PHISHLETS.

DO NOT ASK FOR HELP CREATING PHISHLETS.

DO NOT ASK TO FIX PHISHLETS.

DO NOT ADVERTISE OR TRY TO SELL PHISHLETS.

EXPECT A BAN OTHERWISE. THANK YOU!

REPORT ONLY BUGS OR FEATURE SUGGESTIONS.

Followed the instructions. Used a domain from namecheap. Set up custom nameservers for the domain ns1.domain.com and ns2.domain.com. I set the domain in evilginx and try to stand up the linkedin phishlet and get;

get directory at 'https://acme-v02.api.letsencrypt.org/directory': Get "https://acme-v02.api.letsencrypt.org/directory": dial tcp: lookup acme-v02.api.letsencrypt.org: Temporary failure in name resolution

if nslookup domain.com I get the correct IP but if I ns lookup google.com I get ** server can't find google.com: SERVFAIL. It looks like DNS is resolving only the evilginx service but nothing else, causing it to not be able to reach letsencrypt. I disabled systemd.resolved so that It would start up. What do I do to be able to resolve letsencrypt?

sethfaulkner commented 2 years ago

https://github.com/kgretzky/evilginx2/issues/125 This solved my issue