DNS spoofing doesn't work

sczane32
6 years ago

0

Okay, so I followed the steps from a couple of tutorials to attempt dns spoofing. I’m using Kali on VMware and tried dns spoofing on my host computer(Ubuntu 18).
Problem is, it just doesn’t work.
I’ve tried different ip addresses for redirection but it always goes to the website instead of redirecting it.
I read somewhere that dns spoofing doesn’t work on https websites.
Then where do you even get to use it?

5replies
4voices
2,716views
Mugi [Mugiwara27]
6 years ago

0

Everything works fine for me, have you tried with two different device ? Because the problem is probably from the VM, network problems using VMs is not a new thing

If you want to understand why it doesn’t work for most https websites, check this link ;
https://security.stackexchange.com/questions/94331/why-doesnt-dns-spoofing-work-against-https-sites

And as for how to use DNS spoof so it can be efficient in a way you want to pwn someone, good luck understanding by yourself ;) ( CoC & ToU )

But nowadays, you need to use multiple types of attack to pwn a single thing

(ps: have you read my dns spoofing tutorial ? Maybe mine will work for you ; https://www.hackthis.co.uk/articles/dns-spoofing )

sczane32
6 years ago

0

Well, so yeah i tried it with two different devices. I still got no results.
I tried to spoof for facebook and redirect it to another website’s dns but it simply goes to the actual site.

And yes, I was following your guide all along haha.

There were also a couple of errors ettercap was giving when i started the sniff.
/proc/sys/net/ipv6/conf/all/use_tempaddr is not set to 0.
/proc/sys/net/ipv6/conf/wlp2s0/use_tempaddr is not set to 0

So I changed both from 2 to 0 but still got nothing.

sczane32
6 years ago

0

Actually, one thing i do wanna know. The ip that we put in etter.dns, does it matter what it is? I tried using one of amazon’s ip’s for it but it didn’t work.

dloser
6 years ago

1

Try debugging the situation. Have you looked at the network traffic? Is there a DNS request made? Are there any replies?

A common trap is that a program/system has a local cache. For example, your browser might not make a DNS request for every HTTP request. It will typically do it once and reuse the result on consecutive HTTP requests.

Also, DNS spoofing does work with HTTPS. Or better, HTTPS is something separate of DNS. DNS doesn’t work with HTTPS in a similar way as putting your own house number on a neighbour’s house doesn’t allow you to enter the neighbour’s house with your own key. ;)

Darwin [DIDIx13]
6 years ago

0

^ Great comment +1

You must be logged in to reply to this discussion. Login
1 of 6

This site only uses cookies that are essential for the functionality of this website. Cookies are not used for tracking or marketing purposes.

By using our site, you acknowledge that you have read and understand our Privacy Policy, and Terms of Service.

Dismiss