this is a very annoying "feature" of windows. when you ping a name
windows
first tries a netbios name resolution (through wins or ip broadcast) then
after, only if needed, a dns resolution.
suppose you have on your lan 3 win$ machines :
- machine 1 with ip 1.1.1.1, netbios name NAME1
- machine 2 with ip 1.1.1.2, netbios name NAME2
- machine 3 with ip 1.1.1.3, netbios name NAME3
and in your dns server the following entries
- NAME1 IN A 1.1.1.2
- NAME2 IN A 1.1.1.1
from machine 3, if you "ping NAME1" you'll get an answer from
machine 1
with ip 1.1.1.1, but if you "ping NAME1.yourdomain.com" you'll get
an
answer from machine 2 with ip 1.1.1.2
now if machines 1 and 2 do not handle smb (basically non win$ machines)
then when you "ping NAME1", netbios name resolution will fail, then a
dns
name resolution will occur in which your (machine 3) default domain name
will be appended to NAME1, and you'll get an answer from machine 2 (which
has DNS name NAME1 and netbios name NAME2)
maybe there's one more of many magic registry tricks that prevents this
behaviour ? if somebody knows...
note that in your case the netbios name resolutions still works though both
machines are NOT on the same ip subnet : it's because you configured
"cofr3" as wins server on your client
about your named.conf file I think it won't work as it is : you have
configured it as "forward only", so named won't try and resolve
any query
locally, even queries against the "cofrny.gov" zone will be forwarded
(and
of course you'll get a NXD response). read about BIND and change your
configuration.
hth
A 10:21 31/12/2002 -0500, vous avez ?crit :>I can ping the virtual Linux servers NetBIOS name and access a share.
Perhaps someone can examine the attached named.conf file for errors and/or
omissions.>
>My virtual Linux server (172.17.60.6) has been configured as a WINS
server, and a PDC. I am not, however, certain how to configure it as a DNS
server beyond what is in the attached named.conf file. >
>Here are the results of pinging the virtual Linux servers NetBIOS name
followed by the results of pinging the DNS name:>
>C:\>ping cofr3
>
>Pinging cofr3 [172.17.60.6] with 32 bytes of data:
>
>Reply from 172.17.60.6: bytes=32 time=10ms TTL=254
>Reply from 172.17.60.6: bytes=32 time<10ms TTL=254
>Reply from 172.17.60.6: bytes=32 time<10ms TTL=254
>Reply from 172.17.60.6: bytes=32 time<10ms TTL=254
>
>Ping statistics for 172.17.60.6:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 10ms, Average = 2ms
>
>C:\>ping cofr3.cofrny.gov
>Unknown host cofr3.cofrny.gov.
>---------------------------------------------------------------------------
------------------------------>
>Here is the workstation IP configuration:
>
>C:\>ipconfig /all
>
>Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : city-f5pfa29xta
> Primary DNS Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : cofrny.gov
>
>Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : cityofrochester.gov
> Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Ethernet>Controller (3C905C-TX Compatible)
> Physical Address. . . . . . . . . : 00-06-5B-4A-26-C6
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 172.16.4.251
> Subnet Mask . . . . . . . . . . . : 255.255.248.0
> Default Gateway . . . . . . . . . : 172.16.0.50
> DHCP Server . . . . . . . . . . . : 172.16.0.121
> DNS Servers . . . . . . . . . . . : 172.17.60.6
> 10.100.224.51
> 10.100.224.52
> Primary WINS Server . . . . . . . : 172.17.60.6
> Lease Obtained. . . . . . . . . . : Sunday, December 29, 2002
1:25:15 AM>
> Lease Expires . . . . . . . . . . : Wednesday, January 01, 2003
1:25:15>---------------------------------------------------------------------------
------------------------------>
>Clearly the workstation is on the 172.16.0 subnet while the server ison
the 172.17.60 subnet. I was hoping that this would be addressed by
specifying remote announce in the smb.conf file for the workstations
subnet. Apparently I am still missing something.>
>Any assistance would be greatly appreciated.
>
>
>
>Attachment Converted: "d:\app\net\eudora\attach\named.conf"
>
- * - * - * - * - * - * -
Bien s?r que je suis perfectionniste !
Mais ne pourrais-je pas l'?tre mieux ?
Thierry ITTY
eMail : Thierry.Itty@Besancon.org FRANCE