Right, I've done that.  I've set the DNS servers to 192.168.x.x and  
those get passed to the clients properly.  If you look at the  
resolv.conf on an OSX client after a connection, it looks like

nameserver 192.168.x.x
nameserver 192.168.x.y

but I want it to look like

domain bar.com
nameserver 192.168.x.x
nameserver 192.168.x.y

Windows clients behave in a similar way, not getting the default  
search domain.  The domain is set to bar.com in the general setup on  
the monowall, but it doesn't seem to get passed to the clients.

thanks,
jay


On Oct 5, 2006, at 9:53 AM, SDamron wrote:

> You need to assign DNS automatically to the pptp client and setup DNS
> names for your servers in m0n0.  There is documentation for this on
> the site, can't remember the exact link, but do some searching, and
> you will find it.
>
> On 10/5/06, Jay Lyerly <jayl at ceintl dot com> wrote:
>> Is there any way to assign a default DNS search domain to pptp
>> clients?  I have an internal web server named foo in the domain
>> foo.bar.com.  On my internal hosts, http://foo works b/c they are set
>> to search bar.com.  This setting isn't passed to PPTP.  From a pptp
>> machine, http://foo doesn't work, but http://foo.bar.com does.
>>
>> Under both windows and OSX, you can set the search domain on the
>> client side, but its many clicks and something my users are
>> invariable not get quite right.  I was using the PPTP server on OSX
>> Server edition which managed to set the default search domain on
>> clients.  Unfortunately, as a PPTP server, it wasn't all to stable.
>>
>> So, can the PPTP server broadcast its DNS search domain to clients?
>>
>> thanks,
>> jay
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>>
>>
>
>
> -- 
> -------------------------------
> A morning without coffee is like something without something else.
>