On 11/08/2011 08:20 PM, lynn wrote:
On 11/08/2011 07:16 PM, Brian K. White wrote:
On 11/7/2011 5:11 PM, lynn wrote:
On 11/07/2011 09:36 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2011-11-07 at 15:15 +0100, lynn wrote:
I realised that the name of my Linux box was hh1.com ... Do you know that both domains exist in internet? Is that intentional? Not intentional. I think all domains that are of the form xyz.com will be snapped up in internet. Mine is only a 192.168 lan address.
Saludos L x
He means was it intentional that you used an *.com domain on a lan.
When you do that, the ambiguity that results is your fault, not the fault of whoever out there has those domains on the public net.
Ambiguity = problems. Unnecessary ambiguity = unnecessary problems.
Don't use <short-string>.com .org .net etc domains on lans unless you need to and are prepared to deal with the complications of getting that to do what you think you want it to do.
Even when you actually own the name, it's still a complication although at least then it's possible to address (no pun).
Yes. I think I understand. Changing the domain name sounds like the way to go. L x
Well, I unjoined the windows boxes from the domain, changed the server name to xxx.site, changed the LDAP dc to dc=site, turned off bind and rejoined the windows 7 boxes to the domain. Amazingly they are working without my internal DNS running. Your ambiguity argument has a lot in its favour. I just wish I knew enough to explain all this. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org