local domain?

English Network/Internet
1

I don’t really have a problem, annoying maybe. I’m running openSUSE 13.1 at the mainserver and it gives domain, NTP, default gateway, DNS etc trow DHCP.

I’m using ****.local on my lan and ****.nu on the outside Wan. openSUSE pc’s, Windows and Android units swallows the setup and working. I receive messages from Ubuntu (12.02LTS&14.04LTS) that “network is disabled .local domain is not supported”. Network is still working.

So… -Is it a bug in openSUSE or Ubuntu? Is it anything special for Ubuntu clients that I have missed?

Regards

2

On 2014-08-04 12:46, jonte1 wrote:

> I’m using ****.local on my lan and ****.nu on the outside Wan. openSUSE
> pc’s, Windows and Android units swallows the setup and working. I
> receive messages from Ubuntu (12.02LTS&14.04LTS) that “network is
> disabled .local domain is not supported”. Network is still working.

And it is probably true, .local domains should not be used with Linux.
There is a bugzilla about that at ubuntu somewhere, so they are more
aware of the issue than openSUSE.

https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/205236
https://bugzilla.novell.com/show_bug.cgi?id=747939

The problem is that .local domain names conflict with avahi/zeroconf
services. It is impossible to join a Windows domain from Linux, if avahi
services are running (and they do by default) and the domain name is
something.local.

> So… -Is it a bug in openSUSE or Ubuntu? Is it anything special for
> Ubuntu clients that I have missed?

The issue is the same in Ubuntu and openSUSE, it is simply that they
tell you about it and openSUSE does not.

You should rename your domain to something else, like *.lnet, plain
simple…

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

3

Interesting, I will give a try later in the week to change the DNS/scope of DHCP. I have search it before

Regards

4

The following you are not running Domain based security (like AD or openLDAP).

You start by changing the machine name configured in the network device configuration. On openSUSE (unlike other distros), this is best done in
YAST > Network Devices > Hotname tab

Once this is done on each and every machine in your network, if you’re not running any special network security (eg Domain based security like openLDAP or Active Directory), everything should now “just work.” If you’re running special network services like SAMBA, you may also have to modify configuration files for those services.

If you are really running Domain-based security like openLDAP or AD, although possible it’s extremely difficult to change a Domain name. Most of the time the recommendation is to just wipe it clean and start over. It takes real <expert> skill to change a Domain name which is why it’s so incredibly important to name your Domain correctly in the first place.

TSU

5

On 2014-08-04 21:06, tsu2 wrote:
>
> jonte1;2657461 Wrote:
>> Interesting, I will give a try later in the week to change the DNS/scope
>> of DHCP. I have search it before

Not DNS, but Windows AD (Active Directory) Domain name. It is used on
Enterprise level Windows setups.

Even if you are not using that, what Ubuntu is telling you is that you
can not use a .local name because there is a conflict between zeroconf
and AD… So it very correctly does not allow you to setup a .local host
name, just in case.

YaST should do the same, and as you can see in that bugzilla I linked,
they intended to that, then they forgot.

> If you are really running Domain-based security like openLDAP or AD,
> although possible it’s extremely difficult to change a Domain name. Most
> of the time the recommendation is to just wipe it clean and start over.
> It takes real <expert> skill to change a Domain name which is why it’s
> so incredibly important to name your Domain correctly in the first
> place.

I have done it… and it is difficult. Often it breaks so badly that you
have to start over. Or you get strange errors.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

6

Hmm. Hmm… :. This is what I like at openSUSE forums, you get a answer pretty fast. Even answer on things you haven’t consider.

-Samba, configured as workgroup only
-DNS zone, configured as ****.local
-DHCP, gives ****.local

And here it comes, -I have played around with LDAP and have certificates installed. But I never had it working 100% to my demands. What I know it isn’t used for any function but I have to do some digging in there before any changes.

Thanks!

Regards

7

That’s the issue.
Many people <think> they might have succeeded in changing the Domain name at a higher level, but there are many low level objects that won’t change and can be addressed only with command lines and knowledge of the objects you have to go after.

So, people will put the work in and think they succeeded only to have things turn squirrelly down the road.
The only way to be successful is to follow specific instructions and be willing to study the LDAP structure far deeper than most people venture.

Workgroup names are no problem, they are all managed simply as standalone settings on each machine, that of course have to be consistently same… Not stored in a complex database and directory structure.

TSU

8

On 2014-08-06 03:16, tsu2 wrote:

>> I have done it… and it is difficult. Often it breaks so badly that you
>> have to start over. Or you get strange errors.

> That’s the issue.
> Many people <think> they might have succeeded in changing the Domain
> name at a higher level, but there are many low level objects that won’t
> change and can be addressed only with command lines and knowledge of the
> objects you have to go after.
>
> So, people will put the work in and think they succeeded only to have
> things turn squirrelly down the road.
> The only way to be successful is to follow specific instructions and be
> willing to study the LDAP structure far deeper than most people venture.

Many Windows Servers admins would not know how to do that (I don’t). You
assume that Windows just handles it for you, that’s what you pay for
when you buy a Windows Server system.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

9

I have done some digging into my environment and I will not try to change my .Local domain. I can see tracks and the use of LDAP/Domain in there. I will do a fresh install on a new 13.2 server(and my other server as well) when released. I wonder where I have pick up the .Local? Has it ever existed in SUSE/openSUSE? About old things, I still use vol1, vol2… for some of my shares. I know where that is coming from:).

Regards

10

On 2014-08-10 13:26, jonte1 wrote:

> I wonder where I have pick up the .Local?
> Has it ever existed in SUSE/openSUSE?

Certainly. It is a typical/default setting in many places. Many
documentations use it.

When I was training with AD, and tried to add Linux machines, then found
out I could not, it took me sometime to find out why it would not work.

It is not nice to find out, after days of working, that you have to redo
it all because Linux machines will not connect because of the domain
name choice. And finding that the documentation doesn’t warn about the
issue is maddening.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

11

A general comment:

I started a discussion of this, a while back, on dslreports:

Domain name for private use

It was a pretty good discussion. I more-or-less thought “.localdomain” won that discussion.

Since then, my ISP (and provided router) has been assigning “attlocal.net” so I just went along with that.

12

On 2014-08-10 17:16, nrickert wrote:
>
> A general comment:
>
> I started a discussion of this, a while back, on dslreports:
>
> ‘Domain name for private use’
> (http://www.dslreports.com/forum/r27338341-Domain-name-for-private-use)

LOL. I like this one:

«I used to maintain an officially registered domain that another company
had used as their internal domain (it was a nice 3 letter .com domain).
Several times a year I had to contact them that once again their
internal (often confidential) email was finding its way to our mailservers.»

> It was a pretty good discussion. I more-or-less thought “.localdomain”
> won that discussion.

I had a problem with some software that thought that name was “too
long”. So I used instead “.lnet”. The suggestion to use “.lan” looks
reasonable. But the suggestion to use "something.example.com does not.

> Since then, my ISP (and provided router) has been assigning
> “attlocal.net” so I just went along with that.

Curious…

The name is registered, but resolves empty. It works…

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

13

Let info coming about this :). Nice link nrickert and I was also LOL on… The post.

.local is used both here and there I have figure out. I wonder why adwahi/zeroconf (yes I know who introduce that, my favorite) and why MS network is confused when a Linux or Apple unit try to connect(good bug report there robin_listas about doc).

Today at a newly installed openSUSE it suggest .site. As above, -how long will it take before anyone start using the prefix in functions and it will create problems again?

Myself? Oh I have >10 suggestion to myself on short names to use for local domain when 13.2 is here and re-installation.

If I trust wikipedia? Not entirely. But even a pig can find a pearl in the mud sometimes. I thing that I pick up the .local from MS Small business server late -90’s.

Regards

14

On 2014-08-12 15:36, jonte1 wrote:
>
> Let info coming about this :). Nice link nrickert and I was also LOL
> on… The post.

More links:


