User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:howto:dnsdebug [2019/02/21 13:35]
jschlehofer Title is too long and it works on all our routers
en:howto:dnsdebug [2020/03/30 18:17] (current)
jschlehofer Remove wraps for pictures, add mention about opkg update, links for our new documentation
Line 3: Line 3:
 ===== Do I have DNS problem? ===== ===== Do I have DNS problem? =====
 ==== Yes, it is a DNS problem ==== ==== Yes, it is a DNS problem ====
-Often, problems related to DNS result in improbable error messages in web browsers. ​E.g. web browser claims that ''​www.google.com''​ does not exist:+Often, problems related to DNS result in improbable error messages in web browsers. ​For example, ​web browser claims that ''​www.google.com''​ does not exist:
  
-<WRAP center center align box 70%>{{:​en:​public:​debug:​firefox_server_not_found_en.png}}</​WRAP>​+{{ :​en:​public:​debug:​firefox_server_not_found_en.png?500 |}}
  
 If your web browser reports that a website does not exist while it works while using different Internet connection (e.g. when using mobile Internet connection),​ follow this guide. If your web browser reports that a website does not exist while it works while using different Internet connection (e.g. when using mobile Internet connection),​ follow this guide.
Line 12: Line 12:
 On the other hand, it is unlikely that you have a DNS problem if the page loads but reports some other error, e.g. ''​503 Server Unavailable'':​ On the other hand, it is unlikely that you have a DNS problem if the page loads but reports some other error, e.g. ''​503 Server Unavailable'':​
  
-<WRAP center center align box 70%>{{:​en:​public:​debug:​http_503_en.png}}</​WRAP>​+ 
 +{{ :​en:​public:​debug:​http_503_en.png?500 |}}
  
 This guide will likely not help you in such cases. This guide will likely not help you in such cases.
Line 23: Line 24:
  
 ==== 1. Install resolver-debug package ==== ==== 1. Install resolver-debug package ====
-Package for debugging resolver isn'​t ​the standard part of TurrisOS system, because of that it's necessary ​to install it from our repository before debugging.+ 
 +Package for debugging resolver isn'​t ​preinstalled by default in Turris OS. It needs to be installed manually.
  
 {{ :​en:​public:​debug:​install_info.png?​300 | Picture 1}} {{ :​en:​public:​debug:​install_info.png?​300 | Picture 1}}
   - Go to LuCI interface [[http://​192.168.1.1/​cgi-bin/​luci/​admin/​system/​packages|http://​192.168.1.1/​cgi-bin/​luci/​admin/​system/​packages]] (or in LuCI menu System->​Software)   - Go to LuCI interface [[http://​192.168.1.1/​cgi-bin/​luci/​admin/​system/​packages|http://​192.168.1.1/​cgi-bin/​luci/​admin/​system/​packages]] (or in LuCI menu System->​Software)
 +  - Update lists by pressing the button (you can do it in CLI with command **opkg update**)
   - Write **resolver-debug** to textbox //Download and install package// ​ and click to OK button (number one in Picture 1)   - Write **resolver-debug** to textbox //Download and install package// ​ and click to OK button (number one in Picture 1)
  
Line 51: Line 54:
  
 ==== 4. Send the logs to support ==== ==== 4. Send the logs to support ====
-Follow instructions on page [[en:howto:​error_reporting|Error reporting]] and send your logs to support. Please note that procedure listed above supersedes part //How to get logs// on page [[en:howto:​error_reporting|Error reporting]] :-)+Follow instructions on page [[https://​docs.turris.cz/​basics/​support/​|Error reporting]] and send your logs to support. Please note that procedure listed above supersedes part //Getting ​logs// on page [[https://​docs.turris.cz/​basics/​support/​|Error reporting]] :-)