How to point DNS at a dynamic IP address?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















Bluehost is my DNS provider and my app is hosted on heroku. I'm trying to point the DNS at my heroku app but there's an issue. Heroku's documentation states the following:




Some DNS providers will only offer A records for root domains. Unfortunately, A records will not suffice for pointing your root domains to Heroku because they require a static IP. These records have serious availability implications when used in environments such as on-premise data-centers, cloud infrastructure services, and platforms like Heroku. Since Heroku uses dynamic IP addresses, it’s necessary to use a CNAME-like record (often referred to as ALIAS or ANAME records) so that you can point your root domain to another domain. See examples below.




They go on to recommend creating a CNAME record with the values @ and your root domain alias, e.g. hidden-sierra-7936.herokudns.com.



But Bluehost won't allow this because they want an IPv4 IP Address only and won't accept something like hidden-sierra-7936.herokudns.com as a valid CNAME record. I've already done the www record and things aren't working, so I'm guessing I need the ANAME record as well.



enter image description here



Is there any way around this other than switching to a new DNS provider?










share|improve this question

























  • Are you sure that they want an IP for a CNAME record? CNAMEs can only be pointed to hostnames, not to IP addresses. Same should go for ANAME/ALIAS records. Can you show us the error?

    – Lanexbg
    Nov 17 '18 at 5:11











  • Added an image. Not sure how helpful it'd be. I have a feeling there's no solution here other than switching DNS provider.

    – temporary_user_name
    Nov 17 '18 at 5:20













  • Okay, so it doesn't specifically says it needs an IP, so the problem is in the Host, because there can be a CNAME record for the root domain (@). Try with ALIAS/ANAME to the herokuapp or web forwarding to the www subdomain (which as you said already has a CNAME record)

    – Lanexbg
    Nov 17 '18 at 5:56






  • 1





    I don't mean A record. If you do not see ANAME, ALIAS or some web forward / redirect records in that drop-down with the types you better contact Bluehost for a solution.

    – Lanexbg
    Nov 17 '18 at 7:01






  • 1





    Ha, yes, indeed, sorry :). Anyway, there is nothing much to add: if you want to have the ability to add CNAME/ALIAS to root domain, you have to use DNS provider that supports it.

    – Dusan Bajic
    Nov 17 '18 at 9:10


















0















Bluehost is my DNS provider and my app is hosted on heroku. I'm trying to point the DNS at my heroku app but there's an issue. Heroku's documentation states the following:




Some DNS providers will only offer A records for root domains. Unfortunately, A records will not suffice for pointing your root domains to Heroku because they require a static IP. These records have serious availability implications when used in environments such as on-premise data-centers, cloud infrastructure services, and platforms like Heroku. Since Heroku uses dynamic IP addresses, it’s necessary to use a CNAME-like record (often referred to as ALIAS or ANAME records) so that you can point your root domain to another domain. See examples below.




They go on to recommend creating a CNAME record with the values @ and your root domain alias, e.g. hidden-sierra-7936.herokudns.com.



But Bluehost won't allow this because they want an IPv4 IP Address only and won't accept something like hidden-sierra-7936.herokudns.com as a valid CNAME record. I've already done the www record and things aren't working, so I'm guessing I need the ANAME record as well.



enter image description here



Is there any way around this other than switching to a new DNS provider?










share|improve this question

























  • Are you sure that they want an IP for a CNAME record? CNAMEs can only be pointed to hostnames, not to IP addresses. Same should go for ANAME/ALIAS records. Can you show us the error?

    – Lanexbg
    Nov 17 '18 at 5:11











  • Added an image. Not sure how helpful it'd be. I have a feeling there's no solution here other than switching DNS provider.

    – temporary_user_name
    Nov 17 '18 at 5:20













  • Okay, so it doesn't specifically says it needs an IP, so the problem is in the Host, because there can be a CNAME record for the root domain (@). Try with ALIAS/ANAME to the herokuapp or web forwarding to the www subdomain (which as you said already has a CNAME record)

    – Lanexbg
    Nov 17 '18 at 5:56






  • 1





    I don't mean A record. If you do not see ANAME, ALIAS or some web forward / redirect records in that drop-down with the types you better contact Bluehost for a solution.

    – Lanexbg
    Nov 17 '18 at 7:01






  • 1





    Ha, yes, indeed, sorry :). Anyway, there is nothing much to add: if you want to have the ability to add CNAME/ALIAS to root domain, you have to use DNS provider that supports it.

    – Dusan Bajic
    Nov 17 '18 at 9:10














