DNS Resolver Host Override not working
- 
 @johnpoz said in DNS Resolver Host Override not working: That is pfsense trying to get something with nginx? Yeah, what is this : @l0rdraiden said in DNS Resolver Host Override not working: ...... open() "/usr/local/www/index.php/204" failed (20: Not a directory), client: 192.168.1.30, server: , request: "GET /index.php/204 HTTP/1.1", host: "ne*********.duckdns.org" 
 .... open() "/usr/local/www/ocs/v1.php/cloud/user" failed (2: No such file or directory), client: 192.168.1.30, server: , request: "GET /ocs/v1.php/cloud/user?format=json HTTP/1.1", host: "tc***s.duckdns.org"/index.php/204 => this doesn't exists on pfSense (the web server / files ). 
 //ocs/v1.php/cloud/user => same thing.Just the browser who 'thinks' it's connected to some site, but redirected to the pfSense webroot, and obtaining a "non - not here". 
- 
 @Gertjan you think that is something to do with his host override trying to ask pfsense for something... I can not really tell what that error is without more context. 
- 
 Realy, .... dono. I guess @l0rdraiden want to reach a local server (coming from local), the server he exposes on the Internet using a duckdns.org DDNS domain name. 
 Local host overrides always worked for me, using the default Resolver.
- 
 yup zero issue with them.. But I don't see how an error on pfsense for nginx has anything to do with unbound? 
- 
 IMHO, the errors are cached URL's in a browser, that thinks it's connected to a webserer (dsame URL) but it is connected to the GUI (or portal web server). 
 It's hitting the server (nginx) with the stored URL's and nginx is complaining about it.
 I see this all the time on my own web servers : the most strange page requests are popping up - and errored out by the web server.
- 
 @johnpoz said in DNS Resolver Host Override not working: @Gertjan you think that is something to do with his host override trying to ask pfsense for something... I can not really tell what that error is without more context. He disabled Resolver Live Sync in DNSBL and it seems to work fine for now. 
- 
 @ronpfs said in DNS Resolver Host Override not working: Resolver Live Sync I read about this (new ?) option. Not finding much btw. 
 unbound man pages do not mention them.Isn't it a somewhat hidden : "do a restart" ? 
 As far as I know, bind, for example, places "watches" on files, and read them in on the fly when they changed - without a global restart.
- 
 @gertjan 
 It's basically a bunch of unbound-control cmds to change the local-data and local-zone in unbound live db.
 Something the DHCP services could do to register new leases. But now BBcan177 has implemented a Python module to unbound.  . .
 It's faster, has more functionality and doesn't require GBs of memory for unbound. 
- 
 Ah, if so, then that looks good. 
 This should be implement upstream (in pfSense itself).
 No more x restarts a minute on big networks, thus no more flushing the DNS cache.And pfBlockerNG users would be really happy (parsing these mega block files take time every restart). 
- 
 The issue is posted here finally 
 https://forum.netgate.com/topic/140021/dns-resolver-host-override-not-working/21
 
 


