Hotspot - problem with DNS traffic on some client platforms

RouterOS General
1

Hi
I have problem with DNS client, when customer uses Planet XRT-401D router on hotspot interface. DNS is not resolved at all - neither builtin in hotspot or any other. The windows’ “nslookup” is not resolving names either, even when connected directly and whole DNS resolution in system works well. I created static firewall NAT rule (accept external DNS without port redirection) and configured routers to use external specified DNS and it works… until MT is rebooted. After reboot - a dynamic hotspot rules are being created before static ones.
Windows boxes runs ok (except nslookup).
Any idea?
regards!
kj

2

nslookup in hotspot, not working for me too.

Routeros ver 2.9rc4, ping and browsing work, nslookup does’nt.
I think there is also some slowness in browsing.

3

Please write to support@mikrotik.com with your routers configuration and also include the support output file which is made when the nslookup doesn’t work.

4

Temp solution =
Add your DNS to walled garden on port 53

5

I confirm again - DNS responses are not translatet to 53 and MT sends responses from 64xxx port (I don’t remember). Linux boxes or simply routers doesn’t understand what’s going on and ignores responses. I have never seen working nslookup in none of my networks even on windows boxes, where overall DNS resolution works! I have sniffer log and will send it to support.

6

IP 192.168.21.172.32769 > 192.203.230.10.domain: 944 A? download3.avast.com. (37)

  • ok
    IP 10.20.0.1.64872 > 192.168.21.172.1661: UDP, length 167
  • request to public dns redirected to hotspot’s dns. response becomes from hotspot’s dns, but from wrong port and TO wrong port (I think) too
    IP 192.168.21.172 > 10.20.0.1: icmp 203: 192.168.21.172 udp port 1661 unreachable
  • of course…
7

Add hostname for DNS’ (RouterOS) IP address.

8

Did you mean:

/ip hotspot profile print
0 * name=“default” hotspot-address=10.10.0.1 dns-name=“MT-TEST”
html-directory=hotspot rate-limit=“” http-proxy=0.0.0.0:0
smtp-server=0.0.0.0 login-by=mac,http-chap split-user-domain=no
use-radius=no

and

/ip dns static print
0 D MT-TEST 10.10.0.1 5m

or anything more?

Suddenly this was not helpful :frowning:
regards
kj

9

uhm, i guess i am the only one running local dns cache.
because adding hostname is necessary for dns cache to work.
might not apply to you.

10

I do use dns cache too and I didn’t had configured these entries before your post. Did I configured everything, that you mean? I’ll check once again, if was it helpfull, but today two customers called me with DNS problem again. I’ll verify these calls on monday.

11

Not helped
DNS answers still from 64872
Sent to support week ago - no answer :frowning:

12

I found it! :stuck_out_tongue:
Problem occours only sometimes, when using more then one IP address on hotspot interface (even then not always!). I disabled all additional addresses - DNS started to run ok - and then enabled them back - still runs ok. As I can see: “primary” IP addres (the one from neighbour viewer) has changed - now there is one from my hotspot IP pool, before this operation there was one from additional addresses not belonging to hotspot pool… works until reboot of course :unamused:

kj