Mikrotik check for updates error could not resolve dns name

Микротик dns resolve failed

Thu Jan 05, 2012 8:25 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 9:59 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 10:03 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 10:25 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 10:26 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 10:31 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 10:33 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 10:40 am

mikrotik : ip dns print:

[admin@BMCHS] > ip dns print
primary-dns: 195.112.195.34
secondary-dns: 192.168.2.200
allow-remote-requests: yes
max-udp-packet-size: 512
cache-size: 50000KiB
cache-max-ttl: 1w
cache-used: 15KiB

ip dhcp-server lease print:

[admin@BMCHS] > ip dhcp-server lease print
Flags: X — disabled, R — radius, D — dynamic, B — blocked
# ADDRESS MAC-ADDRESS HOS. SERVER RAT. STATUS

Re: «DNS resolving failed» error

Thu Jan 05, 2012 10:42 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 10:46 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 11:02 am

Re: «DNS resolving failed» error

Thu Jan 05, 2012 11:02 am

Re: «DNS resolving failed» error

Mon Jan 16, 2012 8:51 am

I added the ip of mikrotik to the dns server which is a windows server 2003

but should i put mikrotik in the domain
i mean should i change the name of mikrotik to become
mikrotik.domain.com
if so,how to do it?
how to let mikrotik see the domain?
i need help here because everything should work well but i m still facing the dns resolving failed error
thank you anyway

Re: «DNS resolving failed» error

Mon Jan 16, 2012 9:53 am

Re: «DNS resolving failed» error

Mon Jan 16, 2012 9:57 am

Re: «DNS resolving failed» error

Mon Jan 16, 2012 10:22 am

Re: «DNS resolving failed» error

Thu Feb 02, 2012 3:38 pm

i managed to get through the DNS resolving error by restarting the RouterOS.( i heard from a friend that it’s a bug in version 3 )

now i am having another error: (Network is Unreachable)
i have already tested the internet connection by connecting the laptop directly to the internet cable it is working properly.
now i believe that there is something wrong in my configuration. how can i figure out what is the missing part in the configuration.
Please advise.

Источник

Микротик dns resolve failed

Wed Jan 26, 2022 11:13 pm

Hello,
I would like to ask you for help with home network issue.

My network is described at attached picture. Router A is providing connection to the Internet.

Problem is that I can’t update the RouterOS on the Router B. Error message is «could not resolve dns names». Updates on Router A and C are working fine. I see different DNS setup on Router B versus C but I don’t know how to force same DNS configuration with dynamic servers to Router B. I don’t even know if this is the solution.

It’s the only problem. The other devices behind the Router B are web sites correctly (there is no problem with DNS).

Router B DNS configuration:

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 2:18 am

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 9:47 am

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 10:00 am

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 2:04 pm

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 2:18 pm

hide-sensitive is default now and it makes sense to have it like that.
If you want to see all, you need to use show-sensitive or even verbose (have to test if that last one is not redundant ).

But it doesn’t hurt to specify it since it’s not always obvious which version a user has (ROS6 or 7).

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 7:43 pm

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 8:20 pm

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 9:39 pm

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 11:31 pm

Re: Check for Updates failed — could not resolve dns name

Thu Jan 27, 2022 11:58 pm

Re: Check for Updates failed — could not resolve dns name [SOLVED]

Fri Jan 28, 2022 3:00 am

You’re almost there. Basically just disable dhcp servers on B and C, and you’ll have one big network with 192.168.11.0/24.

— on both B and C, dhcp client should be on bridge (and you need to enable the one on B, that’s why it doesn’t work now!)
— bridge should be added to LAN interface list
— addresses 192.168.88.1/24 and 192.168.99.1/24 won’t be needed anymore, there will be 192.168.11.x from dhcp (you can add static reservations on A)
— it’s not clear to me, how you’re currently connecting to B, when both firewall and mac winbox allow access only from interfaces in LAN list, but since you have all interfaces in bridge and bridge itself is not listed, it shouldn’t work
— it’s good idea to add some firewall on A, because as it is now, it’s wide open to whole world (that’s if you have public address, otherwise it’s slightly less bad); you can find some inspiration in this thread

