Problem with ROS 6.6 but it started in 6.5 with DNS, basically caused slow browsing and random page timeouts.
We started getting timeouts on some websites and general Internet slowdown. It seemed to get progressively worse.
We restart main router and all is fine for sometimes a day, sometimes an hour.
We narrowed it down to, it seems Mikrotik DNS proxy, but I did not go into depths as I have a network that was slow/down so we made some changes as workaround. I still have a case that is not behaving as expected unless I’m missing something.
The DNS proxy used here (10.1.1.100) was a MT but changed to Linux Named/Bind server since, but results are same.
The domain being looked up is a split-horizon domain set up on the server.
SXT:
[admin@] /ip dns> pr
servers: 10.1.1.100
dynamic-servers:
allow-remote-requests: yes
max-udp-packet-size: 512
query-server-timeout: 2s
query-total-timeout: 10s
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 266KiB
PC:
Ethernet adapter Local Area Connection:
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1 <-SXT
If I do a lookup from PC directly to the Named server hosted domain, it works, but proxy via SXT does not.
However most other domains/hosts work, for some reason some requests are ignored.
Directly from PC to server:
C:\Users\User>nslookup www.true.co.za 10.1.1.100
Server: UnKnown
Address: 10.1.1.100
Name: true.co.za
Address: 72.9.231.106
Aliases: www.true.co.za
From PC via SXT pointing to server:
C:\Users\User>nslookup > www.true.co.za > 192.168.0.1
Server: UnKnown
Address: 192.168.0.1*** UnKnown can’t find > www.true.co.za> : Non-existent domain
Also trying to ping hostname on SXT:
[admin@Ekkas] > /ping www.true.co.za
invalid value for argument address:
invalid value of mac-address, mac address required
invalid value for argument ipv6-address
while resolving ip-address: name does not exist
What is strange is how this seemingly started to creep in and got worse to the point where ±50% of clients experienced some browsing issues.
Anyone experienced something like this or have some pointers for me to look at?
No filter/mangle/nat on the SXT apart from masquerade. No other rules on hops between SXT and 10.1.1.100 (DNS server).
Regards