Problems with BIND and a windows XP computer

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, heres the layout of the server:

eth0 - 192.168.0.2, in bind as a master zone called "linuxserver"
eth0:0 - 192.168.0.3, in bind as a master zone called "fredsserver"
eth0:1 - 192.168.0.4, in bind as a master zone called "jonysserver"

there's also a "lan" master zone which resolves:

fred.lan to 192.168.0.87
james.lan to 192.168.0.1

My other linux computer can lookup all of the host names correctly. However
the windows XP computer can not lookup fredsserver or jonysserver. Any
ideas?

Fred
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFABpdEDvn9hyzHIq4RAo5cAJ93ayTftiBTfm/XX58GVN/5RfFU7wCggSqV
yWKHr8mQiMokb1PJG4a6Y+s=
=Rvs4
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Cameron Kerr wrote:

> Fred Emmott <(E-Mail Removed)> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi, heres the layout of the server:
>>
>> eth0 - 192.168.0.2, in bind as a master zone called "linuxserver"
>> eth0:0 - 192.168.0.3, in bind as a master zone called "fredsserver"
>> eth0:1 - 192.168.0.4, in bind as a master zone called "jonysserver"
>
> What the!?! Read the DNS HOWTO, you're design is fundamentally flawed.
>
> 192.168.0.* should all be in the same zone. *server should have A
> records in something like localdomain (or lan perhaps in your case).
>
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.

i have read the howto, but i can not see where it says that. Any chance you
can explain a bit more?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFABxrZDvn9hyzHIq4RArVAAKCT/rGqjdCqeXtvOcsiExnHVMClFQCeO4cj
v8yH3jxBT7Mahs617xrNefM=
=cK7z
-----END PGP SIGNATURE-----

Fred Emmott <(E-Mail Removed)> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, heres the layout of the server:
>
> eth0 - 192.168.0.2, in bind as a master zone called "linuxserver"
> eth0:0 - 192.168.0.3, in bind as a master zone called "fredsserver"
> eth0:1 - 192.168.0.4, in bind as a master zone called "jonysserver"

What the!?! Read the DNS HOWTO, you're design is fundamentally flawed.

192.168.0.* should all be in the same zone. *server should have A
records in something like localdomain (or lan perhaps in your case).

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

Fred Emmott <(E-Mail Removed)> 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.

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

Cameron Kerr wrote:

> Fred Emmott <(E-Mail Removed)> 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"

Fred Emmott <(E-Mail Removed)> wrote:

> 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"

Well then, you need to move *server into a domain of its own, probably
into your lan TLD.

The reason it probably doesn't work on Windows is because IE will add a
suffix (.com, .net, .org) to anything without a TLD. It's quite
braindead. I'm glad I don't have to mess with that shite much.

PS. What does the following output

dig +short -t A linuxserver

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

Cameron Kerr wrote:

> Fred Emmott <(E-Mail Removed)> wrote:
>
>> 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"
>
> Well then, you need to move *server into a domain of its own, probably
> into your lan TLD.
>
> The reason it probably doesn't work on Windows is because IE will add a
> suffix (.com, .net, .org) to anything without a TLD. It's quite
> braindead. I'm glad I don't have to mess with that shite much.

It's not just IE - ping and anything network related

though "linuxserver" works

>
> PS. What does the following output
>
> dig +short -t A linuxserver
>
192.168.0.2

fredsserver reports 192.168.0.3

btw a less typing intensive alternative is "host linuxserver"

Fred

Cameron Kerr wrote:

> Fred Emmott <(E-Mail Removed)> wrote:
>
>> It's not just IE - ping and anything network related
>>
>> though "linuxserver" works
>
> Perhaps then its only ever adding the search path, since its an
> unqualified name. After all, there should be no host in the TLD.
>
>> btw a less typing intensive alternative is "host linuxserver"
>
> Yes, I'm well aware of that.
>
sorry didn't mean it offensivily - thanks for your help - and heres more
info:

just added another windows xp computer, and it can also lookup fredsserver,
but not jonysserver - so i'm pretty certain this is a windoze issue, so
will post in some windows network ng

Thanks,

Fred

Fred Emmott <(E-Mail Removed)> wrote:

> It's not just IE - ping and anything network related
>
> though "linuxserver" works

Perhaps then its only ever adding the search path, since its an
unqualified name. After all, there should be no host in the TLD.

> btw a less typing intensive alternative is "host linuxserver"

Yes, I'm well aware of that.

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!