Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

About

News Press Releases News Coverage Press KitCareersContact DNN

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Dreaded "Domain Name Does Not Exist In The Database" errorDreaded "Domain Name Does Not Exist In The Database" error
Previous
 
Next
New Post
6/22/2012 3:08 PM
 
Mark Eckeard


Joined: 1/19/2004
Posts: 924

This is the error I hate the most.

Anyhow, I have a 6.2 Pro install as localhost/dnn62.  It works fine but I need someone else within the company to see it from a remote location and machinename/dnn62 doesn't work.  I assume it's due to the missing record in the portalalias table.

Adding a portal and portalalias record doesn't seem to resolve the issue.  I even tried the suggestion within the error to list all portal alias' in a comma seperated list:

Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list.

Example:

URL: http://localhost/DotNetNuke/default.aspx
URL: http://MACHINENAME/DotNetNuke/default.aspx
URL: http://209.32.134.65/DotNetNuke/default.aspx
PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke

That didn't work.

What can I do to add an alias record to get this to work?

Thanks,

Mark
 
New Post
6/22/2012 6:05 PM
 
Gary Miller


Joined: 5/6/2003
Posts: 36
Mark, why are you not simply adding a portal alias thru the Portals page of the admin menu?If internally localhost/dnn62 works as you suggest then I add each of these to the alias list.1) external static_IP2) internal static_IP/dnn62 (assuming not in a dmz)3) full domain_nameThis seems to work from anywhere. Although some firewalls will not let you reach from inside to the domain_name back in thru the firewall using the resolved external IP. In that case I set up an internal DNS pointer to the inside lan ip of the server.Gary
 
New Post
6/25/2012 1:09 PM
 
Mark Eckeard


Joined: 1/19/2004
Posts: 924
Gary,

I wasn't aware I could do it via the admin menu. Normally the response to this is to manually enter the records via SSMS and that's what I was trying to do.

Thanks for the tip. That seemed to work perfectly!

Regards,
Mark
 
New Post
9/1/2012 8:40 PM
 
Michael Durthaler


Joined: 9/18/2006
Posts: 308

Gary,

 I'm not even getting to the site.  Here's what I've done: I had a development 6.2 site setup with a dedicated IP so we could dial it up over the wire. It's address is http://209.213.120.46 and it works.

OK, now for the production site.  I copied the root folder, renamed it for Production.  Went of course to the Website folder to set up the web.config to point to the production database.  The production database is a copy of the dev db.

The production site needs a certificate on it, which it has now.  I've edited the portal alias tables, etc.  Same procedure that was done for the http:// version (dev) of the site.

Well, with IIS set up for the certificate, the portal alias table edited, etc., I can't get around this error.  I'm missing what it is.

What do you need from me to assist resolving this? 

Thanks!
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Dreaded "Domain Name Does Not Exist In The Database" errorDreaded "Domain Name Does Not Exist In The Database" error


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out