I run two ipfire devices. Since Monday, I haven’t been able to access websites at the office—neither internal nor external. The issue only resolves for a few minutes after I restart the ipfire. I’ve tried a great many things with the help of the AI, but everything has failed. DNS resolution simply isn’t working.
Now here’s the crazy part: at noon today, I wa s at home, where the other ipfire is located. Nothing’s working here either now, even though I haven’t changed anything there. The same symptoms. By process of elimination, that really leaves only the ISP (Telekom) or a bug in version 203, right?
Can you please help me? Thanks
What does the Domain Name System configuration look like on a malfunctioning IPFire system?
And does the connection work without using an FQDN—for example, ping 1.1.1.1?
Hi Alexandr, thanks for your reply. Pinging the IP address works, but name resolution doesn’t. I’ve already tried a lot of things in the DNS settings. Currently, 1.1.1.1 is set as the DNS server, and the DNS servers assigned by the ISP are disabled. But it didn’t work with those either. The protocol is UDP, Safe Search is disabled, and “Include YouTube” is enabled.
And what does the DNS firewall configuration look like?
Everything is deactivatet, all forms are empty
In that case, I would also try removing all DNS servers from the Domain Name System configuration and restarting IPFire.
In this configuration, the IPFire Domain Name System should operate in recursive mode, similar to other recursive servers.
Have you tried with another DNS server, Lightning Wire Labs for example?
I tried 1.1.1.1, 8.8.8.8 and the ISP-DNS-Servers. Which IP do I have tu try for Lightning Wire Labs?
As stated in the wiki it is 81.3.27.54
Another check would be to switch to recursor mode ( no DNS server enabled ).
I tried both, the Lightning Wire Labs-Server and without server. Same issues.
I can’t seem to figure out a pattern in the errors. I can’t access Deepl.com, but ipfire.org works. The same goes for other sites, though most of them don’t work. Within the green network, DNS resolution doesn’t work at all anymore.
Please check:
System Logs, Domain Name System
And check if it’s a browser issue.
For example, ping the FQDN that isn’t working.
Configuring a resolver on the end host—for example, 8.8.8.8—should clearly indicate whether the problem lies with the IPFire Domain Name System.
The ping to the URL didn’t work. I’m attaching a screenshot of the latest entries in the system log of the ipfire at home, where I am right now. I’ll be heading back to the office shortly and will check it there as well. I’ve now entered 8.8.8.8 directly into the network adapter and can access all external sites again. It really does seem to be a DNS issue.
The attached log shows an issue with Domain Name System handling on IPFire; the question remains as to what the RAM/CPU load looks like.
Does this help?
Yes, one more question about services:
Status, services
In my opinion, the problem is related to RAM being clogged up by something—most likely a malfunctioning DNS Firewall.
I suggest removing all selected lists (wait for the process to finish),
restarting IPFire, and checking if the memory has been freed up.