cant update caps - could not resolve dns name

RouterOS Beginner Basics
1

Hello,

I have hex S as router (there is also capsman set), which can “check for updates” and update. Then I have 2x C52iG-5HaxD2HaxD configured (reseted) as caps. normal traffic is ok and everything works as should. But im not able to update these caps, I got “Err: could not resolve dns name”.

I found hint to: set new static DNS record, but not work.

Can someone hint me, where i should look?

Thanks

2

Does ping from CLI of that devices resolves DNS names? Does ping to any public IP work? Is gateway and default route set properly?
They can work locally but have no outside conectivity.

3

Hi,

I’ve checked this and no, I cant ping from caps outside my lan. I thought I should work if all devices in connected to caps works fine and caps are managed from capsman. So I have screwed my config.

caps have just basic config:

/interface wifi datapath
add bridge=bridge-LAN comment=defconf disabled=no name=CAP-datapath
/interface wifi
# managed by CAPsMAN
set [ find default-name=wifi1 ] configuration.manager=capsman datapath=\
    CAP-datapath disabled=no
# managed by CAPsMAN
set [ find default-name=wifi2 ] configuration.manager=capsman datapath=\
    CAP-datapath disabled=no
/interface bridge port
add bridge=bridge-LAN comment=defconf interface=ether1
add bridge=bridge-LAN comment=defconf interface=ether2
add bridge=bridge-LAN comment=defconf interface=ether3
add bridge=bridge-LAN comment=defconf interface=ether4
add bridge=bridge-LAN comment=defconf interface=ether5
/interface wifi cap
set discovery-interfaces=bridge-LAN enabled=yes slaves-datapath=\
    CAP-datapath
/ip address
add address=10.0.0.251/24 interface=bridge-LAN network=10.0.0.0
/system identity
set name=AP1 # (AP2 for another device)

So the problem is on caps’ side or on main router (hex S) or both side?

4

CAPs as they have to know how to get outside.
Set them manually IP, GW, default route and DNS and they should work. Or just let them obtain that data from DHCP.