non-ms clients not working for subnet.

[Billy Reubin]

hello,

I have a Windows 2000 AD setup with 2 domain controllers acting as DNS
servers...

everything works great, I even have DHCP servers setup and Dynamic
registration...

except I have some Unix clients that cannot use the DNS servers for
any resolving hosts
on my local subnet...

if I goto ping a server "gumby" or gumby.abc.local it tells me host
unknown....
If I go into DNS and re-define gumby and tell the DNS server gumby is
on some
other non-local subnet, (Let's say my local network is 192.168.1.0/24)
let's make gumby 192.168.2.1, even though gumby does not exist on that
network
or ip address it still resolves it, and try's to ping it...

I change gumby back to be what it is supposed to be (192.168.1.5/24)
and goes back
to telling me host unknown... I pop into NsLookup and verify the
record just fine...
but cannot ping by the host name.

does this make sense to anyone?

Gumbus.

 

[Herb Martin]

if I goto ping a server "gumby" or gumby.abc.local it tells me host

unknown....
If I go into DNS and re-define gumby and tell the DNS server gumby is
on some
other non-local subnet, (Let's say my local network is 192.168.1.0/24)
let's make gumby 192.168.2.1, even though gumby does not exist on that
network
or ip address it still resolves it, and try's to ping it...

Let's not say that -- the chance are very strong that you problem is
a trivial misconfiguration that you just can't see so don't translate or
even type in the details but either "cut and paste" or "redirect to a file"
to show us the values.

Send us (the equivalent of) IPconfig output and the actual NSlookup
results.

I change gumby back to be what it is supposed to be (192.168.1.5/24)
and goes back
to telling me host unknown... I pop into NsLookup and verify the
record just fine...
but cannot ping by the host name.

does this make sense to anyone?

Yes, since the Internet works with a variety of machine times -- IP
is generic -- there is a 99% chance you have something misconfigured.

Also show us the "route print" or "netstat -r" or equivalent.

 

[Kevin D. Goodknecht [MVP]]

In

hello,

I have a Windows 2000 AD setup with 2 domain controllers acting as DNS
servers...

everything works great, I even have DHCP servers setup and Dynamic
registration...

except I have some Unix clients that cannot use the DNS servers for
any resolving hosts
on my local subnet...

if I goto ping a server "gumby" or gumby.abc.local it tells me host
unknown....
If I go into DNS and re-define gumby and tell the DNS server gumby is
on some
other non-local subnet, (Let's say my local network is 192.168.1.0/24)
let's make gumby 192.168.2.1, even though gumby does not exist on that
network
or ip address it still resolves it, and try's to ping it...

I change gumby back to be what it is supposed to be (192.168.1.5/24)
and goes back
to telling me host unknown... I pop into NsLookup and verify the
record just fine...
but cannot ping by the host name.

does this make sense to anyone?

Gumbus.

You won't be able to ping 192.168.2.1 from a 192.168.1.0/24 network. It is
out of the subnet range the last usable IP in a 192.168.0/24 subnet is
192.168.1.254. If you need to access addresses in a 192.168.2.0 subnet you
need to change the Netmask to 255.255.252.0 which is a 192.168.1.0/20
network

CIDR range 192.168.1.0/22
Netmask 255.255.252.0
Wildcard Bits 0.0.3.255
First IP in range 192.168.0.0 (network address)
Last IP in range 192.168.3.255 (broadcast address)
First useable IP in range 192.168.0.1
Last useable IP in range 192.168.3.254
Number of useable IPs in range 1022

 

[Billy Reubin]

Hello,

thanks for taking the time to help with my problem...

after 3 months, I figured out why...

Our Unix clients are actually Mac OS X,
and it appears that there is a ZeroConfig
problem with trying to resolve .local
addresses...

I thought the problem was with Microsoft's DNS server and
some sort of security setting, that would not let non microsoft
clients resolve any .local (or active directory) hosts.

thanks again.

Cheers,
Gumbus

after many months I found this article:
---------------
I experienced the same problem of OS X Macs not being able to resolve
..local addresses on my internal LAN. After scouring the net, I found
this fix that worked:

Open the Terminal Application

Type the following (Must have root privilege or sudo account): sudo
pico /etc/resolver/local

You will see three lines in the file: nameserver ipaddress, port
5353, timeout 1

On the nameserver line, replace the current IP address with the
address of your local DNS server: for example nameserver 10.0.0.1

On the port line, replace 5353 with 53.

Save your changes and quit pico.



You should be able to resolve .local names properly.
----------------------------------------------------