I ´m using the same hard and configuration for about one year. (RB493 With L4)

A pair of days after I ´d change to ROS V3.30 the terminals cannot resolve DNS names....

I´m using MKT as DNS RELAY (Allow Remote Request)

When I put in the terminals , THE SAME DNS SERVERS that I have in the MKT , every terminal resolve DNS Names without problems....

Regards

have you checked with nslookup?..

Dear Chupaka,

All it´s ok.. but the Mikrotik don´t run as DNS RELAY....

So I´d create a NAT RULE to resolve that :

Chain : DST-NAT
Protocol : UDP
DST-PORT : 53

Action : DST-NAT
DST-ADDRESS : (DNS SERVER - PUBLIC IP)

With this rule the Mikrotik RUN as a DNS RELAY, but NOT with the NATURALL OPTION (ALLOW REMOTE REQUEST)

Regards

remove the NAT rule and just for test, run NSLOOKUP in your PC to see the answer from the DNS server.

I just tested and it works fine for me. My router's address is 192.168.88.1 (it's a RB750 with default config) and in my Windows PC the DNS server is also set to 192.168.88.1, and you can see that it worked fine with allow remote requests:

C:\User\Sebastian>nslookup microsoft.com
DNS request timed out.
timeout was 2 seconds.
*** No se puede encontrar el nombre de servidor para la dirección 192.168.180.1:
Timed out
*** Los servidores predeterminados no están disponibles
Servidor: UnKnown
Address: 192.168.180.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** La petición a UnKnown a caducado

C:\User\Sebastian>nslookup cisco.com
*** No se puede encontrar el nombre de servidor para la dirección 192.168.180.1:
Non-existent domain
*** Los servidores predeterminados no están disponibles
Servidor: UnKnown
Address: 192.168.180.1

DNS request timed out.
timeout was 2 seconds.
Respuesta no autoritativa:
Nombre: cisco.com
Address: 198.133.219.25


C:\User\Sebastian>nslookup mikrotik.com
DNS request timed out.
timeout was 2 seconds.
*** No se puede encontrar el nombre de servidor para la dirección 192.168.180.1:
Timed out
*** Los servidores predeterminados no están disponibles
Servidor: UnKnown
Address: 192.168.180.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** La petición a UnKnown a caducado

change main dns. It is possible that the one that you have established is not working correctly.

regards

yes, it means that the router was contacted, but couldn't get information from the DNS server itself

i have an issue with my router dns, from 10.30am-5.00pm when i ping my dns, it timeout value is very high which makes people browsing to browse very slow and sometimes page times out. sometimes the value even gives request timeout.
i started to experience this from our previous server we where using which is a router os version 2.9 and now we even switch to routerboard rb1000 the problem is still the same.

Plz how do guys think i may be able to fix this my problem

when i ping my dns, it timeout value is very high

so, use another DNS =)