When we are setting up Codeberg Pages you need to know and be sure everything is ok on your side while DNS records are refreshing. There is a checker at https://troubleshoot.codeberg.page/verify.sh but it is only for let's say "technical users".
I have created the following HTML page that, using Google Public DNS query the DNS server to show the content of each DNS record.
Since that HTML is just for debugging (not for everyone) and is using a service that I do not recommend, I suggest to improve the HTML in the following ways and post the web for users:
- Improve the input and output of the information to let the user to write the domain and get checks with marks (OK/KO) that make easier to find the problem (for example a typo)
- Look for a Google Public DNS european alternative (see https://european-alternatives.eu/product/dns0-eu ) to DNS check on client side using Javascript and DNS over HTTPS (DoH). The server must support DNS record types, instead of only A records check.
Comments are in Spanish.
When we are setting up Codeberg Pages you need to know and be sure everything is ok on your side while DNS records are refreshing. There is a checker at `https://troubleshoot.codeberg.page/verify.sh` but it is only for let's say "technical users".
I have created the following HTML page that, using Google Public DNS query the DNS server to show the content of each DNS record.
Since that HTML is just for debugging (not for everyone) and is using a service that I do not recommend, I suggest to improve the HTML in the following ways and post the web for users:
- Improve the input and output of the information to let the user to write the domain and get checks with marks (OK/KO) that make easier to find the problem (for example a typo)
- Look for a Google Public DNS european alternative (see https://european-alternatives.eu/product/dns0-eu ) to DNS check on client side using Javascript and DNS over HTTPS (DoH). The server must support DNS record types, instead of only A records check.
Comments are in Spanish.
2.6 KiB