DNS not working from RouterOS, can't pin down the problem

Hello!

I have RouterOS 6.35.2 on hAP ac (mipsbe). Problem appeared some time ago (can’t tell exact date). When I tried to upgrade to 6.35.2 I noticed that upgrade could not resolve upgrade.mikrotik.com. I performed upgrade manually hoping that would resolve some DNS bug, but it did not. I have ran out of ideas where to look for issues.

So, mikrotik configuration is as follows:

> /ip dns print 
                servers: 8.8.8.8
        dynamic-servers: 80.232.230.241,195.122.12.241
  allow-remote-requests: no
    max-udp-packet-size: 4096
   query-server-timeout: 2s
    query-total-timeout: 10s
             cache-size: 2048KiB
          cache-max-ttl: 1w
             cache-used: 9KiB
/ip dns>

Now let’s try and ping stuff from routeros:

> /ping zuze.laacz.lv
invalid value for argument address:
    invalid value of mac-address, mac address required
    invalid value for argument ipv6-address
    while resolving ip-address: could not get answer from dns server
> /ping 185.35.69.14
  SEQ HOST                                     SIZE TTL TIME  STATUS             
    0 185.35.69.14                               56  61 5ms  
    1 185.35.69.14                               56  61 6ms  
    sent=2 received=2 packet-loss=0% min-rtt=5ms avg-rtt=5ms max-rtt=6ms

Let’s do that from a PC located behind this hAP via all configured nameservers:

C:\>nslookup
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> zuze.laacz.lv
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    zuze.laacz.lv
Address:  185.35.69.14

> server 8.8.4.4
Default Server:  google-public-dns-b.google.com
Address:  8.8.4.4

> zuze.laacz.lv
Server:  google-public-dns-b.google.com
Address:  8.8.4.4

Non-authoritative answer:
Name:    zuze.laacz.lv
Address:  185.35.69.14

> server 80.232.230.241
Default Server:  ns10.lattelecom.lv
Address:  80.232.230.241

> zuze.laacz.lv
Server:  ns10.lattelecom.lv
Address:  80.232.230.241

Non-authoritative answer:
Name:    zuze.laacz.lv
Address:  185.35.69.14

> server 195.122.12.241
Default Server:  ns13.lattelecom.lv
Address:  195.122.12.241

> zuze.laacz.lv
Server:  ns13.lattelecom.lv
Address:  195.122.12.241

Non-authoritative answer:
Name:    zuze.laacz.lv
Address:  185.35.69.14

And also a ping to make sure:

C:\>ping zuze.laacz.lv

Pinging zuze.laacz.lv [185.35.69.14] with 32 bytes of data:
Reply from 185.35.69.14: bytes=32 time=5ms TTL=60

Ping statistics for 185.35.69.14:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 5ms, Average = 5ms
Control-C
^C

I had this issue but in my case the config did not show as you showed, but the two timeout parameters were both zero.
This happened after a reset to defaults.
However in your case it appears to be different, although maybe related?

Atually I have the same dns issue at the new rb3011@6.36rc12