www.domain.com works, domain.com doesn't

and to clarify:

https://www.inquarta.com works

but

https://inquarta.com resolves to sign-up.

https://inquarta.com resolves to sign-up.

When this happens, the URL it goes to is this: https://www.inquarta.com/wp-signup.php?new=inquarta.com
So for some reason, it thinks that “inquarta.com” is not part of the domain name, but is what you might want to call a new blog.

In trying to see why that might be, I’ve notice that attempts to ping inquarta.com get replies from premedjumpstart.com.

ping https://www.inquarta.com
PING inquarta.com (70.32.120.180) 56(84) bytes of data.
64 bytes from premedjumpstart.com (70.32.120.180): icmp_seq=1 ttl=49 time=136 ms

Now wondering if you’ve got the inquarta.com domain properly installed on the server? I’m wondering if you’re forwarding it or something?

hi no not forwarding it to anything.

my dedicated server is called ‘premedjumpstart.com’ which is the name that the vendor gives it (media temple).

this is a virtual dedicated server, or ‘dv’ in the media temple language.

Anything else it could be?

thanks!

Also, when wordpress 3.0 was installed, the coder installed the main site as https://www.inquarta.com, not inquarta.com … so this may have inadvertently created a weird thing with the domain inside wp3.

thanks!

You need to add a rewrite rule to your htaccess file to direct all non-www requests to the www domain.

We resolved this!

Here’s what happened:

* the person who installed wordpress 3.0 used “www.inquarta.com” instead of ‘inquarta.com’ as the domain name of the main site. This drove wp3.0 a little nuts.

We fixed this by going straight into the database and changing the sitename. I don’t recommend others doing this (sorry, I don’t know the specific steps the installer took to do this).

So now the site is resolving properly. Wahoo!