On 06/05/2017 11:13 PM, Walter H. wrote:
On Mon, June 5, 2017 22:25, Samuel Sieb wrote:
On 06/05/2017 11:44 AM, Walter H. wrote:
On 05.06.2017 20:38, Samuel Sieb wrote:
nslookup resolved the .local addresses? That's surprising and might
be a problem.
I'm using inside my network a .local domain which is defined in a ZONE
on my DNS - so no problem ...
Actually, that *IS* a problem. You should not be doing that. That is
quite likely the source of all your problems. That domain name is
reserved for a specific purpose and putting it in DNS will cause
conflicts.
Sorry, you're telling *BULLSHIT*; the TLD .local is exactly reserved for
this purpose ...
_______________________________________________
I'm not familiar with the use or misuse of .local, but I am having a problem
that might be related. I have a surveilance camera, which I am trying to
make work--
a Pyle PIPCAM5. My Linux is PCLinuxOS, but that probably is not germane.
Two
days ago I investigated the camera, which is (at the moment) connected
to the
lan by cat5 cable. Using nmap and one other program I got the responses
that the camera's
name is Android.local and I found the ip address and the MAC address
(which was
supposed to be on the bottom of the camera but wasn't). On that day, I
could ping
the camera by its ip or by its name, and the ping would work. I also
found that it
was made by Murata. Now the problem: yesterday and today it is inaccessible
by any means--ping by ip or name, or by nmap. I have tried connecting
and disconnecting
the lan cable, the power cable, and rebooted the router, but nothing
works. And since
I can't access it, if the name is a problem, there is no way to get to
it and change
the name, even if I knew how! (Oh, I also tried to access it
wirelessly, but that
doesn't work either.) What does TLD mean, anyway?
--doug
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
