I ran `npm uninstall sfdx-cli --global` and then `npm install @salesforce/cli@latest --global` and still get ` @salesforce/cli/1.82.6 darwin-x64 node-v18.17.11 returned when running `sf -v` . 

We are creating several custom objects and related custom fields by deploying the custom object metadata file with './package.xml'. However, the documentation suggests I have to create an additional profile or permission-set metadata file for setting field-level security. Is that necessary, or can I just include the field-level security in the field metadata included in the custom object xml file?

We are configuring 2 Salesforce Marketing Cloud Sender Authentication Packages.

We want to set up subdomains under our top-level domain and point the subdomains to the 4 exacttarget.com name servers, which will be different from the TLD nameservers. We also need to configure each Subdomain with SSLs (4 purchased from salesforce and 6 from a vendor of our choice).

GoDaddy is our TLD registrar, and AWS Lightsail hosts our DNS management.

We Want to set up two subdomains under our TLD for use with our two Marketing Cloud SAPs and 4 subdomains under each of the above. Outline below:

TLD = domain.com

SAP 1:

• sub1.domain.com
  • cloud.sub1.domain.com
  • click.sub1.domain.com
  • view.sub1.domain.com
  • image.sub1.domain.com

SAP 2:

• sub2.domain.com
  • cloud.sub2.domain.com
  • click.sub2.domain.com
  • view.sub2.domain.com
  • image.sub2.domain.com

As mentioned above, We need to point each of the Subdomains above to the following name servers:

• ns1.exacttarget.com
• ns2.exacttarget.com
• ns3.exacttarget.com
• ns4.exacttarget.com

None of the above is possible with our current registrar/DNS setup. If we moved our Registrar from GoDaddy to AWS Route 53 or our DNS management to GoDaddy, could we satisfy the requirements above to start using our SAPs/Marketing Cloud? Is there a different Registrar DNS hosting/management service that would enable us to meet our Requirements?

DOCs below:

• https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm&type=5 (https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm&type=5)
• https://help.salesforce.com/s/articleView?id=sf.mc_es_dns_record_maintenance.htm&type=5 (https://help.salesforce.com/s/articleView?id=sf.mc_es_dns_record_maintenance.htm&type=5)
• https://help.salesforce.com/s/articleView?id=sf.mc_es_subdomain_delegation_guide.htm&type=5 (https://help.salesforce.com/s/articleView?id=sf.mc_es_dns_record_maintenance.htm&type=5)
• https://help.salesforce.com/s/articleView?id=000314909&type=1 (https://help.salesforce.com/s/articleView?id=000314909&type=1)
• https://trailhead.salesforce.com/en/content/learn/modules/email-deliverability-concepts/understand-authentication-and-sap
• https://www.youtube.com/watch?v=YOUfep-KTwk

I ran `npm uninstall sfdx-cli --global` and then `npm install @salesforce/cli@latest --global` and still get ` @salesforce/cli/1.82.6 darwin-x64 node-v18.17.11 returned when running `sf -v` . 

We are creating several custom objects and related custom fields by deploying the custom object metadata file with './package.xml'. However, the documentation suggests I have to create an additional profile or permission-set metadata file for setting field-level security. Is that necessary, or can I just include the field-level security in the field metadata included in the custom object xml file?

We are configuring 2 Salesforce Marketing Cloud Sender Authentication Packages.

We want to set up subdomains under our top-level domain and point the subdomains to the 4 exacttarget.com name servers, which will be different from the TLD nameservers. We also need to configure each Subdomain with SSLs (4 purchased from salesforce and 6 from a vendor of our choice).

GoDaddy is our TLD registrar, and AWS Lightsail hosts our DNS management.

We Want to set up two subdomains under our TLD for use with our two Marketing Cloud SAPs and 4 subdomains under each of the above. Outline below:

TLD = domain.com

SAP 1:

• sub1.domain.com
  • cloud.sub1.domain.com
  • click.sub1.domain.com
  • view.sub1.domain.com
  • image.sub1.domain.com

SAP 2:

• sub2.domain.com
  • cloud.sub2.domain.com
  • click.sub2.domain.com
  • view.sub2.domain.com
  • image.sub2.domain.com

As mentioned above, We need to point each of the Subdomains above to the following name servers:

• ns1.exacttarget.com
• ns2.exacttarget.com
• ns3.exacttarget.com
• ns4.exacttarget.com

None of the above is possible with our current registrar/DNS setup. If we moved our Registrar from GoDaddy to AWS Route 53 or our DNS management to GoDaddy, could we satisfy the requirements above to start using our SAPs/Marketing Cloud? Is there a different Registrar DNS hosting/management service that would enable us to meet our Requirements?

DOCs below:

• https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm&type=5 (https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm&type=5)
• https://help.salesforce.com/s/articleView?id=sf.mc_es_dns_record_maintenance.htm&type=5 (https://help.salesforce.com/s/articleView?id=sf.mc_es_dns_record_maintenance.htm&type=5)
• https://help.salesforce.com/s/articleView?id=sf.mc_es_subdomain_delegation_guide.htm&type=5 (https://help.salesforce.com/s/articleView?id=sf.mc_es_dns_record_maintenance.htm&type=5)
• https://help.salesforce.com/s/articleView?id=000314909&type=1 (https://help.salesforce.com/s/articleView?id=000314909&type=1)
• https://trailhead.salesforce.com/en/content/learn/modules/email-deliverability-concepts/understand-authentication-and-sap
• https://www.youtube.com/watch?v=YOUfep-KTwk