Hi, I dont know where to look in the settings or logs
I have IPFire working on a small pc (standalone) and everything seems to work OK
However after running for a couple of days the other workstations are unable to connect to each other using domain name such a homeassistant.local:8123
This should open the home assistant server but it fails, this happens on several things the same with time out and unable to connect.
I can access them by IP address with no problem so I assume it is local domain issue. if I type a web domain www.microsoft.com it is OK
or my web address www.si-tech.com.hk is also fine.
After a restart of IPFire everything is back to normal.
Where do I start to find what is happening.
Regards
Berni
A local DNS problem
Local DNS hostnames are registered in Unbound
- Either registered in DHCP using the name defined in the field “Remark” for fixed leases
- Or provided by the client upon DHCP connection
(The default domain is the IPFire server domain in this case)
www.ipfire.org - DHCP Server - Or registered in the hosts page (host and domain)
www.ipfire.org - Edit Hosts
This latter takes precedence over the others
1 Like
Hi Thanks for the quick reply.
However I dont see how this helps me,
when using the system and on inspection before the error and after the error.
Status of the systems DNS is displayed. This shows Working in green text
even when machines are unable to connect to each other it shows working.
The address of the workstations does not change, I need to know what and where to look to see what is the issue.
.
I dont want to go back to using my TP Link router / firewall as it is not very secure. it works OK but not good security
I also reported issues with the local DNS.
https://community.ipfire.org/t/local-dns-not-reliable
I was kindly informed here that this was only the case for me.
So I managed to resolve my issues by applying these rules:
- Define hosts (Remark field) for fixed leases in the DHCP page
- Define only static hosts in the hosts page
But not in both.
This rule worked for me, but it hasn’t been validated by the community.
If you provide a little more information about your configuration, others will certainly be able to help you.
A status of working doesn’t mean that the information of unbound is complete.
As @pscar13 mentioned there are several sources of namespace information.
They report (name, domain, IP) tuples to unbound. If there are multiple entries for the same IP with different domains, it is up to the selection algorithm of unbound to chose an answer. I don’t exactly know, how this is implemented.
But you can check, whether the various ways deliver consistent information.
See pscar13 link to Edit Hosts (5)
This works for me.
Have lots of Local PC’s with fixed IP’s and Host names
configured in “Edit hosts” this works for local name resolution.
I’m even pointing the names to a NginX proxy manager.
Work Great. And no more security warnings.
1 Like
Hi And thanks to each for the helpful information
I will wait till tomorrow as I am setting up a new system for the firewall
with 6 x 2.5G lan port, Intel N100 CPU 4 core 8 thread, 16Gb DDR5 ram & 128GB ssd M2
will set as Red, Orange, and all others Green