Feature Requests
Share ideas, discuss and vote on requests from other users in community
 

Force Lowercase Domains at registration.

Anonymous shared this idea 6 years ago
Declined

Some customers use uper-case words on domains, like "MyDomainNameCompany.net". It would be great if whmcs could transfer them into lower-case after the domain order or in the order form, so we don't have to manually correct into admin area and invoices.

Original Forum Request:

http://forums.whmcs.com/showthread.php?63278-Accept-only-lower-case-domains

Best Answer
photo

We already do convert to lowercase when IDN domains are not involved.

However, the statement, "so we don't have to manually correct into admin area and invoices." confuses me - can someone please elaborate as to why you need to change the casing to lower case post order?

Comments (15)

photo
1

>>"because domains all are lowercase "

> Forcing the lowercase of domains itself would violate RFC 1035: https://tools.ietf.org/html/rfc1035

Much of 1035 has largely been replaced/obsoleted in implementation over the last 20-ish years with the open-resolver projects, the introductions of new gtlds 10 years ago, IDN's (idns must be in lowercase when sent to the registry) and so forth.

Which is moot as WHMCS itself doesnt put anything in dns zones anyway :p

>"because not all whois implentations can cope with mixed case"

You introduce problems when the details in whoisservers.php returns that SomeWierdDomain.blah is 'not found' (and therefroe assumes it can be registered) when somewierddomain.blah already exists and then the registrar rejects the registration, and the client rings up wanting to know how the domai they wanted has been 'stolen' when it's been registered since 1994.

Some implementations of 'standard' internet tools wont accept mixed case (although many try to 'fix' your mistypes for you)

>>"because some registries wont accept them

>"Passing the domain registered from the end user to the registry can be passed in lowercase to ensure they accept.

Solving the 'garbage in' means less solving of 'garbage out' ;)

>>"because its a nightmare to find something when they're all mixed

>"The casing of the domain shouldn't matter here as we can easily ensure the search areas ignore casing.

Not everything uses your front-end search facilities - custom modules, custom reports, interfaces to external systems, other systems that read/write to the whmcs db are just a few examples.

If you try to go to http://www.IbM.com your browser will go into the subroutine 'UserIsAnIdiot(tm)' and correctly change it to lookup http://www.ibm.com (which is what it then adds to it's db/cache)

Why give the WHMCS admins the support issue, and end-users various problems with things not working as expected when you can just have a switch in WHMCS setup for 'force domains to lowercase' and it's just 'fixed' ?

photo
1

Rob,

Absolutely valid points - do you have any reference material where this RFC is deprecated in lieu of more up-to-date regulations?

photo
1

Rob Golding wrote

> because domains all are lowercase

No, all domains are case-insensitive.

> because some registries wont accept them

Which?

> because not all whois implentations can cope with mixed case

Which?

> beause its a nightmare to find something when they're all mixed

How?

> Solving the 'garbage in' means less solving of 'garbage out' ;)

PEBKAC.

> Not everything uses your front-end search facilities - custom modules, custom reports, interfaces to external systems, other systems that read/write to the whmcs db are just a few examples.

Well, then these custom modules etc. obviously need a bug-fix.

So instead of demanding a deliberate RFC violation from WHMCS, you probably should pester those who write tools which do not cope with the industry standard.