1. Remove the text on the Create a website tab that says “ignore” really can just delete whole line
2. Database records for SSL need to be deleted from database when switching from Static to Dynamic (If you make a cert request, switch and switch again it shows the prior request. It should be defaulted again)
3. Instant alias should ignore global dns rules
External IP address bound to SSL binding, now internal dedicated IP
SSL Tab only to show website name and domain
default choice to include global dns zone during site creation is unchecked
When switching SSL enabled site to shared, certificate to be deleted
When deleted SSL enabled site, certificate to be deleted
Switch IP Mode added to the hosting plan
Ensure the server component for IIS global dns definitions contain at least the
following:
An "A" record with name "[host_name]" and IP Addres "[ip]"
This is regardless if DNS is implemented.
Ensure also the IIS server component configuration contains the Public Shared
IP address, this will be the "external" ip as to be configured in the dns
records
Note: * records as part of the global dns records are not taken care of so they
will need to changed manually. Main reason is that they are not bound to a
website as such and for DNS purposes only.
This change has impacted quite some areas, any testing is welcome
When creating a new website the GlobalDNSRecord configuration defines the
hostheaders/websitepointer to be created
Various forms updated where the hostname field is set to www
GlobalDNSRecord allows empty recordData field
To create related dns records when creating a hostheader/website pointer with
the specification of a hostname a 'A' or 'CNAME' globalDNSRecord definition
of '[host_name]' is required to create the the dns record.
This change addresses a couple of situations:
a) where sites had to be created with a freely chosen hostnames, which was
not possible
b) we needed a single repository with that would accommodated websites but
also sharepoint and tenant specific OWA sites, which was not possible
c) The concept of Domain Pointers was ok but appeared hard to understand
for the end users and added some complexity/additional steps when adding a new
site
The domain pointer approach is updated :
A) decoupled the “sites” from domain
B) Created a new “Domains” Domain Pointer record for each new site created,
to keep on track of the various sites created through the platform
C) Upon removal of the site the Pointer gets removed as well
D) For websites a freely chosen hostname can be taken, similar to
sharepoint (which is or generated or chosen by the tenant)
E) Removed the pointer displaying/listing from the UI, and show only the
top-level and subdomains.
This changeset contains fixed on the verification if a website or hostheade
(domain pointer) already exists
Fix on if no server component dns record (globaldnsrecord) is defined.
In order to use user selectable hostnames icw dns provisioning use the variable
[host_name] as hostname in the dns definitions. The variable will be replaced
