After the upgrade , some websites resolved some are not, my dhcp server serving ip to hosts with dns of his own address 192.168.10.1 (ipfire ip ) and websites doesnt resolved , but if i insert dns (8.8.8.8) manually in the nic its resolving . whats going on here ?
in core 202 it was perfectlly ok
see
i did it, and it did absolutely no difference .
In the post IPFire 2.29 - Core Update 203 released - #40 by bonnietwin I read that there have been a bug raised a for some of the DNS problems. I added Secondary DNS 1.1.1.1 (or 8.8.8.8 if you like) in DHCP settings and DNS Servers, until it is fixed, and it seems to work for devices on green now. So if you problems are related to mine/others, maybe try that?
i disconnect the clients and did a lot more then that.
current situation :
hosts the request dns resolving via ipfire not working , if manually inserted 8.8.8.8 via NIC getting resolved to all websites
yes that is also what i did to currently bypass the issue, iv insert secondery dns to the dhcp configuration
i have no idea what is a recursor mode i never configured it like that, everything worked fine before the upgrade.
That looks like the configured DNS servers are not working.
Click ‘Check DNS servers’, what status is reported when you hover over the result.
wierd…
my iphone getting resolved completely fine
Your 2nd screenshot shows two differences
This leads to status ‘Working’.
What’s the status of ‘Check DNS Servers’?
i already did it few times, they return OK. there is no problem with the dns servers. its seems the issue is with the ipfire’s dns service that doesnt forward dns requests from the clients out to the dns servers. its working only if the clients getting secondary dns server like 8.8.8.8 from the dhcp entries
Something looks unusual with your DNS resolution.
Why does nslookup google.com return forcesafesearch.google.com? That is not the expected behavior with IPFire.
Even when Enable Safe Search is enabled, IPFire should only redirect www.google.com, not google.com.
Could this be a restriction or DNS filtering imposed by your ISP?
You could also try restarting the resolver and clearing its cache:
/etc/init.d/knot-resolver restart
Wait a few seconds after the restart, then run:
kresctl cache clear
i’m having what i think is a similar issue. most domains resolve ok and the page loads, however some do not unless i add a secondary DNS server to my dhcp configuration, a DNS server other than ipfires (8.8.8.8) as stated in a prior comment here.
i have tried flushing the knot-resolver cache, restarting, rebooting the firewall, disabling dns firewall, changing from tls to udp in my dns configuration. everything i can find, thus far the only thing that is allowing all domains to resolve is to not use ipfire’s dns.
yep.
looks like the exact same issue. btw what hardware your ipfire runs on ?
and do you have any ideas how to solve it ?
because i dont think someone here or any of the developers/maintainers knows how to solve it or even what the cause of it
I made a mistake; that configuration was correct.
However, it seems your ISP is filtering DNS requests.
Check if you have access to the root DNS servers.
kdig . NS
i don’t think my issues are hardware related. i upgraded from 202 and have been using ipfire for 10+ years now without issue. the dns change is a big one, and i’m sure there is/will be a fix, it’s definitely not obvious to me what it is though.
hardware wise, i run some older hardware that i had laying around/acquired for very cheap. intel xeon e3-1240l, connectx-4 lx dual port card, an intel i226-v dual port card, and 16 gb of ram. overkill for the house network, it’s really solid though and never fails.