Why not pinged ya.ru with the router?

This picture here gives. 8.8.8.8 ping !
5c9b03ed03ff4141942616.png
What's wrong?
March 19th 20 at 08:45
2 answers
March 19th 20 at 08:47
Because the Ip/DNS, or DNS is not registered or the server is not enabled the checkbox Allow Remote Requests

p.s. Do not forget even a moment that resolv NRM Winbox is solely using the DNS servers that are registered on the computer at this point. He Mikrotik resolved from those prescribed in the ip/dns and it so happens that the ping or trace to a certain resource by the domain name of the Telnet Mikrotik and Winbox different.
Dnsi spelled out. A tick is!
5c9b577ee005d458200462.png - Carmella83 commented on March 19th 20 at 08:50
That's what the 'setovka' gets:
5c9b580ff2f96736637355.png - Carmella83 commented on March 19th 20 at 08:53
Here static DNS
5c9b58ad781c4505146425.png - Carmella83 commented on March 19th 20 at 08:56
You have written nonsense, Dickie. The CSN must be the first not microta address and the address of Google, the rest can be removed at all. In static DNS do not need to Google and Yandex the record. Network needs as DNS to only ip Mikrotik and nothing more. The only way to work. - Electa commented on March 19th 20 at 08:59
@Electa, Thanks for the reply. Probably I incorrectly described the problem.
Namely. With Internet access on the local machines there are no problems. The problem with updating the router. In fact, he does not see the server and downloads the update.
The fact that the router is configured to "balanced" with two WAN ports to one service provider. (PPPoE) on both lines. The first port address is static, the second gets dynamically.
Balancing works fine with one exception: stopped pingomatic server by name. Because of this, the router cannot find the server for updates.
PS off balance, recovering and ping the router fine download update.
Thank you. - Carmella83 commented on March 19th 20 at 09:02
Means configured incorrectly balancing and packet marking. In the Internet you can find at least 3 redundancy schemes. And most likely, your used to fail, or not applicable to the realities of current. - Electa commented on March 19th 20 at 09:05
It seems that it is. Question: where is the error?
5c9cb5ec2fbe8449607848.png
Taken from here: https://habr.com/ru/post/244385/ - Carmella83 commented on March 19th 20 at 09:08
March 19th 20 at 08:49
Because the domain name need to resolvit in ip, and microt does not
Well you Google for the ip pinguet why Yandex name?
Command-type ping [resolve ya.ru] work (may be slightly wrong syntax)

Find more questions by tags Mikrotik