0












0








0








Bluehost is my DNS provider and my app is hosted on heroku. I'm trying to point the DNS at my heroku app but there's an issue. Heroku's documentation states the following:




Some DNS providers will only offer A records for root domains. Unfortunately, A records will not suffice for pointing your root domains to Heroku because they require a static IP. These records have serious availability implications when used in environments such as on-premise data-centers, cloud infrastructure services, and platforms like Heroku. Since Heroku uses dynamic IP addresses, it’s necessary to use a CNAME-like record (often referred to as ALIAS or ANAME records) so that you can point your root domain to another domain. See examples below.




They go on to recommend creating a CNAME record with the values @ and your root domain alias, e.g. hidden-sierra-7936.herokudns.com.



But Bluehost won't allow this because they want an IPv4 IP Address only and won't accept something like hidden-sierra-7936.herokudns.com as a valid CNAME record. I've already done the www record and things aren't working, so I'm guessing I need the ANAME record as well.



enter image description here



Is there any way around this other than switching to a new DNS provider?










share|improve this question
















Bluehost is my DNS provider and my app is hosted on heroku. I'm trying to point the DNS at my heroku app but there's an issue. Heroku's documentation states the following:




Some DNS providers will only offer A records for root domains. Unfortunately, A records will not suffice for pointing your root domains to Heroku because they require a static IP. These records have serious availability implications when used in environments such as on-premise data-centers, cloud infrastructure services, and platforms like Heroku. Since Heroku uses dynamic IP addresses, it’s necessary to use a CNAME-like record (often referred to as ALIAS or ANAME records) so that you can point your root domain to another domain. See examples below.




They go on to recommend creating a CNAME record with the values @ and your root domain alias, e.g. hidden-sierra-7936.herokudns.com.



But Bluehost won't allow this because they want an IPv4 IP Address only and won't accept something like hidden-sierra-7936.herokudns.com as a valid CNAME record. I've already done the www record and things aren't working, so I'm guessing I need the ANAME record as well.



enter image description here



Is there any way around this other than switching to a new DNS provider?







dns






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 17 '18 at 5:20







temporary_user_name

















asked Nov 17 '18 at 5:00









temporary_user_nametemporary_user_name

17.2k3099165




17.2k3099165













  • Are you sure that they want an IP for a CNAME record? CNAMEs can only be pointed to hostnames, not to IP addresses. Same should go for ANAME/ALIAS records. Can you show us the error?

    – Lanexbg
    Nov 17 '18 at 5:11











  • Added an image. Not sure how helpful it'd be. I have a feeling there's no solution here other than switching DNS provider.

    – temporary_user_name
    Nov 17 '18 at 5:20













  • Okay, so it doesn't specifically says it needs an IP, so the problem is in the Host, because there can be a CNAME record for the root domain (@). Try with ALIAS/ANAME to the herokuapp or web forwarding to the www subdomain (which as you said already has a CNAME record)

    – Lanexbg
    Nov 17 '18 at 5:56






  • 1





    I don't mean A record. If you do not see ANAME, ALIAS or some web forward / redirect records in that drop-down with the types you better contact Bluehost for a solution.

    – Lanexbg
    Nov 17 '18 at 7:01






  • 1





    Ha, yes, indeed, sorry :). Anyway, there is nothing much to add: if you want to have the ability to add CNAME/ALIAS to root domain, you have to use DNS provider that supports it.

    – Dusan Bajic
    Nov 17 '18 at 9:10



















  • Are you sure that they want an IP for a CNAME record? CNAMEs can only be pointed to hostnames, not to IP addresses. Same should go for ANAME/ALIAS records. Can you show us the error?

    – Lanexbg
    Nov 17 '18 at 5:11











  • Added an image. Not sure how helpful it'd be. I have a feeling there's no solution here other than switching DNS provider.

    – temporary_user_name
    Nov 17 '18 at 5:20













  • Okay, so it doesn't specifically says it needs an IP, so the problem is in the Host, because there can be a CNAME record for the root domain (@). Try with ALIAS/ANAME to the herokuapp or web forwarding to the www subdomain (which as you said already has a CNAME record)

    – Lanexbg
    Nov 17 '18 at 5:56






  • 1





    I don't mean A record. If you do not see ANAME, ALIAS or some web forward / redirect records in that drop-down with the types you better contact Bluehost for a solution.

    – Lanexbg
    Nov 17 '18 at 7:01






  • 1





    Ha, yes, indeed, sorry :). Anyway, there is nothing much to add: if you want to have the ability to add CNAME/ALIAS to root domain, you have to use DNS provider that supports it.

    – Dusan Bajic
    Nov 17 '18 at 9:10

















