Mikrotik no route to host ошибка как исправить

Код: Выделить всё

[admin@MikroTik] > /ip firewall mangle                                                                                                     
[admin@MikroTik] /ip firewall mangle> print detail                                                                                                            
Flags: X - disabled, I - invalid, D - dynamic 
 0    chain=prerouting action=mark-connection new-connection-mark=allow_in connection-state=new protocol=tcp dst-port=9999 
[admin@MikroTik] /ip firewall mangle> /ip firewall nat                                                       
[admin@MikroTik] /ip firewall nat> print detail    
Flags: X - disabled, I - invalid, D - dynamic 
 0    chain=srcnat action=masquerade src-address=61.75.223.64/27 out-interface=pppoe-out1 log=no log-prefix="" 
 1    chain=dstnat action=redirect to-ports=80 protocol=tcp dst-port=9999 
 [admin@MikroTik] /ip firewall nat> /ip firewall mangle                                                                                                     
[admin@MikroTik] /ip firewall mangle> print detail       
Flags: X - disabled, I - invalid, D - dynamic 
 0    chain=prerouting action=mark-connection new-connection-mark=allow_in connection-state=new protocol=tcp dst-port=9999 
[admin@MikroTik] /ip firewall mangle> /ip firewall filter 
                                                                                                      [admin@MikroTik] /ip firewall filter> print detail       
Flags: X - disabled, I - invalid, D - dynamic 
 0    chain=input protocol=icmp 
 1    chain=input connection-state=new protocol=tcp src-address=61.75.223.64/27 in-interface=br-lan dst-port=80,8291,22 
  2    chain=input action=accept connection-state=new protocol=tcp connection-mark=allow_in in-interface=pppoe-out1 dst-port=80 log=no log-prefix="" 
 3    chain=input action=accept connection-state=new protocol=udp src-address=61.75.223.64/27 in-interface=br-lan dst-port=53,123 log=no log-prefix="" 
 4    chain=input connection-state=established,related 



  


                       
  



 5    chain=output connection-state=!invalid 
 6    chain=forward action=accept connection-state=established,new src-address=61.75.223.64/27 in-interface=br-lan out-interface=pppoe-out1 log=no log-prefix="" 
 7    chain=forward action=accept connection-state=established,related in-interface=pppoe-out1 out-interface=br-lan log=no log-prefix="" 
 8    chain=input action=drop 
 9    chain=output action=drop 
10    chain=forward action=drop 
[admin@MikroTik] /ip firewall filter> /ip route 
[admin@MikroTik] /ip route> print detail       
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 0 ADS  dst-address=0.0.0.0/0 gateway=pppoe-out1 gateway-status=pppoe-out1 reachable distance=0 scope=30 target-
 1 ADC  dst-address=61.75.213.64/27 pref-src=61.75.213.65 gateway=br-lan gateway-status=br-lan reachable distance=0 scope=10 
 2 ADC  dst-address=213.231.0.200/32 pref-src=213.231.25.165 gateway=pppoe-out1 gateway-status=pppoe-out1 reachable distance=0 scope=10 
[admin@MikroTik] /ip route> /ip addres  
[admin@MikroTik] /ip address> print detail
Flags: X - disabled, I - invalid, D - dynamic 
 0   address=61.75.213.65/27 network=61.75.213.64 interface=br-lan actual-interface=br-lan 
 1 D address=213.231.25.165/32 network=213.231.0.200 interface=pppoe-out1 actual-interface=pppoe-out1 
 admin@MikroTik] /ip address> /interface
[admin@MikroTik] /interface> print detail
Flags: D - dynamic, X - disabled, R - running, S - slave 
 0  R  ;;; wan
       name="eth1-wan" default-name="ether1" type="ether" mtu=1500 actual-mtu=1500 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E4 
       last-link-up-time=jan/21/2018 15:02:12 link-downs=0 
 1   S ;;; lan
       name="eth2-lan" default-name="ether2" type="ether" mtu=1500 actual-mtu=1500 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E5 link-downs=0 
 2   S name="eth3-lan" default-name="ether3" type="ether" mtu=1500 actual-mtu=1500 
 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E6 link-downs=0 



  


                       
  



 3   S name="eth4-lan" default-name="ether4" type="ether" mtu=1500 actual-mtu=1500 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E7 link-downs=0 
 4  RS name="eth5-lan" default-name="ether5" type="ether" mtu=1500 actual-mtu=1500 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E8 
       last-link-down-time=jan/21/2018 15:21:29 last-link-up-time=jan/21/2018 15:21:33 link-downs=1 
 5   S name="wlan1" default-name="wlan1" type="wlan" mtu=1500 actual-mtu=1500 l2mtu=1600 max-l2mtu=2290 mac-address=64:D1:54:9F:C8:E9 
       last-link-down-time=jan/21/2018 15:54:09 
       last-link-up-time=jan/21/2018 15:53:14 link-downs=2 
 6  R  name="br-lan" type="bridge" mtu=auto actual-mtu=1500 l2mtu=1598 mac-address=64:D1:54:9F:C8:E5 last-link-up-time=jan/21/2018 15:02:09 link-downs=0 
 7  R  name="pppoe-out1" type="pppoe-out" mtu=1480 actual-mtu=1480 last-link-up-time=jan/21/2018 15:19:52 link-downs=0 
[admin@MikroTik] /interface> /ip dhcp-server 
[admin@MikroTik] /ip dhcp-server> print detail
Flags: D - dynamic, X - disabled, I - invalid 
 0    name="dhcppool" interface=br-lan lease-time=8h address-pool=dhcppool bootp-support=static authoritative=yes use-radius=no lease-script="" 
       admin@MikroTik] /ip dhcp-server> /ip pool
[admin@MikroTik] /ip pool> print detail
 0 name="dhcppool" ranges=61.75.223.66-61.75.223.93 
[admin@MikroTik] /ip dns> print       
                      servers: 
              dynamic-servers: 194.143.136.1,194.143.136.2
        allow-remote-requests: no
          max-udp-packet-size: 4096
         query-server-timeout: 2s
          query-total-timeout: 10s
       max-concurrent-queries: 100
  max-concurrent-tcp-sessions: 20
                   cache-size: 2048KiB
                cache-max-ttl: 1w
                   cache-used: 18KiB

Примерно чуть более месяца назад приобрёл роутер MikroTik hap hac2, настроил по Quick set, после настроил ещё только dns сервера и пару статичных адресов в DHCP. Всё это время он работал без нареканий.
Но пару дней назад почему-то стал выдавать no route to host на публичные адреса, хотя при этом пинг до хоста работает и telnet по порту из роутера выполняется успешно (no route to host — с клиентов). То есть, с клиентов:

$ ping github.com
PING github.com (140.82.118.3) 56(84) bytes of data.
64 bytes from lb-140-82-118-3-ams.github.com (140.82.118.3): icmp_seq=1 ttl=56 time=51.8 ms

$ telnet github.com 22
Trying 140.82.118.3...
Trying 140.82.118.4...
telnet: Unable to connect to remote host: No route to host

С терминала роутера же всё ок. В чем может быть проблема?

Да, после перезагрузки на некоторое время проблема исчезает примерно на несколько часов.

Привожу конфиг:

# apr/23/2019 15:37:56 by RouterOS 6.44.2
# software id = L82U-UTWW
#
# model = RBD52G-5HacD2HnD
# serial number = B4A00AF34868
/interface bridge
add admin-mac=74:4D:28:1E:30:C0 arp=proxy-arp auto-mac=no comment=defconf name=bridge
/interface ethernet
set [ find default-name=ether3 ] speed=100Mbps
set [ find default-name=ether4 ] speed=100Mbps
set [ find default-name=ether5 ] speed=100Mbps
/interface pppoe-client
add add-default-route=yes disabled=no interface=ether1 name=pppoe-out1 password=<pass> user=<user>
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-g/n channel-width=20/40mhz-eC disabled=no distance=indoors frequency=2447 mode=ap-bridge ssid=<SSID> wireless-protocol=802.11
set [ find default-name=wlan2 ] arp=proxy-arp band=5ghz-a/n/ac channel-width=20/40/80mhz-Ceee disabled=no distance=indoors frequency=auto mode=ap-bridge ssid=<SSID> tx-power=22 tx-power-mode=\
    all-rates-fixed wireless-protocol=802.11
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk mode=dynamic-keys supplicant-identity=MikroTik wpa-pre-shared-key="<password>" wpa2-pre-shared-key="<password>"
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=dhcp ranges=192.168.88.5-192.168.88.254
/ip dhcp-server
add add-arp=yes address-pool=dhcp disabled=no interface=bridge lease-time=50m name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=wlan1
add bridge=bridge comment=defconf interface=wlan2
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
add interface=pppoe-out1 list=WAN
/ip address
add address=192.168.88.1/24 comment=defconf interface=ether2 network=192.168.88.0
/ip dhcp-client
add comment=defconf dhcp-options=hostname,clientid interface=ether1
/ip dhcp-server lease
add address=192.168.88.6 client-id=1:d0:50:99:6:39:68 mac-address=D0:50:99:06:39:68 server=defconf
add address=192.168.88.7 mac-address=D4:3B:04:7B:46:89 server=defconf
add address=192.168.88.9 client-id=1:ac:ed:5c:cc:c4:50 mac-address=AC:ED:5C:CC:C4:50 server=defconf
add address=192.168.88.8 mac-address=BC:A8:A6:84:78:2B server=defconf
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes servers=8.8.8.8,8.8.4.4
/ip dns static
add address=192.168.88.1 name=router.lan
/ip firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf:  drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
/ip ssh
set allow-none-crypto=yes
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=ether1 type=external
add interface=bridge type=internal
add interface=pppoe-out1 type=external
/system clock
set time-zone-name=Europe/Saratov
/system identity
set name=kolyan
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN

