Skip to content

moving domain to google domains

Configure
6 2 1.3k
  • I am moving in my domain to google domains. i have authorized the security code and everything and it will be moved in automatically in 5days.

    while moving into google domain it offered the settings to keep existing DNS settings which is CF i have checked that option.

    hoping everything will be moved successfully. once it is moved i have to make sure everything is working HTTPS at CF and also need to set email forward at google domain.

    as you know at times i am experiencing HTTP to HTTPS redirect failures, shall i set the HTTPS option at google DNS level?

    do you have any other suggestions?

    https://community.cloudflare.com/t/help-how-do-i-get-google-domains-email-forwarding-to-work-with-cloudflare-dns/163813
    https://support.google.com/domains/answer/9428703

  • I am moving in my domain to google domains. i have authorized the security code and everything and it will be moved in automatically in 5days.

    while moving into google domain it offered the settings to keep existing DNS settings which is CF i have checked that option.

    hoping everything will be moved successfully. once it is moved i have to make sure everything is working HTTPS at CF and also need to set email forward at google domain.

    as you know at times i am experiencing HTTP to HTTPS redirect failures, shall i set the HTTPS option at google DNS level?

    do you have any other suggestions?

    https://community.cloudflare.com/t/help-how-do-i-get-google-domains-email-forwarding-to-work-with-cloudflare-dns/163813
    https://support.google.com/domains/answer/9428703

    @hari If you’re still using Cloudflare to pass the traffic through then you should leave everything as it is and ensure you force https at that level. Moving the domain to Google will have no bearing on the https side of things if they are not hosting the site directly.

  • @hari If you’re still using Cloudflare to pass the traffic through then you should leave everything as it is and ensure you force https at that level. Moving the domain to Google will have no bearing on the https side of things if they are not hosting the site directly.

    @phenomlab

    //update// I have successfully moved to google domains and configured email forwarder so far everything is working fine.

    emails are forwarding to gmail and outgoing emails are sent using elastic email for cloudways.

    while configuring forwarders i have come across DNSSEC

    and i configured following this, this one line looks scary

    ce359788-fd95-41e9-b22a-6a93aacec23b-image.png

    should i hit publish? or do indeed to wait till Sep 18, 2021, 12:00:00 PM ?

    i am using google domains with CF. by publishing this will cause any downtime?

  • @phenomlab

    //update// I have successfully moved to google domains and configured email forwarder so far everything is working fine.

    emails are forwarding to gmail and outgoing emails are sent using elastic email for cloudways.

    while configuring forwarders i have come across DNSSEC

    and i configured following this, this one line looks scary

    ce359788-fd95-41e9-b22a-6a93aacec23b-image.png

    should i hit publish? or do indeed to wait till Sep 18, 2021, 12:00:00 PM ?

    i am using google domains with CF. by publishing this will cause any downtime?

    @hari If the domain is in the progress of being migrated, then I’d personally wait rather than force the activation of DNSSEC. In most cases, DNSSEC itself does not cause any downtime, but if your domain is still in the migration phase, then this could represent issues which are easily avoided by simply waiting.

    Personally, I’d let everything bed in for a week to ensure it’s all ok before enabling anything else.

  • @hari If the domain is in the progress of being migrated, then I’d personally wait rather than force the activation of DNSSEC. In most cases, DNSSEC itself does not cause any downtime, but if your domain is still in the migration phase, then this could represent issues which are easily avoided by simply waiting.

    Personally, I’d let everything bed in for a week to ensure it’s all ok before enabling anything else.

    @phenomlab as per your suggestion after updating the tag and key i left it alone, thought i can publish it later after 2 or 3 days.

    today, when i rechecked google domains already published it and CF, detected it.

    52dfa771-3a66-4e95-ac4b-804c72fe9b13-image.png

    So, that is all we need to do?

    🥳

    Solved

  • @phenomlab as per your suggestion after updating the tag and key i left it alone, thought i can publish it later after 2 or 3 days.

    today, when i rechecked google domains already published it and CF, detected it.

    52dfa771-3a66-4e95-ac4b-804c72fe9b13-image.png

    So, that is all we need to do?

    🥳

    Solved

    @hari That’s it. Yes. Nothing more to do


Related Topics
  • 4 Votes
    11 Posts
    2k Views
    @Hari Really? Can you elaborate a bit more here?
  • 10 Votes
    12 Posts
    3k Views
    @veronikya said in Cloudflare bot fight mode and Google search: docker modifications are a pain in the ass, I couldn’t have put that better myself - such an accurate analogy. I too have “been there” with this pain factor, and I swore I’d never do it again.
  • DNS to Point Domain Name to

    Solved Configure dns entries
    13
    3 Votes
    13 Posts
    2k Views
    @Madchatthew good luck
  • 3 Votes
    4 Posts
    2k Views
    @DownPW yeah, I seem to spend a large amount of my time trying to educate people that there’s no silver bullet when it comes to security.
  • Where to add to DNS settings for Google crawl

    Solved Configure dns
    4
    1 Votes
    4 Posts
    1k Views
    @eveh yes, as the DNS will be natively registered there.
  • how to use CF tunnels with Virtualmin?

    Solved Configure cf tunnel cloudflare virtualmin
    10
    3 Votes
    10 Posts
    2k Views
    @Hari DDoS protection is not just a switch, or one component. It’s a collection of different and often disparate technologies that when grouped together form the basis of a combined toolset that can be used in defence. Typically these consist of IDS (Instrusion Detection System) and IPS (Intrusion Prevention System) components that detect irregularities in network traffic, and will take decisive action based on predefined rulesets, or in the case of more modern systems, AI and ML. Traditional “traffic shaping” technology is also deployed, so if an attack cannot be easily identified as malicious, the bandwidth available to that connection is severely limited to nothing more than a trickle rather than a full flow. Years ago, ISP’s used traffic shaping (also called “policers”) as an effective means of stopping applications such as BearShare, eDonkey, Napster, and other P2P based sharing systems from functioning correctly - essentially reducing the “appeal” of distributing and seeding illegal downloads. This was essentially the ISP’s way of saying “stop what you are doing please” without actually pulling the plug. These days, DDoS attacks are designed to overwhelm - not assume control of - webservers and other public facing components. It’s rare for small entities to be attacked unless there is some form of political agenda driven by your site or product. A classic example is governmental institutions or lawmakers who effectively are classed as “enforcers” and those who disagree are effectively making a statement in the form of Denial of Service. DDoS protection is effectively the responsibility of the hosting provider, but you shouldn’t just assume that they will protect you or your site. Their responsibility stops at their infrastructure, so it’s then up to you too decide how you full the gap in between your host and the website. Typically, you’d leverage something like Imunify360 which you can get for Plesk (and something I’d strongly recommend) but it’s not free, and is a paid (not expensive per month) subscription. If you want to use VirtualMin then there are a variety of tools readily available out of the box such as firewalls and fail2ban.
  • 1 Votes
    2 Posts
    842 Views
    @hari the cache level for woocommerce should always be bypass. Any caching of woocommerce will cause you serious issues and will result in the checkout process not functioning correctly. This does mean that the overall experience will be slower (depending on geographic location) although CF is known to cause significant issues hence the need to bypass. If you want to cache as much as possible, then set rules to bypass caching on the cart and account pages etc.
  • Redirect Google registered domain

    Solved Hosting
    4
    1 Votes
    4 Posts
    947 Views
    @phenomlab Just had a look at all settings and advice given. I’m going to set up the redirect once I have the forum ready to accept members. I’d hate for anyone to be forwarded at this moment in time .