Re: [Samba] name resolves to public address - should resolve to

On Wednesday 07 May 2008, Joe Demeny wrote:
> The Windows clients are configured to look up the Samba PDC machine
> for both DNS and WINS. The Windows clients seem to be able to find
> other machines as well as the PDC:
>
> Z:\>ping pilot-ws
>
> Pinging pilot-ws [10.10.10.34] with 32 bytes of data:
>
> Reply from 10.10.10.34: bytes=3D32 time<1ms TTL=3D128
=2E..
> Z:\>ping mail
>
> Pinging mail [10.10.10.253] with 32 bytes of data:
>
> Reply from 10.10.10.253: bytes=3D32 time<1ms TTL=3D64
=2E..
> Z:\>ping mail.mycustomer.com
>
> Pinging mail.mycustomer.com [aaa.bbb.ccc.ddd] with 32 bytes of data:
>
> Reply from aaa.bbb.ccc.ddd: bytes=3D32 time<1ms TTL=3D64

This is because "mail" is most likely the systems netbios name and=20
therefore the registered netbios name in the WINS database, a dotted=20
domain name name is unusual as a netbios name but "mail.mycustomer.com"=20
wouldn't be a proper one as it is too long. So "mail.mycustomer.com"=20
will always be a domain (hosts/DNS) type lookup - the systems are not=20
asking Samba for such resolution.

> What I want is that the Windows machines resolve both mail and
> mail.mycustomer.com to 10.10.10.253.
>
> On the Samba PDC machine in /etc/hosts I have:
>
> 10.10.10.253 =A0 =A0mail.mycustomer.com =A0mail

As Dennis mentioned you can use the "hosts" file in Windows as well - it=20
will, in most cases be searched first for such name resolution (as it=20
is in 'nix).

> In smb.conf I have:
>
> =A0 =A0 wins support =3D Yes
> =A0 =A0 dns proxy =3D No
> =A0 =A0 name resolve order =3D wins host lmhosts broadcast
That's only a directive for the running Samba's own lookups - it doesn't=20
propagate to to clients.

Best solution, if your DNS handles outside requests as well, is to use=20
split horizon DNS (BIND views, as Dennis mentioned, if using that=20
product).

=2D-=20
Chris
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba