[AdGuard DNS] Beta

Status
Not open for further replies.
K

Kvothe

New Member
I just bought AdGuard Pro but I'm not sure how to enable the DNS feature. I followed the instructions in the app to enable the VPN but nothing really changed. I went to the "learn more about AdGuard DNS" official site and found completely separate directions asking me to put in a new DNS to my Wi-Fi connection, which I did (why wasn't that in the app?). Yet still, no matter what I do, AdGuard's site tells me that I'm not connected to AdGuard DNS and I still see ads inside of apps. Am I missing something? Can anyone help? Thanks.
 
T

thedicemaster

Beta Tester
adguard DNS is a completely separate service, for devices that can't use the adguard app.

I suggest you undo the changes you made to your Wi-Fi settings, and then request assistance with configuring the app.
 
vasily_bagirov

vasily_bagirov

Administrator
Staff member
Administrator
@Kvothe is it possible that you have other apps installed that already use VPN?

Also @thedicemaster is correct about undoing the dns configuring. With Adguard Pro you only need to enable DNS blocking in the app.
 
T

thedicemaster

Beta Tester
sorry, didn't notice where I was replying.
I have 2 adguard threads that send reply notices, and I thought I was replying to the one for adguard for android.

so my comment about YouTube doesn't apply to adguard dns.
 
V

Volaris

New Member
Are the American servers still online? I keep getting really high pings in the 200s/300s ms. Used to be 25ms.
 
V

Volaris

New Member
vasily_bagirov said:
Does it still continue to be so?
Click to expand...
Hi, yes the pings are still high for both AdGuard DNS servers, which makes Internet browsing laggy. Below are AdGuard servers ping times:





for comparison, below is Google DNS. AdGuard DNS used to be under 30ms before.



If it helps, I'm in California using a big ISP (Comcast).
 
Ketjow3

Ketjow3

New Member
Hi from Poland,
Generaly Adguard DNS work well, don't have any isuues with it. I have use DNS in my router from UPC Poland provider.
Please add some polish (Poland) blocklists to Adguard DNS, because there are sites with adds that still shows.
And finally keep up good work with it - it's really great service.
 
vasily_bagirov

vasily_bagirov

Administrator
Staff member
Administrator
@Volaris sorry I havent replied for almost a week now. Could you please run
Code: 
tracert 176.103.130.130
command and send us a screenshot of the result? Same for .131 address.
 
P

Preston

New Member
hello I started to test your service changing dns in my router settings and my family is very glad because now see less ads when browsing on their smartphones but i have the problem that sometimes the pages that supposed always online like facebook or google dont load, so have to reload many times... i guess because i have too ping high... by the way i understand that is in test fase, so i grateful anyway whith you all for make this service possible, is a great idea, keep going!
Code: 
C:\>ping 176.103.130.130

Haciendo ping a 176.103.130.130 con 32 bytes de datos:
Respuesta desde 176.103.130.130: bytes=32 tiempo=237ms TTL=56
Respuesta desde 176.103.130.130: bytes=32 tiempo=239ms TTL=56
Respuesta desde 176.103.130.130: bytes=32 tiempo=237ms TTL=56
Respuesta desde 176.103.130.130: bytes=32 tiempo=239ms TTL=56

Estadísticas de ping para 176.103.130.130:
  Paquetes: enviados = 4, recibidos = 4, perdidos = 0
  (0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
  Mínimo = 237ms, Máximo = 239ms, Media = 238ms

C:\>tracert 176.103.130.130

Traza a la dirección 176-103-130-130.flops.ru [176.103.130.130]
sobre un máximo de 30 saltos:

  1  2 ms  1 ms  1 ms  192.168.1.254
  2  51 ms  47 ms  48 ms  bb-la-grand-8-tge0-13-0-7.uninet.net.mx [189.246
.189.118]
  3  44 ms  44 ms  44 ms  ix-et-3-1-0-0.tcore1.EQL-Los-Angeles.as6453.net
[206.82.129.57]
  4  202 ms  203 ms  *  if-ae-6-20.tcore2.LVW-Los-Angeles.as6453.net [64
.86.252.65]
  5  *  202 ms  217 ms  if-ae-3-2.tcore1.SQN-San-Jose.as6453.net [63.243
.205.13]
  6  *  *  *  Tiempo de espera agotado para esta solicitud.
  7  202 ms  204 ms  208 ms  if-ae-11-2.tcore2.L78-London.as6453.net [63.243.
128.38]
  8  201 ms  200 ms  200 ms  if-ae-8-2.tcore2.AV2-Amsterdam.as6453.net [80.23
1.131.6]
  9  200 ms  200 ms  200 ms  if-ae-2-2.tcore1.AV2-Amsterdam.as6453.net [195.2
19.194.5]
10  200 ms  200 ms  200 ms  if-ae-5-2.tcore1.FNM-Frankfurt.as6453.net [195.2
19.194.14]
11  205 ms  199 ms  200 ms  if-ae-7-2.tcore1.FR0-Frankfurt.as6453.net [195.2
19.50.1]
12  201 ms  202 ms  202 ms  195.219.50.38
13  238 ms  238 ms  239 ms  xe000-18.RT.IXC.MSK.RU.retn.net [46.46.128.101]

14  *  *  *  Tiempo de espera agotado para esta solicitud.
15  237 ms  237 ms  236 ms  176-103-130-130.flops.ru [176.103.130.130]

Traza completa.

C:\>
 
vasily_bagirov

vasily_bagirov

Administrator
Staff member
Administrator
@Preston it is an inherent problem of DNS ad blocking that something extra might be blocked, not just ads, especially on websites like facebook or some google services. I am not sure your case lies in this plane though.

Could you please next time you cant reach a website enter the following command:
nslookup facebook.com 176.103.130.130 - if you use default mode, or
nslookup facebook.com 176.103.130.131 - if you use family protection mode. Of course, substitute facebook.com with another domain depending on where you encounter the problem.
 
Status
Not open for further replies.
Top