[ previous ] [ next ] [ threads ]
 From:  Adam Nellemann <adam at nellemann dot nu>
 To:  Dinesh Nair <dinesh at alphaque dot com>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Beta 1.1b10
 Date:  Sun, 30 May 2004 17:05:29 +0200
Dinesh Nair wrote:

> On Sun, 30 May 2004, Jeremias Reith wrote:
>>After upgrading to 1.1b10 m0n0wall only internal host names can be
>>resolved. The DNS Forwarder returns the refused code (5) to all clients
>>on the LAN as well to m0n0wall itself when trying to reslove an external
>>host name.
> the solution will come soon in the next image manuel releases.
> the problem was that oddly, /etc/dhclient-exit-hooks refuses to execute
> unless it is given execute permissions. it worked fine in previous
> versions of m0n0 _without_ execute perms. giving it execute permissions
> fixes the issue which jeremiah has observed.
> me thinks something changed between /bin/sh in freebsd 4.9 and 4.10.

Huh, strange? I don't seem to have this problem with my 1.1b10 
(generic-pc with DHCP'ed but static IP through ADSL).

Would this be something only some users / configurations / images see?

I've tested this by pinging a few external hosts that I was sure I 
hadn't resolved earlier (so they wouldn't be cached locally or some 
such), but perhaps I need to do something other than that to see this 
"bug" in action? (Hadn't had any other kind of DNS related problems 

FYI: I use the DNS forwarder to resolve external hosts and for a 
number of overrides (local as well as external), and this all works, 
but I haven't enabled the "Register DHCP leases in DNS forwarder" 
option (could this have anything to say?!?)