Recently, I created two parent portals for our site, to be accessed as subdomains:
site.com
sub1.site.com
sub2.site.com
 One of them works flawlessly (sub1), I can access the portal, login and edit everything. But the other is inaccesible (sub2), and a "Server no found" error is returned by the browser instantly upon request (not even an IIS or DNN error). Also, the subdomains can not be accesed with the "www" prefix. www.site.com works, www.sub1.site.com doesn't. Last, when trying to edit the portals from the "Portals" page on the Host menu, I get this error:

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.Admin.Portals.SiteSettings.LoadPortal(String activeLanguage) at DotNetNuke.Modules.Admin.Portals.SiteSettings.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace --- 

sub2 has only one alias: sub2.site.com. Clicking on it from the portal settings in the host menu renders the same "not found" error. Trying to edit the portal from the Host menu returns the DNN error.
I wonder if I should add the subdomains as aliases of the 0 portal? Though that would be inconsistent since it is only one subdomain that is giving trouble. Also, I would like to note that I have full access to the DNN installation, IIS and the server in general, in case that helps.

make sure, your IIS web site has a binding for sub2.site.com, i.e. is either serving all requests for the IP address or has an appropriate host header value.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN