# Correct DNS and Proxies?

**URL:** <https://mpsocial.com/t/correct-dns-and-proxies/148738>\
**Category:** Instagram Marketing\
**Created:** [March 6, 2023, 10:11pm UTC](https://mpsocial.com/t/correct-dns-and-proxies/148738 "2023-03-06T22:11:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JSanders](https://mpsocial.com/letter_avatar_proxy/v4/letter/j/aeb1de/32.png) [@JSanders](https://mpsocial.com/u/JSanders)\
**Post date:** [March 6, 2023, 10:11pm UTC](https://mpsocial.com/t/correct-dns-and-proxies/148738/1 "2023-03-06T22:11:02Z")

</div>

How do you ensure DNS is covered/safe/correct with your proxy you’re using? In both Chrome or Firefox or with a browser add-on?

---

<div class="post-metadata">

**Author:** ![Silicon\_Valley](https://mpsocial.com/user_avatar/mpsocial.com/silicon_valley/32/64431_2.png) [@Silicon\_Valley](https://mpsocial.com/u/Silicon_Valley)\
**Post date:** [November 10, 2023, 2:26am UTC](https://mpsocial.com/t/correct-dns-and-proxies/148738/2 "2023-11-10T02:26:04Z")

</div>

Ensure there is no webRTC leak. Use an anti webRTC plugin

---

<div class="post-metadata">

**Author:** ![darius7](https://mpsocial.com/user_avatar/mpsocial.com/darius7/32/74907_2.png) [@darius7](https://mpsocial.com/u/darius7)\
**Post date:** [October 19, 2026, 1:59pm UTC](https://mpsocial.com/t/correct-dns-and-proxies/148738/3 "2026-10-19T13:59:48Z")

</div>

Run a DNS leak test with the proxy active and compare it with a test without the proxy. The reported resolver should be consistent with the proxy connection, not your usual ISP or local network.

In Firefox, check the remote-DNS setting for SOCKS5. In Chrome, check the proxy type and add-on configuration: an extension may proxy web requests while DNS still resolves locally. WebRTC is a separate leak surface, not a DNS fix.