[Erledigt] Bug oder Feature? Subdomainhosting nicht möglich wenn Zahl im Domainnamen.

[FISA4]

Ich habe gerade das aktuelle Nightly installiert.
Im Anschluss wollte ich "home.domain.tld" als User anlegen.
Es erfolgt eine Fehlermeldung:

Wrong Second Level Domain syntax!

Im Nightly vom 21.10. funktionierte das noch.

Somit ist jetzt das Hosten von Subdomains mit eigenem Login nicht mehr möglich.

Kann mir jemand erklären warum das geändert wurde ???

Gruß

FISA4

[Nuxwin]

(11-29-2009 12:18 AM)FISA4 Wrote:  Ich habe gerade das aktuelle Nightly installiert.
Im Anschluss wollte ich "home.domain.tld" als User anlegen.
Es erfolgt eine Fehlermeldung:

Wrong Second Level Domain syntax!

Im Nightly vom 21.10. funktionierte das noch.

Somit ist jetzt das Hosten von Subdomains mit eigenem Login nicht mehr möglich.

Kann mir jemand erklären warum das geändert wurde ???

Gruß

FISA4

Hi ;


Yes, the validation of the domain name has become more strict (implementing RFC). Now, the system checks the syntax of each label, it can be different depending on whether tld, sld ...

home.domain.tld is not a domain and should not normally be used as such.
But do not worry, a parameter will be added to allow the administrator to disable this behavior.
The second-level domain must follow a syntax similar to tld. Regarding the tld, it must correspond to those listed here http://www.iana.org/domains/root/db/

Moreover, the message you get is the "Wrong Top Level Domain: tld" , not "Wrong Second Level Domain syntax!"

But do not worry, a parameter will be added to allow the administrator to disable this behavior.

[Lucan]

Sorry, but this feature realy sucks.

[FISA4]

(11-29-2009 12:31 AM)nuxwin Wrote:  Hi ;


Yes, the validation of the domain name has become more strict (implementing rfc). Now, the system checks the syntax of each label, it can be different depending on whether tld, sld ...

home.domain.tld is not a domain and should not normally be used as such.

The second-level domain must follow a syntax similar to tld. Regarding the tld, it must correspond to those listed here http://www.iana.org/domains/root/db/

Any ispCP Users have a free hosting service.
By the "strict to rfc" way, they can´t use ispCP 1.0.3.
I think, this is not good.

It would be nice if the admin has the right to switch off the "strict to rfc".

Greets

FISA4

[Nuxwin]

(11-29-2009 12:36 AM)Lucan Wrote:  Sorry, but this feature realy sucks.

Because we want to offer a standards-compliant implementation? So if I understand it, to please you, you need the code well rotted. I take note.

[Lucan]

In my opinion it doesn't help anybody.

It does the opposit it limit's the admin about the things he is able to with his server.
I don't think that you or the other dev's should decide if a admin is able to use a subdomain as a user or not.

And as FISA said, also a lot of free hosters are using ispcp, what do they do now? taking a other panel? never update again? patch all files manually back after an update?


For me personally, i always create the User customerxy.s01.mydomain.com and add the domain he likes to as an alias.
If you ask your self why, its quite easy.

the url customerxy.s01.mydomain.com will exist "for ever" but customers often don't use theiere domain after a year or so.
So i just can delete the alias and add the new ordered domain, whithout any trouble.

But now, that won't be possible anymore.

Also when i want to test something, i create a new user with sub.domain.com - which won't be able anymore too.


So please, don't just make such important descisions without asking the community. It's not fair in my opinion.


just my 2 cents

[Nuxwin]

(11-29-2009 12:48 AM)FISA4 Wrote:  Any ispCP Users have a free hosting service.
By the "strict to rfc" way, they can´t use ispCP 1.0.3.
I think, this is not good.

It would be nice if the admin has the right to switch off the "strict to rfc".

Greets

FISA4

Sure, I repeat --> But do not worry, a parameter will be added to allow the administrator to disable this behavior.

[FISA4]

(11-29-2009 12:58 AM)nuxwin Wrote:  Sure, I repeat --> But do not worry, a parameter will be added to allow the administrator to disable this behavior.

OK, this sounds good for me.

[Nuxwin]

(11-29-2009 12:58 AM)Lucan Wrote:  bla bla bla

When I need to wipe me, I'll call you !

I do not discuss more because obviously you do not read the response until the end.

[sPiKe]

also ich fänds überhaupt nich gut, wenn man keine subdomains mehr als kunden anlegen könnte, da ich ja freehoster bin und meinen kunden eine subdomain biete. ich kann denen ja keine tld domain auch noch kostenlos anbieten?
also wie ich es mitbekommen hab, soll man diese option dann auch deaktivieren können, das wäre dann ok.
aber bitte nicht standardmäßig das ausbauen, dass man keine subdomains mehr anlegen kann