Can't create domains

I haven't upgraded to 5.7 yet. Is it possible that something broke in the 5.7 release?

What happens when you submit the form?

If you're not in production, you could try editing domain_admin.inc:

function domain_create_form_submit($form_id, $form_values) {
  print '<pre>';
  print_r($form_values);
  exit;
  db_query("INSERT INTO {domain} (subdomain, sitename, scheme, valid) VALUES ('%s', '%s', '%s', %d)", $form_values['subdomain'], $form_values['sitename'], $form_values['scheme'], $form_values['valid']);
  // Let other modules act.
  $domain = domain_lookup(NULL, $form_values['subdomain']);
  module_invoke_all('domainupdate', 'create', $domain, $form_values);
  // The user_submitted flag is needed for Domain User.
  if (!$form_values['domain_arguments']['user_submitted']) { 
    drupal_set_message(t('Domain record created.'));
    drupal_goto('admin/build/domain/view');
  }  
}

Then report back what it prints out.

That last comment makes no sense to me.

Try putting the debug code inside domain_create_form_validate().

Some additional debugging steps:

-- Do other forms on your site work?
-- Have you configured the root domain?
-- From what domain is the "create domain" form loaded? (It should be the root domain.)
-- Do you have the module's "Search engine optimization" option turned on?
-- When viewing the HTML source on 'admin/build/domain/create', what is the form action?

There is a "treat www.* as an alias of *" setting that should also solve this problem.

I'm not sure that changing the documentation as you suggest is any help here, as this is the first time this issue has come up.

If we changed the text, what would we change it to?

Considering that the primary domain or root domain for www.example.com is example.com, and any web server that is not configured to allow example.com to resolve is misconfigured, I'm really not going to agree with you here.

Look at the RFC for domains. www.* is the exception, not the rule. Or look at cookie handling. http://www.ietf.org/rfc/rfc2109.txt.

   Domain=domain
      Optional.  The Domain attribute specifies the domain for which the
      cookie is valid.  An explicitly specified domain must always start
      with a dot.

It starts with a dot because "example.com" is the root domain, and "*.example.com" is a valid subdomain. Changing the terminology here won't prevent user error.

The form field is already labeled "Primary domain," perhaps something more needs to be added in the README:

----
4.1.1   Primary Domain Name

Enter the primary domain for your site.  Typically, you will also enter this
value into settings.php for cookie handling.  Do not use http:// or a trailing
slash when entering this value.

So I'm looking for a documentation suggestion here. Otherwise, it's a "won't fix."

There may be a documentation issue, because it occurs to me that we changed the behavior at one point during development.

Originally, the module only allowed you to create subdomains. You set a root domain (example.com) and were expected to set the subdomains to be:

-- one.example.com
-- two.example.com

And so on.

However, during the testing process, we changed it to allow any domain to be entered. So "primary domain" is the preferred term. Now you can use:

-- example.com
-- myexample.com
-- one.example.com

You set the "primary domain" to be the fallback in case someone requests a domain that is not registered. This is used in cases where wildcard DNS is used.

So perhaps a documentation change is in order. We should at least make clear that the "Primary domain" must be accessible. But I'm still a little confused about what you set the Primary domain to.

Apparently, you should have set it to www.example.com, and the problem occurred because you set it to example.com, but your web server did not recognize that?

To me, that is a misconfiguration of the web server, and I won't take steps to prevent that error via code.

But I agree that is irrelevant, and will try to make the documentation consistent.

That first one is a legacy issue, addressed in #16 and will be changed.

For the second, however, that language is accurate. When creating user-based domains, only the leftmost domain element can be created. That will be appended to the "root domain." This is a security feature so that users can't go crazy creating domain records.

So, in effect, if you let users create domains on "exampleuser.com" they are created at:

-- user1.exampleuser.com
-- user2.exampleuser.com

and so forth.

So the "root domain" concept is accurate there, I think. Perhaps you just want a longer description? But most people ignore those.

I have added this description for "Primary domain":

The primary domain for your site. Typically example.com or www.example.com. Do not use http or slashes.
This domain will be used as the default URL for your site.
If an invalid domain is requested, users will be sent to the primary domain.

And this to Domain User:

The root domain to use for creating user domains, typically example.com.  No http or slashes.
When users create domains, their username will be added to the root domain to create a custom domain.
For example, user.example.com or administrator.example.com.