Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi all,
I have my own domain that is already used to access GitLab pages and I'm going to switch it to Github pages.
I have to change the DNS records and then check the custom domain in settings.
But DNS records can take a significant amount of time to be propagated, and some visitors may experience lengthy outages if they get the domain resolved into the new IP while Github still have it resolved to the old IP and cannot check the domain on its end.
Are there any options to reduce this gap and make the whole process as seamless as possible?
I've reduced the TTL to 300 seconds and plan to change the DNS record in 2 days. Is this the only thing I can do?
Beta Was this translation helpful? Give feedback.
All reactions