splash page: deprecate ns-vultr

It isn't reliable; It's off the last week of the month.
This commit is contained in:
Brian Cunnie
2020-11-27 16:01:37 -08:00
parent 5269ed5ecb
commit 3e8d3d263a

View File

@@ -105,9 +105,14 @@ src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> <![endif]-->
own the domain “example.com”, and you want your subdomain, “xip.example.com” to have xip.io-style features. To own the domain “example.com”, and you want your subdomain, “xip.example.com” to have xip.io-style features. To
accomplish this, set the following four DNS servers as NS records for the subdomain accomplish this, set the following four DNS servers as NS records for the subdomain
“xip.example.com”</p> “xip.example.com”</p>
<div class="alert alert-warning" role="alert">
<b>2019-07-31 Nameserver (NS) Change!</b> Update your nameservers. We
have deprecated ns-vultr.nono.io because it's turned off the last week
of the month when it has reached its 3 TB bandwidth quota.
</div>
<div class="alert alert-warning" role="alert"> <div class="alert alert-warning" role="alert">
<b>2018-09-20 Nameserver (NS) Change!</b> Update your nameservers. We have <b>2018-09-20 Nameserver (NS) Change!</b> Update your nameservers. We have
deprecated ns-he.nono.io in favor of <b>ns-vultr.nono.io</b> deprecated ns-he.nono.io <del>in favor of ns-vultr.nono.io</del>.
</div> </div>
<table class="table"> <table class="table">
<thead> <thead>