Standalone man-in-the-middle attack framework used for phishing login credentials along with session cookies, allowing for the bypass of 2-factor authentication
I'm having an issue with how Evilginx2 acts as a DNS resolver.
I'm using Ubuntu Server 20.04 with resolved.conf set to DNSStubListener=no to free up port 53 and AWS Route53 as a DNS provider.
I know to get Evilginx to work as a DNS resolver I need to set the glue records to point to the Evilginx server but I would also like to use my domain with subdomains for a web server and mail server.
I've noticed that there is a feature request from 2018 that would solve this issue (#135) that hasn't been implemented, but I was wondering if there is a way to set a DNS forwarder for specific domains (e.g. domain.tld, mail.domain.tld) to resolve to AWS name servers?
I have an idea of how I would implement this feature, manually (As described in #135) just wanted to make sure it wasn't possible before I commit to it, I'm not well versed in Go but from reading the code I'm sure I can do it.
I'm having an issue with how Evilginx2 acts as a DNS resolver. I'm using Ubuntu Server 20.04 with resolved.conf set to DNSStubListener=no to free up port 53 and AWS Route53 as a DNS provider.
I know to get Evilginx to work as a DNS resolver I need to set the glue records to point to the Evilginx server but I would also like to use my domain with subdomains for a web server and mail server.
I've noticed that there is a feature request from 2018 that would solve this issue (#135) that hasn't been implemented, but I was wondering if there is a way to set a DNS forwarder for specific domains (e.g. domain.tld, mail.domain.tld) to resolve to AWS name servers?
I have an idea of how I would implement this feature, manually (As described in #135) just wanted to make sure it wasn't possible before I commit to it, I'm not well versed in Go but from reading the code I'm sure I can do it.
Thanks, Bison