[KLUG Members] I have a couple questions.

[Jeremy Leonard]

> > 1. I know I've seem Mac stuff here before so I hope it's ok to ask
> > this
> > question. I have a lab of 30 emacs. I just upgraded them from
> > Jaguar to
> > Panther. I use eDir on Novell NetWare 6.5 for auth and the home
> > directories
> > are on this server too. Everything worked fine with 10.2.8 but
> > after
> > upgrading. I get a message that states "My home directory is on a
> > SMB or AFP
> > share. You cannot login at this time. Please contact you
> > administrator." The
> > only doc I could find on Apple's site said to disable fast user
> > switching.
> > It is already. Has anyone seen this or know how to fix it?
>
> I am not sure on your first one.  Did you check on Novells tech
> support website?
>

I did. I didn't find anything.

> >
> > 2. At my house I use a single Suse 9.0 box as my
> > fileserver/Firewall/DNS/email/web and anything else I can't remeber
> > right
> > now. what I want to know is can I use BIND to run two seperate
> > zones. One
> > for the internet and one for my lan for the same domain. For the
> > lan I want
> > to resolve to local addresses. For the Internet I want to resolve
> > to public
> > addresses. I know how to set this up with multiple boxes but I only
> > have
> > one. If so, where can i find some info on setting this up?
>
> I think that you have worded the question a bit wrong.  What you are
> wanting to do is to run a DNS domain for a private domain on the
> Internal LAN and still be able to resolve Internet addresses.  You
> can setup the DNS server (BIND) with a zone for the domain that you
> want to use internally (something like home.local).  You then point
> the clients to your firewall box as the DNS server.  If the client is
> looking up something in home.local then your DNS server will respond
> with the address.  If the request is for something other than the
> local segment then the server will perform a lookup by contacting the
> root zone on the Internet and going from there.  It is pretty
> straight forward.
>
> If you are using Windows with Active Directory on the internal
> network and want to use the Windows DNS server you can either point
> to that (the server will talk through the firewall to do a lookup) or
> you can setup the Windows DNS server to use a forward pointing to the
> DNS server for the Internet if it cannot resolve the address locally.


I don't think I worded it wrong. The box I'm using IS the DNS for my public
domain. elite4god.com I want people on my lan to resolve hosts in that
domain to their 192.168.x.x addresses. You can't go out a nat and back in so
if a user on my lan enters www.elite4god.com into their browser it doesn't
come up. They get unknown host. If I ping that DNS name I get the public
address. I want to run two DNS servers each one only listens on one nic. The
LAN side returns LAN addresses for my zone and the public side returns the
public addresses. I don't want my users to have to use a different dns name
if they are on the lan as apposed to when they are connected to the Internet
through some other way.