http://en.wikipedia.org/wiki/Tld#Pseudo-domains
http://en.wikipedia.org/wiki/Pseudo-top-level_domain
http://en.wikipedia.org/wiki/.local
http://en.wikipedia.org/wiki/Alternative_DNS_root
http://en.wikipedia.org/wiki/Onion_routing
http://en.wikipedia.org/wiki/I2p
http://en.wikipedia.org/wiki/.home

> .local is used both here and there I have figure out. I wonder why
> adwahi/zeroconf (yes I know who introduce that, my favorite) and why MS
> network is confused when a Linux or Apple unit try to connect(good bug
> report there robin_listas about doc).

The link above explains it.

> Today at a newly installed openSUSE it suggest .site.

Maybe .site is not a bad choice, apparently.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

15

Thanks. As I wrote before I’m learning a lot of new things in this forum. I finished the book of James A. Michener, Space (Bricksize) yesterday. I notice about some week ago that my 7" tablet was showing me a mobil site(there it is again) of the openSUSE forum in my tablet. Maybe I should spend some time(1-2 evenings) devoted to…

Best regards.

16

Why not try? Did some backups yesterday evening. Wake early this morning and started to-

-stopped ldap
-delete CA for *.****.local
-change .local to .int ((Internial, Intranet etc) the best/shortest I could come up with) in ->YaST ->Network Devices->Network Settings->Hostname/DNS tab and the Domain name from ****.local to ****.int in Domain Search

-deleted the old dns-zone with ****.local and create a new with ****.int
-Adjust the DHCP scoop given ****.local with give ****.int instead

Rebooted 3 times during above to look for problems.

It has been up and running for a couple of hours with the new local(.int) domain name. No more problems messages from Ubuntu and win/android/openSUSE clients just working even after reboot on them and new info from DHCP.

But the great advantage seen so fare is a much faster response time in browse the network(int/ext) and very noticeable in Firefox.

Maybe next weekend I will have another look on LDAP if everything still working.

Thanks forum for input and ideas.

regards

17

On 2014-08-16 13:56, jonte1 wrote:
>
> Why not try? Did some backups yesterday evening. Wake early this morning
> and started to-
>
> -stopped ldap
> -delete CA for *****.**.local
> -change .local to .int ((Internial, Intranet etc) the best/shortest
> I could come up with) in ->YaST ->Network Devices->Network
> Settings->Hostname/DNS tab and the Domain name from ****.local to
> ****.int

…int? Nice one… Unfortunately, it is a registered TLD. Look it up
here: https://publicsuffix.org


gov.in
mil.in

// info : http://en.wikipedia.org/wiki/.info
info

// int : http://en.wikipedia.org/wiki/.int
// Confirmed by registry <iana-questions@icann.org> 2008-06-18
int
eu.int

+++····················
From Wikipedia, the free encyclopedia

The domain name int is a sponsored top-level domain (sTLD) in the Domain
Name System of the Internet. Its name is derived from the word
international, characterizing its use for international organizations
and treaty-related purposes.[1] The first use of this domain was by
NATO, which had previously been assigned the top-level domain nato.

According to Internet Assigned Numbers Authority (IANA) policy, based on
RFC 1591, the sTLD int is reserved for international treaty-based
organisations, United Nations agencies, and organisations or entities
having Observer status at the UN.[2]
····················+±

Sample links:

http://en.wikipedia.org/wiki/List_of_organizations_with_.int_domain_names

Probably, all three letter combinations are or will eventually be taken :frowning:

I’m afraid you have to change it again >;-)

(I’d suggest .lnet - local net)

> But the great advantage seen so fare is a much faster response time in
> browse the network(int/ext) and very noticeable in Firefox.

Curious…

> Maybe next weekend I will have another look on LDAP if everything still
> working.
>
> THANKS FORUM FOR INPUT AND IDEAS.
> regards

:-))

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

18

Grrrr >:). And I thought I was checking it up before. Not using the same sources/tools as you apparently. I will try local.“mydomain”.nu instead for a while. I would rather have a short name but I will have some time to think an check it up. Anyway its a not a big deal to change when I have learn not to have LDAP involved.

Have change it and I still have this large improvement in response time when browsing, feels like new HW/ISP connection , -.local was not a hit on my config at my home system.

Thanks :).

regards