Re: Check for Updates failed — could not resolve dns name

Fri Jan 28, 2022 4:27 pm

You’re almost there. Basically just disable dhcp servers on B and C, and you’ll have one big network with 192.168.11.0/24.

— on both B and C, dhcp client should be on bridge (and you need to enable the one on B, that’s why it doesn’t work now!)
— bridge should be added to LAN interface list
— addresses 192.168.88.1/24 and 192.168.99.1/24 won’t be needed anymore, there will be 192.168.11.x from dhcp (you can add static reservations on A)
— it’s not clear to me, how you’re currently connecting to B, when both firewall and mac winbox allow access only from interfaces in LAN list, but since you have all interfaces in bridge and bridge itself is not listed, it shouldn’t work
— it’s good idea to add some firewall on A, because as it is now, it’s wide open to whole world (that’s if you have public address, otherwise it’s slightly less bad); you can find some inspiration in this thread

Источник

Микротик dns resolve failed

Sun Jun 09, 2019 1:12 pm

At least once a day MIkroTik stops resolving anything via first DNS server (192.168.10.1 in this example)

Is it a bug in DNS resolver implementation?
How can I fix this?

Re: DNS unable to resolve host

Sun Jun 09, 2019 2:06 pm

It seems that the way how multiple DNS servers, set up in /ip dns, are utilized in ROS, is to use one until it fails then switch over to another one and use that one until it fails, etc. So use of multiple DNS servers is fine as long they all resolve whatever needed.

In your case, the second DNS server doesn’t resolve «your» .lan TLD . so if your application depends on proper resolving of .lan hostnames, you should remove any other DNS srrver from /ip dns configuration.

Re: DNS unable to resolve host

Sun Jun 09, 2019 2:25 pm

You haven’t provided much context, but I suppose 192.168.10.1 to be a local one (another Mikrotik?) which can resolve *.lan while 1.1.1.1 is an external one which is obviously unable to resolve *.lan.

The local resolver does use the configured downstream servers as backup of each other, but in a different way than you probably expect — it asks one of them, and if it provides any answer, including an empty one, it uses that answer, caches it if it contains any useful information, and forwards it upstream, i.e. to the querying external client or internal application. Only if no response comes, it tries the other server and if that one answers, the resolver keeps using it also for the subsequent queries, until it eventually doesn’t answer so there is a reason to try with yet another one (which may be the one used previously if you have just two).

Now once you indicate the 192.168.10.1 as a server to be used, its response is cached, but it does not make the resolver start using that server for subsequent queries, it remembers the last one it chose on its own until it stops responding.

To date you cannot tell the embedded resolver to use a particular downstream server for a particular domain suffix. Only ugly workarounds allowing that are possible, which involve layer7-protocol firewall rules and some in-depth knowledge of the DNS protocol packet format and of Mikrotik’s handling of packet data by means of regular expressions.

Re: DNS unable to resolve host

Sun Jun 09, 2019 2:51 pm

Thank you for reply.

Hm, ok. But what if someone uses several networks with their own DNS servers and wants to resolve custom domains for appropriate network?
For example:
Network 1: 172.17.1.0/24, DNS server 172.16.1.1, TLD: .lan
Network 2: 172.17.2.0/24, DNS server 172.16.2.1, TLD: .local
Network 3: 172.17.3.0/24, DNS server 172.16.3.1, TLD: .corp

Also I did not find any settings to «reset failed status» for DNS server and start using first one again. During my troubleshooting I have found that MikroTik stops using first DNS after one failed attempt and then switches to another. In my case first server is behind VPN tunnel and sometimes there are delays which can cause such issues, but I still want to resolve «.lan» domains via this network (or at least, get resolve error when VPN is down).

Specifying only first server in DNS settings is not a good idea for me, because when VPN becomes unreachable, DNS resolve stops working for any domains.

And I’m wondering why MikroTik does not try to use another server when gets failed resolve message from one of DNS servers in this list.

