Closed jasenf closed 2 years ago
@jasenf can you give the commands you are using (removing DNS & Subscription information) to add the wildcard name?
Also, have you added a subdomain of the wildcard to another Front Door or Azure CDN?
there are no commands documented. that's my point. wildcard support for frontdoor was announced but i can't find any CLI commands to set it up either in FrontDoor, or the subsequent AzureDns entries.
take care,jasen
On Mon, Mar 30, 2020 11:00 PM, TravisCragg-MSFT notifications@github.com wrote:
@jasenf can you give the commands you are using (removing DNS & Subscription information) to add the wildcard name?
Also, have you added a subdomain of the wildcard to another Front Door or Azure CDN?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
I just assumed there would be a how-to guide or some basic documentation on the CLI. I don't usually see MS release something with no documentation behind it.
@jasenf You can use az network front-door frontend-endpoint to add the DNS entry. If this is blocking you from moving forward, your best bet is to create a support request. If you do not have a support plan, please let me know.
For additional documentation on the proper CLI commands, I am assigning this issue to the document author to evaluate and update as appropriate.
Thanks Travis -- I hacked around the CLI for a few hours today and feel like I got close, but simply could not get it to work.
The problems in documentation are:
1) it is not documented on how to bind an alias resource that is wildcard domain to a front door instance
2) how to set up a front door front endpoint as a wildcard endpoint
3) how to tie a certificate within the key vault to that frontend point.
I seemingly got all three to work via the CLI with no errors being throw (just through trial and error) but the front door end point would not active or deliver the proper certificate or allow http only access. i've tried MS support and am getting nowhere. the last response was trying to tell me how to set up an apex domain as if they aren't even aware of this problem.
I would not mind being someone's guinea pig in getting this set up if that's at all possible.
Hi @jasenf, the reason why there was no documentation for using wildcard domains specifically is because wildcard domains can be managed like normal custom domains in Front Door. In retrospect, this should have been stated explicitly in the documentation that was launched for clarity.
If you really don't mind being someone's guinea pig in getting this set up, so that fewer people have to go through trial and error, I would be happy to put you in touch with someone working on improving Front Door documentation.
Hi Jessica, I have set it up a few times via the CLI now, and the interface does now support it (even though it didn't) My issue was with the lack of documentation while we waited for the portal to support it. happy to help otherwise if I can.
If I try to "Add a record" > "*" > type CNAME or A using Alias Record Set, pointing to a Front Door, it won't let me. As shown in the image below
If I use the CLI, it works. Here's an example:
front_door_id=$(az network front-door show --name "frontdoorname" --query id -o tsv --resource-group my-rg)
az network dns record-set cname create --name "*" --zone-name yourdns.com --target-resource $front_door_id --resource-group my-rg
Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close
Further to the point of there being no documentation, how do we bind the wildcard domain to FrontDoor within AzureDNS? We still get the error message "Wildcards () in the name '' are not supported for Front Door and Azure CDN resources due to apex domain onboarding." So even if there command line parameters for setting up FrontDoor, I don't see how we will be able to bind the domain name to it.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.