Are you looking for an answer to the topic “no route to host“? We answer all your questions at the website barkmanoil.com in category: Newly updated financial and investment news for you. You will find the answer right below.

Keep Reading

How do I fix No route to host?

Open the applet or go through your system settings. Select your connection and find the “IPv4” tab. Switch the connection to “Manual” and manually enter in the IP address of your computer and the IP of your router as the gateway. Then, in the DNS field below, enter your router’s IP or the IP of another DNS server.

What causes no route to host?

‘No Route to Host’ denotes a network problem, usually one which shows up when the server or host is not responding. This may happen because of network issues or because of an inappropriate setup.

\”Connection refused\” vs \”No route to host\” (4 Solutions!!)

Images related to the topic\”Connection refused\” vs \”No route to host\” (4 Solutions!!)

What is no route host exception?

“No route to host” Signals that an error occurred while attempting to connect a socket to a remote address and port. Typically, the remote host cannot be reached because of an intervening firewall, or if an intermediate router is down.

Can ping but SSH no route to host?

Your “no route to host” while the machine responds to ping is a sign of a firewall that is denying you access but is informing you that it happened (i.e. with an ICMP message rather than just silent drop). Check your outgoing firewall. If it isnt that then its blocked closer to the destination.

How do I fix port 22 without hosting?

Login, and access a command prompt. Then use the firewall-cmd (RHEL/CentOS/Fedora) or UFW (Debian/Ubuntu) to open port 22 (or the port you configured to be used for SSH) in the firewall as follows. Now try to re-connect to the remote server once more via SSH.

How do I fix destination host unreachable?

Can ping but connection refused?

If it says Connection refused , it is likely that the other host is reachable, but there is nothing listening on the port. If there is no response (packet is dropped), it is likely a filter blocking the connection. Next, try nmap <ip> . This will tell you which ports are open and blocked.

See some more details on the topic no route to host here:

Cách sửa lỗi kết nối “No Route to Host” trên Linux – Thủ thuật

Dưới đây Taimienphi.vn sẽ liệt kê một số nguyên nhân gây lỗi cũng như cách sửa lỗi “No Route to Host” trên Linux. sua loi ket noi no route to host tren linux.

+ Read More

How to Fix “No Route to Host” Connection Error on Linux

When you’re trying to connect to a service on Linux, “No route to host” is one of the last things you want to hear.

+ View More Here

‘No Route to Host’ Error in Linux – What To Do – Alphr

‘No Route to Host’ denotes a network problem, usually one which shows up when the server or host is not responding. This may happen because of …

+ View More Here

