Cameron Kerr wrote:

> Fred Emmott <pcfreak65@hotmail.com> wrote:
>
>> they are all in the same reverse lookup zone (192.168.0) - are you saying
>> that you cant have more than one tld in 192.168.0.x ? i'm not sure sure
>> if i was clear what i meant - the linuxserver master zone works fine, and
>> the lan master zone works fine, and the other 2 work fine from linux/bsd,
>> but not from windows xp. if i get your meaning right, only one of
>> "linuxserver" or "lan" should work, not both, but all 4 work fine from
>> linux/bsd, but even from windows 2 of them work.
>
> If you have a master zone called {linux,freds,jonys}server, then you
> would have something in those domains, such as
>
> bob.linuxserver
> foo.linuxserver
> joe.fredsserver
>
> You can indeed have PTR records in 192.168.0 pointing to different
> domains, that's fine (and in the days of CIDR, sometimes necessary)
>
> What are the _purposes_ of {linux,freds,jonys}server ? and of "lan" ?
>
> If I had a clearer idea of what you are trying to ultimately achieve, I
> could steer you in a better direction.
>
> PS. I'm currently moving, so I'll be off the internet for a couple of
> days soon.
>

linuxserver is a real dns/apache/irc/ftp server
{freds,jonys}server point to the same ip address as
{freds,jonys}.linuxserver, which is an IP-based apache virtual host, using
eth0 aliases.

With the exception of server.lan, which points to linuxserver, *.lan point
to individual user's computers, so if a certain user has a problem, i just
need to "ssh <user>.lan"