• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

stupid webhost (fixed)

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Wow, odd. Dixiesys doesn't allow DNS IP changes, but godaddy does. Something didn't match up in the conversation between Wong and I. When he was telling me to change the IP that the DNS nameserver was registered to, I figured he was talking about ffmcobalt.com because predigio.net works perfectly. Why fix something that isn't broken, right? Wrong. I changed the IP for predigio.net's DNS registration and since ffmcobalt.com is registered under predigio.net's reseller's account, this is somehow supposed to fix whether or not ffmcobalt.com resolves. 😕

Mkay whatever.
 
Originally posted by: RossMAN
I never knew this. You're also a UU customer.

Small world.
Based on your recommendation, yes. For approximately the last six months.

Again, many thanks for your help in that regard.
 
Originally posted by: Nik
Wow, odd. Dixiesys doesn't allow DNS IP changes, but godaddy does. Something didn't match up in the conversation between Wong and I. When he was telling me to change the IP that the DNS nameserver was registered to, I figured he was talking about ffmcobalt.com because predigio.net works perfectly. Why fix something that isn't broken, right? Wrong. I changed the IP for predigio.net's DNS registration and since ffmcobalt.com is registered under predigio.net's reseller's account, this is somehow supposed to fix whether or not ffmcobalt.com resolves. 😕

Mkay whatever.
Actually, that makes complete sense.

I had originally thought you had private name servers set up on both domains (ie, NSx.predigio.net and NSx.ffmcobalt.com); ergo, both DNS entries would require modification with the new IP address. However, if you use the predigio private nameservers for the ffmcobalt domain, then updating one cascades to the other (since ffmcobalt points to NSx.predigio.net servers).
 
I've had trouble with nameservers and the way ultraunix sets their's up, it was pretty frustrating to have my site down for an extra day
 
Originally posted by: Nik
One of my two domains quit working this week. It's hosted on a reseller's account along with my second domain (both on same reseller's account, get it?). However, one works one doesn't. This happened before. What do I get? I get asked to change my nameservers from ns1.predigio.net to some IP.

Uh... excuse me, but wtf is the purpose of a nameserver if people are dropping IP's into the nameserver slots for their domain hosts? When that happened, the guy who heads the host said that they'd fix it on their side since I can't put IP's in place of my DNS nameservers with the company I bought that domain from. It was fixed in a few days.

What happens? My domain goes down. First thing I do is trace route the domain. No propogation. So I go back to the domain registration company and the name servers are still correct. I go back to my webhost, and what do I get?

"Hi Nik,

I have just checked with domain and found it using the wrong NS.

Please change your NS IP to:
69.90.172.57 & 207.58.130.53.

Once DNS propagated, everything should be all good."

GRR!! I DON'T CONTROL THE NAME SERVERS! YOU give ME the name servers that I drop into the nifty magic little forms with the company I registered the domain through and it magically works within three days. If you want to change the IPs that the nameservers point to, that's YOUR job! Not mine!!

*phew*

I feel better now. But it still ain't working. 🙁

this is why i do my own DNS, separate from the web host.
 
Back
Top