has anyone else had problems deploying a single domain for store & checkout? the SSL certificate deployment fails and NS support is actually claiming that because the live DNS doesn't point to NS hosting yet (as the site needs to be tested before driving users to it, obviously), then it's impossible to deploy. I was told I should just use a new/different subdomain - as if there are no such things as search engines or bookmarks. I never had a problem deploying a new domain in NS before the 2020.2 update last year, but have had this problem several times since then. NS refuses to even admit that it's a bug.

I'm having trouble deploying extensions off and on today. Not sure if that's related.

I'm not sure I follow here. You've set up your domain in NetSuite to point to shop.example.com and asked it to deploy an automatic TLS certificate for it. But in your domain's DNS control panel, you haven't pointed the domain to the hosting domain provided by NetSuite (eg shop.example.com.hosting.netsuite.com)? If so, I'm not sure how you expect the certificate to work? I feel like I must be missing something.

The SSL certificate has nothing to do with the settings on the authoritative DNS server. I can generate a SSL certificate using any number of tools just fine, without any DNS settings whatsoever. I can even do it in NS if there is no DNS setting. However, it ONLY fails if there is a DNS setting pointing to another host, which makes zero sense. I obviously need to test the site fully before directing the live domain to the NS hosted site. I can test it using a host file override to mimic the DNS setting for my computer. All of this is SOP for testing & deploying new web sites. Expecting someone to point a live site to the dev site in NS just to be able to START deploying the SSL certificate (and before any testing can be completed) is not reasonable.

I do not understand what you are trying to do. It seems that is not the SuiteCommerce way. What I usually do is to create a staging/testing domain in NetSuite (bought in goDaddy for example, setup the DNS part that Steve mentioned) and associate the SSP (touch points). Then you are able to test your site in an stagin domain. Once done you can move/associate your SSP to your real live domain. Not sure if this helps or if you are trying to avoid this part. Good Luck!

Emerson, thanks for your comments. that is basically what we're trying to do. The problem is that the deployment fails completely, both for a single domain or web store only when it's secure. I'm being told that somehow the DNS settings on Godaddy are preventing NS from generating a SSL certificate or setting up its internal DNS to respond to queries on that domain. I can't imagine anyone thinking it's ok to point the live DNS for an active web store to NetSuite BEFORE deploying the domain, in hopes that things will just work and there won't be too much downtime. All of this used to work fine before the 2020.2 update, and I've filed multiple cases on it without the slightest progress.

What a weird issue, I do not know how the Live site or DNS could be affecting here. Just to clarify, 1. you have your new domain or subdomain, https://mysubdomain.com 2. then you create a domain record 3. Domain Type = Single Domain for Web Store and Checkout | You copy the CNAME and setup in your domain provider 4. You probably use the automatic certificate (or create one manually) 5. Save the record 6. are you having problems with the deployment status on the domain record? or are you having problems when deploying extensions/theme? I have had problems with the deployment status before, I usually use another subdomain (the deployment status using the automatic certificate takes at least 2 hours to be up and running)

My main question is this:   1.     For the dev.domain.com subdomain, I was able to deploy the single domain just fine when there was no DNS record set up. 2.     I am now trying to do the exact same thing for the store.domain.com subdomain, but NS is telling me that because there is a DNS record at Go Daddy that points to a different server, that prevents their internal system from generating a SSL certificate and the deployment fails.   This makes no sense whatsoever, and no other system that generates SSL certificates works this way. DNS has nothing to do with generating SSL certificates. We are not willing to just blindly point a live website that users are hitting every day to NetSuite before we even attempt to deploy the domain on the NetSuite side. Asking us to do this violates every principle of proper web development.

Sorry, I do not know what is going on for your scenario.

@Steve Goldberg - is it the official NetSuite position that it's impossible to deploy a domain or a SSL certificate for any website without first pointing the live DNS to NetSuite first? I have spent weeks going back and forth with support and that seems to be what they are saying, but it's not documented anywhere and I have yet to hear any kind of explanation for it. NO other hosting platform requires that all users & search engines be directed to their hosting BEFORE even deploying the web site.

I am not a spokesperson for NetSuite, so I can't say whether that is or is not our official position on that matter.

it is apparently the official NS position that it's impossible to configure NS hosting for a domain unless the external live DNS is pointing to them FIRST. here's a help video that says exactly that: https://videohub.oracle.com/media/SuiteCommerceA+Secure+Your+Website+Domain/1_z5bn415n There isn't another hosting platform in the world with that requirement. We got to enjoy 4 hours of downtime while we waited for NS to deploy the domain after pointing our live, active site to it. The most ridiculous aspect is if there is NO dns entry at all, you can deploy just fine.