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

DNS problems, i think. i have tried everything i can think of. put a lot of time into trying to fix this. #741

Closed ringxzero closed 1 year ago

ringxzero commented 2 years ago

MY ERROR as is below

acme: Error -> One or more domains had a problem: [b.stats.www.htmlconnecting.com] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for b.stats.www.htmlconnecting.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for b.stats.www.htmlconnecting.com - check that a DNS record exists for this domain, url: [c.www.htmlconnecting.com] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for c.www.htmlconnecting.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for c.www.htmlconnecting.com - check that a DNS record exists for this domain, url: [c6.www.htmlconnecting.com] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for c6.www.htmlconnecting.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for c6.www.htmlconnecting.com - check that a DNS record exists for this domain, url: [hnd.stats.www.htmlconnecting.com] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for hnd.stats.www.htmlconnecting.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for hnd.stats.www.htmlconnecting.com - check that a DNS record exists for this domain, url: [t.www.htmlconnecting.com] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for t.www.htmlconnecting.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for t.www.htmlconnecting.com - check that a DNS record exists for this domain, url: [www.htmlconnecting.com] acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: Invalid response from http://www.htmlconnecting.com/.well-known/acme-challenge/3OPJ9ODpeWwqNkTzRH-jiVAOFs8jrr7h6ez6C6ytiZo [137.184.150.196]: "\r\n404 Not Found\r\n\r\n

404 Not Found

\r\n
nginx/1.18.0</ce", url: [www.www.htmlconnecting.com] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for www.www.htmlconnecting.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.www.htmlconnecting.com - check that a DNS record exists for this domain, url:

My DNS settings as is below

DIGITALOCEAN

(A) mydomain.com directs to (A) www.mydomain.com directs to (NS) mydomain.com directs to ns1.digitalocean.com (NS)mydomain.com directs to ns2.digitalocean.com (NS)mydomain.com directs to ns3.digitalocean.com

no DNS settings aviable on godaddy because i set the godaddy nameservers to ns1.digitalocean.com and sn2.digitalocean.com

going to my domain and its ip both pull up my ocean droplet and show welcome to nginx!

i work all day yesterday trying to fix this and put a entire day into this. so its easy to say ive tried everything i know. its just hard finding the right info online to fix this issue.

ringxzero commented 2 years ago

both (A) records direct to my droplet IP whats hosting everything

ringxzero commented 2 years ago

nameservers myDNSsettings

ringxzero commented 2 years ago

the first pic is of my config on godaddy. just the namesevers changed 2 digitalocean.

WilKGoodangel commented 2 years ago

you need to create an AAA record too

HornyLemur commented 2 years ago

Check this FAQ

jepunband commented 2 years ago

this might help : https://github.com/kgretzky/evilginx2/issues/296#issuecomment-505259964

Iro4you commented 1 year ago

You have to buy a domain, example cloudfare and add dns records on cloudfare. and then run evilginx