Khắc phục lỗi định tuyến đến máy chủ (No Route to Host …

Khắc phục lỗi định tuyến đến máy chủ (No Route to Host) trong Linux? · 1. Kiểm tra lại Host/Service · 2. Cổng kết nối sai · 3. Iptables bị chặn kết …

+ View More Here

How do I ping an IP address?

How do I resolve destination host unreachable in Linux?

You can verify it by disabling the firewall and ping the destination IP again. The second common reason is a loose network connection. Referred from this source. We can fix this, by disconnecting both power cables and Ethernet cables from the modem, router, and PC.

Why is destination host unreachable?

Destination Network / Host unreachable – This means that the host that you are trying to ping is down or is not operating on the network. Hardware Error – This usually means that your network adapter is disabled or you have unplugged the Ethernet cable.

Mengatasi mikrotik no route to host

Images related to the topicMengatasi mikrotik no route to host

How check if port is open Linux?

What is the SSH protocol?

SSH or Secure Shell is a network communication protocol that enables two computers to communicate (c.f http or hypertext transfer protocol, which is the protocol used to transfer hypertext such as web pages) and share data.

What port does SSH use?

By default, the SSH server still runs in port 22.

Could not open connection to the host on port 22 Connect failed Linux?

Sometimes while connecting to SSH servers, users often encounter “Connection refused” error by port 22. It happens because of several reasons like SSH service is not running, the port is blocked by the firewall, or the server is using a different port. It can also occur because of the IP conflict issue.

What does it mean when a website is unreachable?

“This site can’t be reached: ERR ADDRESS UNREACHABLE” is a standard error message. When a user attempts to open a website, the browser is unable to connect to the server. The router or your internet settings are usually at blame if the problem is on your end.

How do I renew my IP address?

Getting a new IP address on your Android isn’t quite as straightforward. You need to force your phone to “forget” the current Wi-Fi network it’s connected to. Once you do this, it’ll release its current connection (and IP address). The next time you connect it’ll receive a new one.

How do I fix connection refused?

What is the ICMP port?

ICMP has no concept of ports, as TCP and UDP do, but instead uses types and codes. Commonly used ICMP types are echo request and echo reply (used for ping) and time to live exceeded in transit (used for traceroute).

Why is SSH not working?

Make sure you have SSH access enabled. You can check to see of SSH is enabled by running cf ssh-enabled APP_NAME . Enable it by running cf enable-ssh APP_NAME . Make sure you are not in an environment that blocks outgoing traffic on port 2222 (the default port for cf ssh traffic).

[Mikrotik] How to Enable internet in Mikrotik with Static Route

Images related to the topic[Mikrotik] How to Enable internet in Mikrotik with Static Route

Why is destination host unreachable?

Destination Network / Host unreachable – This means that the host that you are trying to ping is down or is not operating on the network. Hardware Error – This usually means that your network adapter is disabled or you have unplugged the Ethernet cable.

How do I resolve destination host unreachable in Linux?

You can verify it by disabling the firewall and ping the destination IP again. The second common reason is a loose network connection. Referred from this source. We can fix this, by disconnecting both power cables and Ethernet cables from the modem, router, and PC.

Related searches to no route to host

• mysqli real connect hy0002002 no route to host
• no route to host kubernetes
• Java net noroutetohostexception No route to host (host unreachable)
• destination host unreachable ubuntu
• No route to host host unreachable
• Destination host unreachable
• No route to host kubernetes
• no route to host host unreachable
• destination host unreachable
• java net noroutetohostexception no route to host host unreachable
• Destination host unreachable Ubuntu
• destination host unreachable win 10
• Stop iptables CentOS 7
• failed to connect to github com port 443 no route to host

Information related to the topic no route to host

Here are the search results of the thread no route to host from Bing. You can read more if you want.

You have just come across an article on the topic no route to host. If you found this article useful, please share it. Thank you very much.

Код: Выделить всё

[admin@MikroTik] > /ip firewall mangle                                                                                                     
[admin@MikroTik] /ip firewall mangle> print detail                                                                                                            
Flags: X - disabled, I - invalid, D - dynamic 
 0    chain=prerouting action=mark-connection new-connection-mark=allow_in connection-state=new protocol=tcp dst-port=9999 
[admin@MikroTik] /ip firewall mangle> /ip firewall nat                                                       
[admin@MikroTik] /ip firewall nat> print detail    
Flags: X - disabled, I - invalid, D - dynamic 
 0    chain=srcnat action=masquerade src-address=61.75.223.64/27 out-interface=pppoe-out1 log=no log-prefix="" 
 1    chain=dstnat action=redirect to-ports=80 protocol=tcp dst-port=9999 
 [admin@MikroTik] /ip firewall nat> /ip firewall mangle                                                                                                     
[admin@MikroTik] /ip firewall mangle> print detail       
Flags: X - disabled, I - invalid, D - dynamic 
 0    chain=prerouting action=mark-connection new-connection-mark=allow_in connection-state=new protocol=tcp dst-port=9999 
[admin@MikroTik] /ip firewall mangle> /ip firewall filter 
                                                                                                      [admin@MikroTik] /ip firewall filter> print detail       
Flags: X - disabled, I - invalid, D - dynamic 
 0    chain=input protocol=icmp 



  


                       
  



 1    chain=input connection-state=new protocol=tcp src-address=61.75.223.64/27 in-interface=br-lan dst-port=80,8291,22 


  2    chain=input action=accept connection-state=new protocol=tcp connection-mark=allow_in in-interface=pppoe-out1 dst-port=80 log=no log-prefix="" 
 3    chain=input action=accept connection-state=new protocol=udp src-address=61.75.223.64/27 in-interface=br-lan dst-port=53,123 log=no log-prefix="" 
 4    chain=input connection-state=established,related 
 5    chain=output connection-state=!invalid 
 6    chain=forward action=accept connection-state=established,new src-address=61.75.223.64/27 in-interface=br-lan out-interface=pppoe-out1 log=no log-prefix="" 
 7    chain=forward action=accept connection-state=established,related in-interface=pppoe-out1 out-interface=br-lan log=no log-prefix="" 


 8    chain=input action=drop 
 9    chain=output action=drop 
10    chain=forward action=drop 
[admin@MikroTik] /ip firewall filter> /ip route 
[admin@MikroTik] /ip route> print detail       
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 0 ADS  dst-address=0.0.0.0/0 gateway=pppoe-out1 gateway-status=pppoe-out1 reachable distance=0 scope=30 target-
 1 ADC  dst-address=61.75.213.64/27 pref-src=61.75.213.65 gateway=br-lan gateway-status=br-lan reachable distance=0 scope=10 



  


                       
  



 2 ADC  dst-address=213.231.0.200/32 pref-src=213.231.25.165 gateway=pppoe-out1 gateway-status=pppoe-out1 reachable distance=0 scope=10 
[admin@MikroTik] /ip route> /ip addres  
[admin@MikroTik] /ip address> print detail
Flags: X - disabled, I - invalid, D - dynamic 
 0   address=61.75.213.65/27 network=61.75.213.64 interface=br-lan actual-interface=br-lan 
 1 D address=213.231.25.165/32 network=213.231.0.200 interface=pppoe-out1 actual-interface=pppoe-out1 
 admin@MikroTik] /ip address> /interface
