Bug #15127
closed
``check_dnsavailable()`` failing even when DNS is available
Added by Kris Phillips 11 months ago.
Updated 11 months ago.
Plus Target Version:
24.03
Affected Architecture:
All
Description
In the file /usr/local/www/services_acb.php there is a call on line 233 to "check_dnsavailable" which queries against 8.8.8.8 using a function in /etc/inc/system.inc. Recently a change to Google's DNS servers has broken this function.
Currently, this can be worked around with the following one-line command until a system patch can be made on 23.09.1:
awk 'NR==233 {$0="if ((!($_REQUEST['\''download'\'']) || $input_errors)) {"} 1' /usr/local/www/services_acb.php > temp && mv temp /usr/local/www/services_acb.php
Files
The attached workaround patch may be applied using the System Patches package until a proper fix is available via the recommended patches.
Simply add a new patch using the URL https://redmine.pfsense.org/attachments/download/5796/15127.patch
, save, then apply.
- Subject changed from ACB doesn't show backups due to check_dnsavailable PHP call even though they're available to ACB doesn't show backups when Google DNS fails
- Status changed from New to Assigned
- Assignee set to Marcos M
- Target version set to 2.8.0
- Plus Target Version set to 24.03
verified prior condition and that ACB restore entries were once again present following application of the patch above
- Subject changed from ACB doesn't show backups when Google DNS fails to ``check_dnsavailable()`` failing even when DNS is available
- Category changed from Auto Configuration Backup to PHP Interpreter
This affects a lot more than just ACB. It affects DHCP lease display, ARP display, NDP display, update checks, and potentially other related areas along with ACB.
- Has duplicate Bug #15129: Arp table not displaying hostname added
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
- Status changed from Feedback to Resolved
I applied the patch and tested all the services that were potentially affected.
ACB worked fine.
The DHCP lease page worked fine.
The NDP table had entries.
The firewall was able to check for updates.
I am marking this ticket resolved.
Also available in: Atom
PDF