#Required CF DNS Server names Changed after Namecheap Renewal

1 messages · Page 1 of 1 (latest)

sand trout
#

Why did my required nameservers change, and thus total domain outage, after a routine domain extension at namecheap?

quaint heart
#

are you sure you are logged into the right cloudflare account?

sand trout
#

mydomain.com is not benefiting from Cloudflare's network. To boost speed and security, update its nameservers.

Why did I receive this email?
mydomain.com was added to your Cloudflare account. However, this domain is still not using Cloudflare's nameservers.

How to update nameservers for this domain

  1. Log into your domain registrar (See instructions)

  2. Replace your current nameserver records with only these two:
    tess.ns.cloudflare.com
    vasilii.ns.cloudflare.com

#

woke up to that.

#

its been on coudflare dns successfully, for 3-4 years. and yes, I'm in the right account.

dreamy stream
#

So, namecheap changed your nameservers after the renewal? Or you saying that nothing changed but you still got that cloudflare notice?

sand trout
#

my perspective is something happened to make CF change what pair of DNS server names I had to use.

dreamy stream
#

Ahh, sorry. Good details. Strange.

sand trout
#

this is just the final kick to get rid of namecheap at this point. $20 for a .com is absurd.

quaint heart
#

did you renew before or after it expired?

sand trout
#

before. its an autorenewal that went throughh on the 29th

sand trout
#

SOLVED: PEBAC. Typo'd the domain, and I'm guessing the domain renewal and a reminder for an unconfigured domain... that happen to be the same domain threw me for a loop.