[admin@MikroTik] /interface> print detail
Flags: D - dynamic, X - disabled, R - running, S - slave 
 0  R  ;;; wan
       name="eth1-wan" default-name="ether1" type="ether" mtu=1500 actual-mtu=1500 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E4 
       last-link-up-time=jan/21/2018 15:02:12 link-downs=0 
 1   S ;;; lan
       name="eth2-lan" default-name="ether2" type="ether" mtu=1500 actual-mtu=1500 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E5 link-downs=0 



  


                       
  



 2   S name="eth3-lan" default-name="ether3" type="ether" mtu=1500 actual-mtu=1500 
 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E6 link-downs=0 


 3   S name="eth4-lan" default-name="ether4" type="ether" mtu=1500 actual-mtu=1500 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E7 link-downs=0 
 4  RS name="eth5-lan" default-name="ether5" type="ether" mtu=1500 actual-mtu=1500 l2mtu=1598 max-l2mtu=4074 mac-address=64:D1:54:9F:C8:E8 
       last-link-down-time=jan/21/2018 15:21:29 last-link-up-time=jan/21/2018 15:21:33 link-downs=1 
 5   S name="wlan1" default-name="wlan1" type="wlan" mtu=1500 actual-mtu=1500 l2mtu=1600 max-l2mtu=2290 mac-address=64:D1:54:9F:C8:E9 
       last-link-down-time=jan/21/2018 15:54:09 
       last-link-up-time=jan/21/2018 15:53:14 link-downs=2 
 6  R  name="br-lan" type="bridge" mtu=auto actual-mtu=1500 l2mtu=1598 mac-address=64:D1:54:9F:C8:E5 last-link-up-time=jan/21/2018 15:02:09 link-downs=0 
 7  R  name="pppoe-out1" type="pppoe-out" mtu=1480 actual-mtu=1480 last-link-up-time=jan/21/2018 15:19:52 link-downs=0 
[admin@MikroTik] /interface> /ip dhcp-server 
[admin@MikroTik] /ip dhcp-server> print detail
Flags: D - dynamic, X - disabled, I - invalid 
 0    name="dhcppool" interface=br-lan lease-time=8h address-pool=dhcppool bootp-support=static authoritative=yes use-radius=no lease-script="" 
       admin@MikroTik] /ip dhcp-server> /ip pool
[admin@MikroTik] /ip pool> print detail
 0 name="dhcppool" ranges=61.75.223.66-61.75.223.93 
[admin@MikroTik] /ip dns> print       
                      servers: 
              dynamic-servers: 194.143.136.1,194.143.136.2
        allow-remote-requests: no
          max-udp-packet-size: 4096
         query-server-timeout: 2s
          query-total-timeout: 10s
       max-concurrent-queries: 100
  max-concurrent-tcp-sessions: 20
                   cache-size: 2048KiB
                cache-max-ttl: 1w
                   cache-used: 18KiB