I have been able to connect to the internet for four days without any problems after the topic and support, but when I woke up this morning and was listening to music on Youtube, the internet disconnected. Same situation as the topic.
After that, I tried a loose security setting and was able to get to the DHCP address assignment, but I cannot connect to the internet. I didn’t touch the network settings, I was only browsing the internet, but is it possible to get into a situation where I can connect to the internet again?
Here there is no net connection, but only a connection, and after rebooting the network icon is crossed(x).
I am not sure why there is suddenly no internet connection, but I would like to know if there is a solution to this problem. The commands with lax security were registered in the DHCP Lerease of PFSense.
Thanks. I set the additional DNS to 220.127.116.11.9 from the connection settings. 18.104.22.168/ICMP is still in the FW logs. 22.214.171.124.9/ICMP also passes in ping. DNS queries are also seen by PFSense, but 126.96.36.199.9 is not shown. I am not sure about that.
You can install dig package in template if internet is working.
Or you can edit /etc/resolv.conf and remove or comment out all nameservers and then add specific nameserver: nameserver 188.8.131.52
or nameserver 192.168.1.1
And then try to resolve domain with browser or curl in this qube: curl https://debian.org
Maybe if it’s your ISP transient issue.
Or maybe something is wrong in PFSense DNS server configuration.
Thank you. When it comes to the root server, I am using CloudFlare addresses 184.108.40.206 and 220.127.116.11 (I think), but there may have been a fault with this address or a higher-level DNS server. The previous one was improved by detach/attach, but this time the problem may be considered to be caused by the DNS root server side.
Thanks for continuing, my PFSense DNS settings have always been set to 18.104.22.168 and 22.214.171.124. Yes, I was getting DNS Probe errors in Firefox on QubesOS, so there may be something wrong on the PFSense settings side, I’ll ask on the PFSense forums, although there may be a duplicate problem with DNSSEC being turned on. …
Thank you! You were right, it seems that the DNS Server address set in PFSense was the cause, I left the DNS Server checkbox setting on the PFSense side as is, changed the address used to 126.96.36.199/188.8.131.52 and changed the nameserver setting to the default setting in QubesOS. nameserver has also been returned to the default settings, but communication is still possible without problems.
The 184.108.40.206 and 220.127.116.11 settings were used because they were introduced in a tutorial published by a Youtuber, but when I looked into it, I found that they are addresses used in malware blocking. As for me, I just want to be able to DoH/DoT, so I will continue with this setting.