Источник

Микротик dns resolve failed

Thu Apr 30, 2020 12:05 pm

A have a pair of Mikrotik devices — RB2011UiAS working as router and switch, and RBcAPGi-5acD2nD (cAP ac) working as access point in WISP AP mode.
The second one is not accessible via web interface, configuring with Winbox.
When trying to check for updates in System — Packages tab it returns ‘ERROR: could not resolve DNS name’. Pinging 8.8.8.8 in CLI returns ‘no route to host’.
But AP is working — all devices connected on both frequencies get internet connection. What should I do to get updates?

Thank you in advance.

Re: Can’t update — could not resolve DNS name error

Thu Apr 30, 2020 1:51 pm

Re: Can’t update — could not resolve DNS name error

Thu Apr 30, 2020 2:26 pm

Re: Can’t update — could not resolve DNS name error

Thu Apr 30, 2020 2:29 pm

1. Configure default route in /ip route using main router’s LAN IP address as gateway

Re: Can’t update — could not resolve DNS name error

Thu Apr 30, 2020 3:13 pm

On both devices, get to command line (in Winbox, it’s the [Terminal] button), export the configuration to a file using /export hide-sensitive file=device_name, download the files, anonymise them following the hint in my automatic signature right below, and post both. Your cAP may have no IP address at all.

Off-topic, if your uplink bandwidth is more than 100 Mbit/s, it may be useful to make the cAP ac a router, because its CPU is much more powerful than the one of the 2011.

Re: Can’t update — could not resolve DNS name error

Thu Apr 30, 2020 7:15 pm

Re: Can’t update — could not resolve DNS name error

Thu Apr 30, 2020 7:24 pm

Re: Can’t update — could not resolve DNS name error [SOLVED]

Thu Apr 30, 2020 7:36 pm

You haven’t configured any IP address on the /interface bridge named bridge on the cAP ac manually, and the /interface bridge filter rule action=drop chain=input dst-port=68 in-interface=ether1 ip-protocol=udp mac-protocol=ip prevents responses from the DHCP server running at the 2011 from reaching the client on the cAP ac. Has this rule been added by Quickset or have you added it yourself with something particular in mind?

Depending on what you choose (to set an IP address manually or to remove the bridge filter rule to allow the DHCP to work), you may remove the static default route as the DHCP client will get it from the 2011’s DHCP server; however, the DHCP server doesn’t indicate any DNS, so again, either keep it set manually on the cAP ac, or set dns-server=192.168.1.1 at the only row of /ip dhcp-server network on the 2011.

Источник

Микротик dns resolve failed

Sat Jul 11, 2020 1:44 pm

I have a hAP ac^2 home router running RouterOS 6.47. When trying to establish a connection to a VPN server via its IP it works fine, however it complains about not being to resolve the DNS record when using the hostname instead.

When trying to resolve a hostname from the router, I get this:

Re: Unable to resolve DNS names

Sat Jul 11, 2020 9:00 pm

Re: Unable to resolve DNS names

Sat Jul 11, 2020 9:06 pm

• Gleb Kolupaev
  MTCNA MTCRE MTCTCE
  Telegram https://t.me/baltikaberg

Re: Unable to resolve DNS names [SOLVED] [SOLVED]

Sat Jul 11, 2020 9:21 pm

Thanks for the replies.

It was caused by another VPN connection that somehow managed to cause the DNS resolver to fail. Disconnecting that link solved the issue. I’ll need to investigate why that was happening.

Re: Unable to resolve DNS names

Sat Jul 11, 2020 9:44 pm

The slash before ping or its absence changes nothing.

Setting allow-remote-requests to yes would help if the DNS query was failing from a LAN host, but it doesn’t help with router’s own DNS queries failing.

So I suspect the dynamically provided DNS server (10.255.255.2) to be guilty. The DNS proxy in RouterOS doesn’t try all servers — it keeps using one of them until it fails to provide a response within some timeout; a negative response (domain name doesn’t exist) is still a response so it doesn’t lead to switching to the other server.

Источник