<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Setting up subdomain hosted at Route53 for Email Sending + Primary Marketing Email domain in Blog, Website &amp; Page Publishing</title>
    <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905685#M10705</link>
    <description>&lt;P&gt;One note to consider here&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/617470"&gt;@sip49&lt;/a&gt;&amp;nbsp;- if you're setting up an &lt;EM&gt;email sending domain&lt;/EM&gt;, you don't need a subdomain as you've described.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A subdomain will be how you host landing pages built in HubSpot, a blog if you'd like, an online versions of your emails (like a newsletter archive). But you email sending domain, which Google and Yahoo are geting strict on now, is different: &lt;A href="https://knowledge.hubspot.com/domains-and-urls/connect-your-email-sending-domain" target="_blank" rel="noopener"&gt;Connect your email sending domain&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 15 Jan 2024 15:58:37 GMT</pubDate>
    <dc:creator>danmoyle</dc:creator>
    <dc:date>2024-01-15T15:58:37Z</dc:date>
    <item>
      <title>Setting up subdomain hosted at Route53 for Email Sending + Primary Marketing Email domain</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905020#M10695</link>
      <description>&lt;P&gt;I can't figure out what I'm doing wrong here, but I'm trying to setup a subdomain (hello.company.com) as my domain for everything in Hubspot (Marketing Professional plan).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am able to follow the instructions for setting up a subdomain, so it gets me to the stage to enter a cname record for hello.company.com. However, my DNS provider (AWS Route53) doesn't like it. It keeps giving me the following error:&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;"Bad request.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;(InvalidChangeBatch 400: RRSet of type CNAME with DNS name hello.company.com. is not permitted at apex in zone hello.company.com.)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;When I google online people say it's against DNS rules to have a CNAME record where you have any other records as well (e.g. we have MX records so we can receive email there). How do folks get this to work? Sounds like a pretty standard use case.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;They do offer A names but it says you can only use those for a primary domain and not a subdomain. What other alternatives are there?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Sat, 13 Jan 2024 05:34:50 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905020#M10695</guid>
      <dc:creator>sip49</dc:creator>
      <dc:date>2024-01-13T05:34:50Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up subdomain hosted at Route53 for Email Sending + Primary Marketing Email domain</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905511#M10701</link>
      <description>&lt;P&gt;Hi &lt;SPAN&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/617470"&gt;@sip49&lt;/a&gt;&lt;/SPAN&gt;,&lt;BR /&gt;&lt;BR /&gt;Thank you for reaching out to the Community!&lt;BR /&gt;&lt;BR /&gt;First, I'd like to share this article that might be of interest "&lt;A href="https://knowledge.hubspot.com/email/troubleshoot-your-email-sending-domain" target="_blank" rel="noopener"&gt;Troubleshoot your domain connection&lt;/A&gt;".&lt;BR /&gt;I also wanted to refer you to this &lt;A href="https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Having-issues-connecting-your-domain-to-HubSpot/m-p/402647" target="_blank" rel="noopener"&gt;related thread&lt;/A&gt; with helpful troubleshooting steps for connecting your domain.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I also would like to ask some of our Community Members and our Top Experts on this subject:&lt;BR /&gt;&lt;BR /&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/149825"&gt;@rlopez&lt;/a&gt;,&amp;nbsp;&lt;SPAN&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/133"&gt;@stefen&lt;/a&gt;&lt;/SPAN&gt;, &lt;SPAN&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/668953"&gt;@IAmerigo&lt;/a&gt;&lt;/SPAN&gt;, &lt;SPAN&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/155074"&gt;@itsme_mariog&lt;/a&gt;&lt;/SPAN&gt;, &lt;SPAN&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/123775"&gt;@danmoyle&lt;/a&gt;&lt;/SPAN&gt;, &lt;SPAN&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/93098"&gt;@JenBergren&lt;/a&gt;&lt;/SPAN&gt; and &lt;SPAN&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/154936"&gt;@BukunmiOdetayo&lt;/a&gt;&lt;/SPAN&gt; &amp;nbsp;do you have tips to help &lt;SPAN&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/617470"&gt;@sip49&lt;/a&gt;&lt;/SPAN&gt;, please?&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Also, if anybody else has anything to add and/or share, please feel free to join in the conversation &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks a lot&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":red_heart:"&gt;❤️&lt;/span&gt; and have a lovely day!&lt;BR /&gt;&lt;BR /&gt;Best,&lt;BR /&gt;Bérangère&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jan 2024 11:23:46 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905511#M10701</guid>
      <dc:creator>BérangèreL</dc:creator>
      <dc:date>2024-01-15T11:23:46Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up subdomain hosted at Route53 for Email Sending + Primary Marketing Email domain</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905512#M10702</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/617470"&gt;@sip49&lt;/a&gt;&amp;nbsp;this seems to be an AWS specific issue from what I can see, I have seen this setup multiple times in the past.&amp;nbsp;&lt;BR /&gt;Have you contacted amazon/route53 specifically regarding their suggestions for this? If it can't be set up there there's not really anything HubSpot could do to override this.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only workaround really would be to use a different domain name to point to HubSpot. For example you could have "hello." as your MX record and "info." as your HS record, or whatever you would like to call it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jan 2024 11:26:08 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905512#M10702</guid>
      <dc:creator>TomM2</dc:creator>
      <dc:date>2024-01-15T11:26:08Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up subdomain hosted at Route53 for Email Sending + Primary Marketing Email domain</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905685#M10705</link>
      <description>&lt;P&gt;One note to consider here&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/617470"&gt;@sip49&lt;/a&gt;&amp;nbsp;- if you're setting up an &lt;EM&gt;email sending domain&lt;/EM&gt;, you don't need a subdomain as you've described.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A subdomain will be how you host landing pages built in HubSpot, a blog if you'd like, an online versions of your emails (like a newsletter archive). But you email sending domain, which Google and Yahoo are geting strict on now, is different: &lt;A href="https://knowledge.hubspot.com/domains-and-urls/connect-your-email-sending-domain" target="_blank" rel="noopener"&gt;Connect your email sending domain&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jan 2024 15:58:37 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/905685#M10705</guid>
      <dc:creator>danmoyle</dc:creator>
      <dc:date>2024-01-15T15:58:37Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up subdomain hosted at Route53 for Email Sending + Primary Marketing Email domain</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/934623#M11553</link>
      <description>&lt;P&gt;Appreciate the response! Yeah, I have reached out to AWS. Although it is an issue if you use their Route53, AWS have called out (and backed up with references) that they have implemented DNS according to the global specs and other DNS providers are breaking the spec to make this work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideally Hubspot should allow A name records for subdomains as well, but for whatever reason they only allow those for primary domains (likely, exactly to cover the case above) but they don't even provide an A name record option if you put in a subdomain. &lt;span class="lia-unicode-emoji" title=":confused_face:"&gt;😕&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ended up just using a different name for my subdomain for these hubspot html email pages.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2024 16:01:47 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/934623#M11553</guid>
      <dc:creator>sip49</dc:creator>
      <dc:date>2024-02-28T16:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up subdomain hosted at Route53 for Email Sending + Primary Marketing Email domain</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/936133#M11604</link>
      <description>&lt;P&gt;Thanks for following up&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/617470"&gt;@sip49&lt;/a&gt;&amp;nbsp; really good to learn more. I actually didn't even know HubSpot didn't allow a records for subdomains tbh! HubSpot allowing A records at all is a pretty new thing.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Out of curiosity, why is it a CNAME doesn't suit for your subdomain? I would have thought a CNAME was a better, more reliable solution than an a record to be honest. Even at that, you could set up a reverse proxy or something similar to push an IP to a cname.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2024 16:14:05 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/936133#M11604</guid>
      <dc:creator>TomM2</dc:creator>
      <dc:date>2024-03-01T16:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up subdomain hosted at Route53 for Email Sending + Primary Marketing Email domain</title>
      <link>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/938357#M11641</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/141"&gt;@TomM2&lt;/a&gt;&amp;nbsp;The issue is really what DNS specifications (and therefore AWS Route 53) allow you to configure (see: &lt;A href="https://totaluptime.com/kb/cname-and-mx-for-the-same-host-name" target="_blank" rel="noopener"&gt;https://totaluptime.com/kb/cname-and-mx-for-the-same-host-name&lt;/A&gt;). Basically the DNS specifications (and the way AWS implemented it, which doesn't seem to be consistent for other DNS providers) is that if you have other records on a sub-domain (e.g. MX records to receive email like us), then you CAN'T also have a cname record. You can EITHER have a cname or MX records, so that was our issue. We want to receive/send email from mail.domain.com but ALSO use mail.domain.com as the hubspot domain for hosted emails/links/etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If hubspot provided the option to use A records (like they do for primary domains) or a CNAME then it'd be a non-issue, but for whatever reason for sub-domains specifically they only present a CNAME DNS record option. I suspect the reason they automatically offer an A record for primary domains, is exactly this reason in that primary domains are almost certainly used for other things beyond just hubspot hosting.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 01:48:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Setting-up-subdomain-hosted-at-Route53-for-Email-Sending-Primary/m-p/938357#M11641</guid>
      <dc:creator>sip49</dc:creator>
      <dc:date>2024-03-06T01:48:43Z</dc:date>
    </item>
  </channel>
</rss>

