This message was deleted.
# azures
sparse-intern-71089
03/17/2021, 8:52 AMThis message was deleted.
w
worried-knife-31967
03/17/2021, 8:56 AMIf you havent obfuscated that domain name, it's likely doing some checking on the tld as it isn't valid.
I'd check that it's cnamed properly too. Azure normally checks the routing before it will allow you to add custom domains.
m
magnificent-television-29869
03/17/2021, 9:13 AMthe domain name is obfuscated
magnificent-television-29869
03/17/2021, 9:13 AMbut I figured out the actual problem, The CustomDomainName is quite misleading, but apparently that cannot be a domain, just a name
t
tall-librarian-49374
03/17/2021, 10:10 AMAren’t you able to leave out this property and let it auto-generate?
m
magnificent-television-29869
03/17/2021, 10:15 AMit said it was required
t
tall-librarian-49374
03/17/2021, 10:29 AMHmm, it’s not in the latest version, according to https://github.com/pulumi/pulumi-azure-native/blob/master/sdk/dotnet/Cdn/CustomDomain.cs#L152
m
magnificent-television-29869
03/17/2021, 10:29 AMbut Pulumi actually errored out saying it was missing
t
tall-librarian-49374
03/17/2021, 10:30 AMOh, odd, that doesn’t sound right
m
magnificent-television-29869
03/17/2021, 10:31 AMno, but thats what I got.
magnificent-television-29869
03/17/2021, 10:33 AManyways it seems like CustomDomain does not support ssl, but ADFCustomDomain does
3 Views