Are you sure that they want an IP for a CNAME record? CNAMEs can only be pointed to hostnames, not to IP addresses. Same should go for ANAME/ALIAS records. Can you show us the error?

– Lanexbg
Nov 17 '18 at 5:11





Are you sure that they want an IP for a CNAME record? CNAMEs can only be pointed to hostnames, not to IP addresses. Same should go for ANAME/ALIAS records. Can you show us the error?

– Lanexbg
Nov 17 '18 at 5:11













Added an image. Not sure how helpful it'd be. I have a feeling there's no solution here other than switching DNS provider.

– temporary_user_name
Nov 17 '18 at 5:20







Added an image. Not sure how helpful it'd be. I have a feeling there's no solution here other than switching DNS provider.

– temporary_user_name
Nov 17 '18 at 5:20















Okay, so it doesn't specifically says it needs an IP, so the problem is in the Host, because there can be a CNAME record for the root domain (@). Try with ALIAS/ANAME to the herokuapp or web forwarding to the www subdomain (which as you said already has a CNAME record)

– Lanexbg
Nov 17 '18 at 5:56





Okay, so it doesn't specifically says it needs an IP, so the problem is in the Host, because there can be a CNAME record for the root domain (@). Try with ALIAS/ANAME to the herokuapp or web forwarding to the www subdomain (which as you said already has a CNAME record)

– Lanexbg
Nov 17 '18 at 5:56




1




1





I don't mean A record. If you do not see ANAME, ALIAS or some web forward / redirect records in that drop-down with the types you better contact Bluehost for a solution.

– Lanexbg
Nov 17 '18 at 7:01





I don't mean A record. If you do not see ANAME, ALIAS or some web forward / redirect records in that drop-down with the types you better contact Bluehost for a solution.

– Lanexbg
Nov 17 '18 at 7:01




1




1





Ha, yes, indeed, sorry :). Anyway, there is nothing much to add: if you want to have the ability to add CNAME/ALIAS to root domain, you have to use DNS provider that supports it.

– Dusan Bajic
Nov 17 '18 at 9:10





Ha, yes, indeed, sorry :). Anyway, there is nothing much to add: if you want to have the ability to add CNAME/ALIAS to root domain, you have to use DNS provider that supports it.

– Dusan Bajic
Nov 17 '18 at 9:10












1 Answer
1






active

oldest

votes


















0














Bluehost does not support this. Google and Cloudflare do, perhaps others. Cloudflare worked for me.






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53348385%2fhow-to-point-dns-at-a-dynamic-ip-address%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Bluehost does not support this. Google and Cloudflare do, perhaps others. Cloudflare worked for me.






    share|improve this answer




























      0














      Bluehost does not support this. Google and Cloudflare do, perhaps others. Cloudflare worked for me.






      share|improve this answer


























        0












        0








        0







        Bluehost does not support this. Google and Cloudflare do, perhaps others. Cloudflare worked for me.






        share|improve this answer













        Bluehost does not support this. Google and Cloudflare do, perhaps others. Cloudflare worked for me.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 18 '18 at 7:56









        temporary_user_nametemporary_user_name

        17.2k3099165




        17.2k3099165
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53348385%2fhow-to-point-dns-at-a-dynamic-ip-address%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Bressuire

            Vorschmack

            Quarantine