Godaddy custom domain cant set txt

Replit Help
1

Question:
I cannot get my domain chat.keyplays.co pointing to my private repil

  1. i set cname and it chat pointing to xxxxxxxxxxx-1dc4c11153d6.id.repl.co.
  2. I try to set txt to replit-verify=xxxxxxxxxx-1dc4c11153d6
    But I get Record name chat conflicts with another record.

I dont know what to do next

3

Hey @malcsilberman!

Thank you for reporting this, we will take a look.

1 Like
4

As a temporary workaround, set up your domain with Cloudflare as it will allow you to add both a CNAME and TXT record on the same domain.

2 Likes
5

I need to retain godaddy as my main domain uses website builder - i only want a subdomain pointing to replit. It is setup correctly with the right cname - I have triple tested this but it never resollves properly. Rather it - see screenshot as to where it resolves too;

Screenshot 2023-04-29 5.31.54 PM
Screenshot 2023-04-29 5.31.54 PM1027×755 22 KB

6

We have been able to identify the issue as a high-priority bug and have created a post for updates: Custom domains fail to connect - #2

1 Like
7

sill got the issue

image
image336×693 39.3 KB

8

@ShaneAtReplit when will this be solved - its nearly 2 weeks and its a critical thing for any hosting. I have to consider moving elsewhere if not solved quickly.
Many thanks

9

I will follow up with the team regarding the investigation. We should be in a good place now to work on a fix, although I’m not 100% sure. I will post all updates to https://status.replit.com/notices/ecfncsbq0ze2juvq-custom-domains-stuck-verifying regarding the issue.

1 Like
10

I see this update but its really strange 1) why has this only now been discovered as a bug since people should have been using this since you began? 2) lots of other ‘hosting’ companies do this eg. I do it on google cloud for some sub-domains - why is it so difficult for you guys to sort out?

Upon investigation, we have identified that this issue is related to CNAME flattening, where various DNS resolvers automatically add an A record along with the CNAME record, preventing us from verifying the domain. We are actively working on finding a solution to address this on our end and resolve the verification issue. We apologize for any inconvenience caused and appreciate your patience as we work towards a resolution.

11

We believe this to be caused by a recent change on our end, which wasn’t the case originally. However, we are still unsure how to resolve this an are still looking for mitigation strategies.

1 Like
12

Also having this issue!! Please fix asap.

13

@ShaneAtReplit any update here?!

14

I apologize for the delay in replying, I thought I went through all of my domain-linking posts and posted the update we made, but I had forgotten this one!

We have concluded our investigation of this issue and have posted the update here:

1 Like