Community discussions

MikroTik App
 
User avatar
Frederick88
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 51
Joined: Thu Jun 24, 2021 12:34 pm

Check for Updates: could not resolve DNS name

Wed Jan 10, 2024 4:30 am

I'm on 7.13 stable.

what's the easiest way to update to 7.13.1 since the internal dns is broken with 7.13 ?

(considering the bug present in 7.13, I would have thought this info would be readily available on the announcement page along with 7.13.1 update?)

Thanks
 
User avatar
Frederick88
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 51
Joined: Thu Jun 24, 2021 12:34 pm

Re: Check for Updates: could not resolve DNS name

Wed Jan 10, 2024 4:37 am

I found answer and tried deleting original post, but loads a blank page after I click delete?

anyway, for anyone else wondering the same thing, create a static DNS A record
upgrade.mikrotik.com > 159.148.147.204
update
remove A record
 
User avatar
Frederick88
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 51
Joined: Thu Jun 24, 2021 12:34 pm

Re: Check for Updates: could not resolve DNS name

Wed Jan 10, 2024 5:03 am

actually it seems I have DoH DNS issue..

DoH server connection error: SSL: ssl: no trusted CA certificate found (6) [ignoring repeated messages]

this just started happening earlier before I attempted to update...
 
User avatar
loloski
Member
Member
Posts: 457
Joined: Mon Mar 15, 2021 9:10 pm

Re: Check for Updates: could not resolve DNS name  [SOLVED]

Wed Jan 10, 2024 5:12 am

Download and import this cert if you are using cloudflare DNS it should work
https://cacerts.digicert.com/DigiCertGl ... G2.crt.pem
 
User avatar
Frederick88
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 51
Joined: Thu Jun 24, 2021 12:34 pm

Re: Check for Updates: could not resolve DNS name

Wed Jan 10, 2024 5:12 am

turns out Certificate issue.

see viewtopic.php?p=1047487&hilit=DOH#p1047487
 
rrd
just joined
Posts: 11
Joined: Mon May 09, 2022 6:08 pm

Re: Check for Updates: could not resolve DNS name

Thu Jan 11, 2024 12:15 am

I had the same problem. I was using CF DoH server.
Imported "DigiCertGlobalRootG2.crt.pem" cert and it started working again.