TXT DNS record is not propagating
Webflow is unable to verify the domain. I did this 10 hours ago but it still isn't working.
Any thing I can do on my end to help it? 🙏🏼
30 Replies
DNS over Discord: A records
enterthejungleverse.com. A @8.8.8.8 +noall +answer
diggy diggy hole
How do I fix this ?
Not sure if you've already deleted the record, but because you created the txt under
_webflow, you'd need to look it up as _webflow.enterthejungleverse.com TXT, you'd never see it on the root of your site itself@Chaika hey are you still online?
I still can't seem to get it right
this is my site now
my godaddy account says this but my cloudflare account says this
what is going on 😭
Those are def not your Cloudflare nameservers
on this page, if you go down a bit, it will tell you "Your assigned Cloudflare nameservers" and list them both
going to be <male or female name>.ns.cloudflare.com, like chan.ns.cloudflare.com. You need to get the exact two for your domain to become active
@Chaika so I just need to put these ones on the godaddy site?
yep, where ns1 and ns2 are now under custom nameservers
also, the site said this moved. how is that possible? I ask because I only have one account
Moved out of Cloudflare since you changed the nameservers to something else after it became active
and that change happened on godaddy not cloudflare, right ?
also thanks for the help @Chaika you have been extremely helpfuld
and that change happened on godaddy not cloudflare, right ?changing the nameservers set for your domain, yea
how long will it take once I change the nameservers to the new ones will it take to get my site back up?
@Chaika
Question is more about from who and what context. com domains are pretty quick to update once you change the nameservers, like less then 30 mins for their authoritive nameservers to start returning the new. Then the rest is all just DNS Resolver and local dns caching. Some ISP Resolvers cache for a long time and ignore ttls
This site is for a client and I think the subcontractor who manages their godaddy is trying to sabotage my team and I.
Thank you so much for your help.
he is literally calling us out saying the site is broken and it is our fault but it seems that someone changed the nameservers in godaddy
I would look into if Godaddy has audit logs or some history logs
also, hope I am not bothering you with all the @s I know you have a lot of support tickets
100% great idea. hopefully they do
Worth noting I'm not a CF Employee if that's what you mean. Green Names/Community Champs are just Volunteers who have some ability to escalate things (and good general knowledge of cf and such). Orange Names/Cloudflare roles are actual employees
I had the same problem with squares provider
bro, you're a beast. can I send you a tip or something ? do you do freelance work?
@Chaika
Nah I appreciate the thought though, I just like Cloudflare and help out sometimes in my spare time
can nameservers ever change automatically in godaddy?
please excuse my ignorance @Chaika
To something that is different but invalid like ns1.cloudflare.com? I really doubt it, but I do not use Godaddy or know too much about them. I can't think of a logical reason they would have anything that would switch them automatically to something random though
For example, Google Domains (rip) used to have an annoying behavior where changing some settings in their panel would reset the nameservers to default/Google owned automatically and confuse people, but why would it go to ns1.cloudflare.com and ns2.cloudflare.com? Those aren't CF Nameservers anyone would be assigned
I mean you can google yourself
godaddy changed nameservers to "ns1.cloudflare.com", not really any hits of interest. Changing nameservers is a very easily destructive action and not anything any reputable domain registrar should be doing on a whimcopy that, I will keep you posted. @Chaika gonna find out tomorrow morning if it was actual sabotage