New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
easyDNS offers a range of DNS hosting from quite expensive to gratis with registration.
I also observed that according to most of this thread, a shared hosting customer is expected to not use DNS hosting from IncogNET or any other premium DNS host. (Maybe Cloudflare is in the same category, but I haven't digested the Cloudflare discussion in this thread.) This feels awfully limiting. Maybe a good option for some is to go ahead and use DNS of choice, and simply wait for an outage before inquiring about why the outage is happening. That strategy works unless an outage hurts one's business.
Ok, so you have lots of services outside the shared hosting where it's easier to change a dozen DNS records for the shared hosting services and want them reachable when the shared hosting is down longer than caching periods. Yes, that's the minority for shared hosting and then it's on you to maintain the external DNS records.
But it's standard practice for the hosting provider to announce IP changes for this reason. If they don't, switch providers.
The point about selecting a new host ultimately answers the question of this thread. Thank you.
To anyone who wants to belabor the subject with me, does the following scenario sound reasonable?
A domain name is used mostly for mail. The owner considers the mail to be important enough to justify being a just a bit selective about DNS hosting. Meanwhile, the owner wants to the name to resolve to a basic web site that does nothing important. She prefers this outcome over a blank, spinning wheel that visitors would see if a web site does not exist. Therefore, she selects an inexpensive shared web host and finds out the host wants her to change DNS, which would undo her previous efforts to find DNS that handles mail to her satisfaction.
Sounds absolutely fine for shared hosting. It's not normal for a host to routinely change the IP associated with a server.
In the unlikely event it's required (perhaps due to upgrades or migrations) you should be notified in advance (probably multiple notifications) and provided with ample time, as well as window in which you should make the changes.
Absolutely crazy to assume everyone is using their nameservers.
Then nobody should give two fucks if the nonexistent webhost goes offline.
The MX records use names, not IP. Even in the spf, you can use a hostname, iirc. And even so, if you really cared about mail and premium DNS, you'd have spf and DKIM monitoring setup.
Anyway, you're shenanigans up and down (free DNS from registrar becomes Premium and intentional). A lot of mental gymnastics for you to feel better about not knowing something you maybe should have.
Anyway, you bought shared hosting of multiple services, not a single one, so the expectation and easiest management is for the server to handle DNS. Full. Stop.
The other thing is, you're responsible for basic troubleshooting. You should have a managed service if you need advice and hand holding support.
Lots of noise.... So...
In short:
They changed the shared hosting IP. It doesn't happen much but when it does...
When using their DNS, as advised by them:
Ip gets auto updated in the dns records, you might not even have noticed.
When not using their DNS:
You should do it yourself. If they didn't notify of the ip change, or you missed it... Tough luck.
Had a similar issue when hostslim changed the shared hosting IP and didn't notify me. Monitor picked up the issue though, changed A records within minutes.