home.social

#googledomains — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #googledomains, aggregated by home.social.

fetched live
  1. I recently moved my personal vanity domain (isaacwyatt.com) to Porkbun. I didn't know before moving that they don't support wildcards in their email forwarding like you can do with gmail, or other registrars.

    I'll have to figure something out since I have a lot of wildcard patterns for various things like newsletters and certain websites or services.

    #PorkBun #GoogleDomains #SquareSpace

  2. I recently moved my personal vanity domain (isaacwyatt.com) to Porkbun. I didn't know before moving that they don't support wildcards in their email forwarding like you can do with gmail, or other registrars.

    I'll have to figure something out since I have a lot of wildcard patterns for various things like newsletters and certain websites or services.

    #PorkBun #GoogleDomains #SquareSpace

  3. I recently moved my personal vanity domain (isaacwyatt.com) to Porkbun. I didn't know before moving that they don't support wildcards in their email forwarding like you can do with gmail, or other registrars.

    I'll have to figure something out since I have a lot of wildcard patterns for various things like newsletters and certain websites or services.

  4. I recently moved my personal vanity domain (isaacwyatt.com) to Porkbun. I didn't know before moving that they don't support wildcards in their email forwarding like you can do with gmail, or other registrars.

    I'll have to figure something out since I have a lot of wildcard patterns for various things like newsletters and certain websites or services.

    #PorkBun #GoogleDomains #SquareSpace

  5. I recently moved my personal vanity domain (isaacwyatt.com) to Porkbun. I didn't know before moving that they don't support wildcards in their email forwarding like you can do with gmail, or other registrars.

    I'll have to figure something out since I have a lot of wildcard patterns for various things like newsletters and certain websites or services.

    #PorkBun #GoogleDomains #SquareSpace

  6. Some great #SRE war stories have been told this week at #srecon. Two of the most compelling were told by #Bluesky and #Squarespace engineers, as detailed here. #postmortem #googledomains #incidentpostmortem #projectpostmortem

    ttps://www.techtarget.com/searchitoperations/news/366621615/BlueSky-Squarespace-pros-give-incident-project-postmortems

  7. Some great #SRE war stories have been told this week at #srecon. Two of the most compelling were told by #Bluesky and #Squarespace engineers, as detailed here. #postmortem #googledomains #incidentpostmortem #projectpostmortem

    ttps://www.techtarget.com/searchitoperations/news/366621615/BlueSky-Squarespace-pros-give-incident-project-postmortems

  8. Some great war stories have been told this week at . Two of the most compelling were told by and engineers, as detailed here.

    ttps://www.techtarget.com/searchitoperations/news/366621615/BlueSky-Squarespace-pros-give-incident-project-postmortems

  9. Some great #SRE war stories have been told this week at #srecon. Two of the most compelling were told by #Bluesky and #Squarespace engineers, as detailed here. #postmortem #googledomains #incidentpostmortem #projectpostmortem

    ttps://www.techtarget.com/searchitoperations/news/366621615/BlueSky-Squarespace-pros-give-incident-project-postmortems

  10. Some great #SRE war stories have been told this week at #srecon. Two of the most compelling were told by #Bluesky and #Squarespace engineers, as detailed here. #postmortem #googledomains #incidentpostmortem #projectpostmortem

    ttps://www.techtarget.com/searchitoperations/news/366621615/BlueSky-Squarespace-pros-give-incident-project-postmortems

  11. #GoogleDomains で登録して移管しわすれてたドメイン、 #Squarespace というサービスに移管されてた :tony_neutral:

  12. #GoogleDomains で登録して移管しわすれてたドメイン、 #Squarespace というサービスに移管されてた :tony_neutral:

  13. #GoogleDomains で登録して移管しわすれてたドメイン、 #Squarespace というサービスに移管されてた :tony_neutral:

  14. #GoogleDomains で登録して移管しわすれてたドメイン、 #Squarespace というサービスに移管されてた :tony_neutral:

  15. #GoogleDomains で登録して移管しわすれてたドメイン、 #Squarespace というサービスに移管されてた :tony_neutral:

  16. ### How Long Does it Take to Announce a Domain Name?

    The time required for a newly registered domain name to become fully operational on the internet can vary due to several factors. Below, we'll break down some key aspects that influence the domain announcement process:

    #### 1. DNS Propagation
    **DNS (Domain Name System)** propagation refers to the process of updating the DNS records globally after you make changes to your domain’s settings, such as pointing it to a new server. This update is required for your domain to resolve to the correct IP address.

    This process can take **anywhere from a few hours to 48 hours** to complete. Typically, **24 hours** is the standard period for DNS propagation. However, certain conditions, like your internet service provider (ISP) caching old DNS information, can cause delays.

    #### 2. Domain Registration Process
    If you’ve just registered a new domain, the actual registration typically happens **within minutes to a few hours**. Some domain registrars complete this nearly instantly, especially when using automated systems. However, manual checks, domain availability, and specific verification requirements can sometimes cause a slight delay.

    Even if your domain is registered quickly, it still requires some time for global DNS servers to recognize the new information. That’s where DNS propagation comes into play.

    #### 3. Blogger and Other Blogging Platforms
    If you're using platforms like **Blogger**, the process of linking a custom domain can take anywhere from **a few minutes to a few hours**. These systems automatically connect your domain once the DNS records are correctly configured, and the changes propagate.

    Usually, after correctly configuring DNS settings for a domain linked to Blogger, most users see their websites live within an hour or two. In rare cases, it could take a little longer—up to 24 hours—depending on the platform's server load and DNS settings.

    ### How to Avoid DNS Propagation Delays
    To ensure that your domain becomes live quickly and without issues, here are some best practices:
    - **Check DNS Records**: Double-check the DNS records (like **A records**, **CNAME**, etc.) to ensure everything is configured properly. Many domain registrars and hosting providers offer DNS management tools to assist you.
    - **Clear DNS Cache**: If you’re having trouble seeing your site after making changes, your browser or computer may still be using old DNS data. Try clearing your DNS cache or use an **Incognito** or **Private** browser window to bypass local cache.
    - **Check with Your ISP**: Some ISPs cache DNS information for longer periods, so even if global DNS has updated, your ISP may still be using outdated data.

    ### What to Do If Your Domain Isn't Working After 48 Hours
    If you find that your domain is still not working after waiting the full 48-hour DNS propagation window, here are a few steps you can take:
    1. **Verify DNS Settings**: Use DNS testing tools like **WhatsMyDNS.net** to check if the correct DNS records have propagated globally.
    2. **Contact Your Registrar or Hosting Provider**: Reach out to your domain registrar or hosting provider to ensure there are no issues with the domain settings or registration.
    3. **Troubleshoot**: Check that there are no typos or misconfigurations in your DNS records (e.g., incorrect IP addresses).

    ### Conclusion
    The process of announcing and setting up a domain name typically happens quickly, but it’s important to allow up to **48 hours** for full DNS propagation. The actual time may vary depending on your DNS settings, internet service provider, and the platforms you’re integrating with, such as **Blogger**.

    By following best practices, like double-checking your DNS records and clearing cache, you can minimize delays and ensure a smooth setup process.

    ### Hashtags:
    #DNS #DomainName #DNSPropagation #Blogger #DomainRegistration #InternetProviders #GoogleDomains #CacheClearance #DNSSettings #WhatsMyDNS #BloggerSupport #InternetSecurity #WebHosting

  17. ### How Long Does it Take to Announce a Domain Name?

    The time required for a newly registered domain name to become fully operational on the internet can vary due to several factors. Below, we'll break down some key aspects that influence the domain announcement process:

    #### 1. DNS Propagation
    **DNS (Domain Name System)** propagation refers to the process of updating the DNS records globally after you make changes to your domain’s settings, such as pointing it to a new server. This update is required for your domain to resolve to the correct IP address.

    This process can take **anywhere from a few hours to 48 hours** to complete. Typically, **24 hours** is the standard period for DNS propagation. However, certain conditions, like your internet service provider (ISP) caching old DNS information, can cause delays.

    #### 2. Domain Registration Process
    If you’ve just registered a new domain, the actual registration typically happens **within minutes to a few hours**. Some domain registrars complete this nearly instantly, especially when using automated systems. However, manual checks, domain availability, and specific verification requirements can sometimes cause a slight delay.

    Even if your domain is registered quickly, it still requires some time for global DNS servers to recognize the new information. That’s where DNS propagation comes into play.

    #### 3. Blogger and Other Blogging Platforms
    If you're using platforms like **Blogger**, the process of linking a custom domain can take anywhere from **a few minutes to a few hours**. These systems automatically connect your domain once the DNS records are correctly configured, and the changes propagate.

    Usually, after correctly configuring DNS settings for a domain linked to Blogger, most users see their websites live within an hour or two. In rare cases, it could take a little longer—up to 24 hours—depending on the platform's server load and DNS settings.

    ### How to Avoid DNS Propagation Delays
    To ensure that your domain becomes live quickly and without issues, here are some best practices:
    - **Check DNS Records**: Double-check the DNS records (like **A records**, **CNAME**, etc.) to ensure everything is configured properly. Many domain registrars and hosting providers offer DNS management tools to assist you.
    - **Clear DNS Cache**: If you’re having trouble seeing your site after making changes, your browser or computer may still be using old DNS data. Try clearing your DNS cache or use an **Incognito** or **Private** browser window to bypass local cache.
    - **Check with Your ISP**: Some ISPs cache DNS information for longer periods, so even if global DNS has updated, your ISP may still be using outdated data.

    ### What to Do If Your Domain Isn't Working After 48 Hours
    If you find that your domain is still not working after waiting the full 48-hour DNS propagation window, here are a few steps you can take:
    1. **Verify DNS Settings**: Use DNS testing tools like **WhatsMyDNS.net** to check if the correct DNS records have propagated globally.
    2. **Contact Your Registrar or Hosting Provider**: Reach out to your domain registrar or hosting provider to ensure there are no issues with the domain settings or registration.
    3. **Troubleshoot**: Check that there are no typos or misconfigurations in your DNS records (e.g., incorrect IP addresses).

    ### Conclusion
    The process of announcing and setting up a domain name typically happens quickly, but it’s important to allow up to **48 hours** for full DNS propagation. The actual time may vary depending on your DNS settings, internet service provider, and the platforms you’re integrating with, such as **Blogger**.

    By following best practices, like double-checking your DNS records and clearing cache, you can minimize delays and ensure a smooth setup process.

    ### Hashtags:
    #DNS #DomainName #DNSPropagation #Blogger #DomainRegistration #InternetProviders #GoogleDomains #CacheClearance #DNSSettings #WhatsMyDNS #BloggerSupport #InternetSecurity #WebHosting

  18. ### How Long Does it Take to Announce a Domain Name?

    The time required for a newly registered domain name to become fully operational on the internet can vary due to several factors. Below, we'll break down some key aspects that influence the domain announcement process:

    #### 1. DNS Propagation
    **DNS (Domain Name System)** propagation refers to the process of updating the DNS records globally after you make changes to your domain’s settings, such as pointing it to a new server. This update is required for your domain to resolve to the correct IP address.

    This process can take **anywhere from a few hours to 48 hours** to complete. Typically, **24 hours** is the standard period for DNS propagation. However, certain conditions, like your internet service provider (ISP) caching old DNS information, can cause delays.

    #### 2. Domain Registration Process
    If you’ve just registered a new domain, the actual registration typically happens **within minutes to a few hours**. Some domain registrars complete this nearly instantly, especially when using automated systems. However, manual checks, domain availability, and specific verification requirements can sometimes cause a slight delay.

    Even if your domain is registered quickly, it still requires some time for global DNS servers to recognize the new information. That’s where DNS propagation comes into play.

    #### 3. Blogger and Other Blogging Platforms
    If you're using platforms like **Blogger**, the process of linking a custom domain can take anywhere from **a few minutes to a few hours**. These systems automatically connect your domain once the DNS records are correctly configured, and the changes propagate.

    Usually, after correctly configuring DNS settings for a domain linked to Blogger, most users see their websites live within an hour or two. In rare cases, it could take a little longer—up to 24 hours—depending on the platform's server load and DNS settings.

    ### How to Avoid DNS Propagation Delays
    To ensure that your domain becomes live quickly and without issues, here are some best practices:
    - **Check DNS Records**: Double-check the DNS records (like **A records**, **CNAME**, etc.) to ensure everything is configured properly. Many domain registrars and hosting providers offer DNS management tools to assist you.
    - **Clear DNS Cache**: If you’re having trouble seeing your site after making changes, your browser or computer may still be using old DNS data. Try clearing your DNS cache or use an **Incognito** or **Private** browser window to bypass local cache.
    - **Check with Your ISP**: Some ISPs cache DNS information for longer periods, so even if global DNS has updated, your ISP may still be using outdated data.

    ### What to Do If Your Domain Isn't Working After 48 Hours
    If you find that your domain is still not working after waiting the full 48-hour DNS propagation window, here are a few steps you can take:
    1. **Verify DNS Settings**: Use DNS testing tools like **WhatsMyDNS.net** to check if the correct DNS records have propagated globally.
    2. **Contact Your Registrar or Hosting Provider**: Reach out to your domain registrar or hosting provider to ensure there are no issues with the domain settings or registration.
    3. **Troubleshoot**: Check that there are no typos or misconfigurations in your DNS records (e.g., incorrect IP addresses).

    ### Conclusion
    The process of announcing and setting up a domain name typically happens quickly, but it’s important to allow up to **48 hours** for full DNS propagation. The actual time may vary depending on your DNS settings, internet service provider, and the platforms you’re integrating with, such as **Blogger**.

    By following best practices, like double-checking your DNS records and clearing cache, you can minimize delays and ensure a smooth setup process.

    ### Hashtags:
    #DNS #DomainName #DNSPropagation #Blogger #DomainRegistration #InternetProviders #GoogleDomains #CacheClearance #DNSSettings #WhatsMyDNS #BloggerSupport #InternetSecurity #WebHosting

  19. ### How Long Does it Take to Announce a Domain Name?

    The time required for a newly registered domain name to become fully operational on the internet can vary due to several factors. Below, we'll break down some key aspects that influence the domain announcement process:

    #### 1. DNS Propagation
    **DNS (Domain Name System)** propagation refers to the process of updating the DNS records globally after you make changes to your domain’s settings, such as pointing it to a new server. This update is required for your domain to resolve to the correct IP address.

    This process can take **anywhere from a few hours to 48 hours** to complete. Typically, **24 hours** is the standard period for DNS propagation. However, certain conditions, like your internet service provider (ISP) caching old DNS information, can cause delays.

    #### 2. Domain Registration Process
    If you’ve just registered a new domain, the actual registration typically happens **within minutes to a few hours**. Some domain registrars complete this nearly instantly, especially when using automated systems. However, manual checks, domain availability, and specific verification requirements can sometimes cause a slight delay.

    Even if your domain is registered quickly, it still requires some time for global DNS servers to recognize the new information. That’s where DNS propagation comes into play.

    #### 3. Blogger and Other Blogging Platforms
    If you're using platforms like **Blogger**, the process of linking a custom domain can take anywhere from **a few minutes to a few hours**. These systems automatically connect your domain once the DNS records are correctly configured, and the changes propagate.

    Usually, after correctly configuring DNS settings for a domain linked to Blogger, most users see their websites live within an hour or two. In rare cases, it could take a little longer—up to 24 hours—depending on the platform's server load and DNS settings.

    ### How to Avoid DNS Propagation Delays
    To ensure that your domain becomes live quickly and without issues, here are some best practices:
    - **Check DNS Records**: Double-check the DNS records (like **A records**, **CNAME**, etc.) to ensure everything is configured properly. Many domain registrars and hosting providers offer DNS management tools to assist you.
    - **Clear DNS Cache**: If you’re having trouble seeing your site after making changes, your browser or computer may still be using old DNS data. Try clearing your DNS cache or use an **Incognito** or **Private** browser window to bypass local cache.
    - **Check with Your ISP**: Some ISPs cache DNS information for longer periods, so even if global DNS has updated, your ISP may still be using outdated data.

    ### What to Do If Your Domain Isn't Working After 48 Hours
    If you find that your domain is still not working after waiting the full 48-hour DNS propagation window, here are a few steps you can take:
    1. **Verify DNS Settings**: Use DNS testing tools like **WhatsMyDNS.net** to check if the correct DNS records have propagated globally.
    2. **Contact Your Registrar or Hosting Provider**: Reach out to your domain registrar or hosting provider to ensure there are no issues with the domain settings or registration.
    3. **Troubleshoot**: Check that there are no typos or misconfigurations in your DNS records (e.g., incorrect IP addresses).

    ### Conclusion
    The process of announcing and setting up a domain name typically happens quickly, but it’s important to allow up to **48 hours** for full DNS propagation. The actual time may vary depending on your DNS settings, internet service provider, and the platforms you’re integrating with, such as **Blogger**.

    By following best practices, like double-checking your DNS records and clearing cache, you can minimize delays and ensure a smooth setup process.

    ### Hashtags:
    #DNS #DomainName #DNSPropagation #Blogger #DomainRegistration #InternetProviders #GoogleDomains #CacheClearance #DNSSettings #WhatsMyDNS #BloggerSupport #InternetSecurity #WebHosting

  20. Hubo un tiempo en el que #Google era sinónimo de éxito e innovación. Sí, también mataban servicios, pero lo hacían pronto y realmente eran cosas que nunca despegaron. El momento en el que para un servicio no era suficiente con que fuera bueno si no que además necesitaba ser rentable para sobrevivir, fue cuando esa empresa dejó de ser de fiar.
    Jamás les perdonaré lo de #GoogleReader o #GoogleDomains más recientemente.
    #enshittification

    From: @corbet
    social.kernel.org/objects/3912

  21. Hubo un tiempo en el que #Google era sinónimo de éxito e innovación. Sí, también mataban servicios, pero lo hacían pronto y realmente eran cosas que nunca despegaron. El momento en el que para un servicio no era suficiente con que fuera bueno si no que además necesitaba ser rentable para sobrevivir, fue cuando esa empresa dejó de ser de fiar.
    Jamás les perdonaré lo de #GoogleReader o #GoogleDomains más recientemente.
    #enshittification

    From: @corbet
    social.kernel.org/objects/3912

  22. Hubo un tiempo en el que #Google era sinónimo de éxito e innovación. Sí, también mataban servicios, pero lo hacían pronto y realmente eran cosas que nunca despegaron. El momento en el que para un servicio no era suficiente con que fuera bueno si no que además necesitaba ser rentable para sobrevivir, fue cuando esa empresa dejó de ser de fiar.
    Jamás les perdonaré lo de #GoogleReader o #GoogleDomains más recientemente.
    #enshittification

    From: @corbet
    social.kernel.org/objects/3912

  23. Hubo un tiempo en el que #Google era sinónimo de éxito e innovación. Sí, también mataban servicios, pero lo hacían pronto y realmente eran cosas que nunca despegaron. El momento en el que para un servicio no era suficiente con que fuera bueno si no que además necesitaba ser rentable para sobrevivir, fue cuando esa empresa dejó de ser de fiar.
    Jamás les perdonaré lo de #GoogleReader o #GoogleDomains más recientemente.
    #enshittification

    From: @corbet
    social.kernel.org/objects/3912

  24. #GoogleDomains, #Squarespace
    The Olympia Indivisible website was created on #Weebly. #Square purchased weebly and we were moved over. Big Trouble! #RedirectHell A new person who we are trying to make an admin can not join our site because he previously had a square account. We have made many contacts with square help to no avail. Does anyone have a recommendation for moving the platform?

  25. #GoogleDomains, #Squarespace
    The Olympia Indivisible website was created on #Weebly. #Square purchased weebly and we were moved over. Big Trouble! #RedirectHell A new person who we are trying to make an admin can not join our site because he previously had a square account. We have made many contacts with square help to no avail. Does anyone have a recommendation for moving the platform?

  26. #GoogleDomains, #Squarespace
    The Olympia Indivisible website was created on #Weebly. #Square purchased weebly and we were moved over. Big Trouble! #RedirectHell A new person who we are trying to make an admin can not join our site because he previously had a square account. We have made many contacts with square help to no avail. Does anyone have a recommendation for moving the platform?

  27. #GoogleDomains, #Squarespace
    The Olympia Indivisible website was created on #Weebly. #Square purchased weebly and we were moved over. Big Trouble! #RedirectHell A new person who we are trying to make an admin can not join our site because he previously had a square account. We have made many contacts with square help to no avail. Does anyone have a recommendation for moving the platform?

  28. #GoogleDomains, #Squarespace
    The Olympia Indivisible website was created on #Weebly. #Square purchased weebly and we were moved over. Big Trouble! #RedirectHell A new person who we are trying to make an admin can not join our site because he previously had a square account. We have made many contacts with square help to no avail. Does anyone have a recommendation for moving the platform?

  29. Nothing like being informed that you are a #squarespace customer, despite never wanting or agreeing to be one. Thanks #GoogleDomains!

    support.google.com/domains/ans

  30. Nothing like being informed that you are a #squarespace customer, despite never wanting or agreeing to be one. Thanks #GoogleDomains!

    support.google.com/domains/ans

  31. It's a shame you can't export all your #GoogleDomains info with Takeout. That would have made life a lot easier right now.

  32. It's a shame you can't export all your #GoogleDomains info with Takeout. That would have made life a lot easier right now.

  33. It's a shame you can't export all your #GoogleDomains info with Takeout. That would have made life a lot easier right now.

  34. It's a shame you can't export all your #GoogleDomains info with Takeout. That would have made life a lot easier right now.

  35. It's a shame you can't export all your #GoogleDomains info with Takeout. That would have made life a lot easier right now.

  36. Successfully transferred the first of many domains from #GoogleDomains to #Porkbun. So far the only thing I had to do after the transfer was set up the email forwarding.

  37. Successfully transferred the first of many domains from #GoogleDomains to #Porkbun. So far the only thing I had to do after the transfer was set up the email forwarding.

  38. Successfully transferred the first of many domains from #GoogleDomains to #Porkbun. So far the only thing I had to do after the transfer was set up the email forwarding.

  39. Successfully transferred the first of many domains from #GoogleDomains to #Porkbun. So far the only thing I had to do after the transfer was set up the email forwarding.