From a support ticket I just wrote:
Hello, I first reported this issue via chat at 10AM Pacific on July 4. I
was told repeatedly it had been solved, but it has not, and my website is
still inaccessable.
<Domain.com> is pointing to a server belonging to <competing web hosting
company>. It should be pointing to <server>. It appears that the DNS
change that was made this morning has still not been picked up by the DDNS
system.
If you do not solve this problem soon, I will simply sign up for an account
with <competing web hosting company>. :-)
Full Version: I should be pissed, but this is just funny
On Tue, 05 Jul 2005 06:31:00 GMT, HC wrote:
| QUOTE |
| From a support ticket I just wrote: Hello, I first reported this issue via chat at 10AM Pacific on July 4. I was told repeatedly it had been solved, but it has not, and my website is still inaccessable. <Domain.com> is pointing to a server belonging to <competing web hosting company>. It should be pointing to <server>. It appears that the DNS change that was made this morning has still not been picked up by the DDNS system. If you do not solve this problem soon, I will simply sign up for an account with <competing web hosting company>. :-) |
You'll still have the 'up to 48 hours' for the new DNS to propagate
though.
--
Regards - Rodney Pont
The from address exists but is mostly dumped,
please send any emails to the address below
e-mail ngpsm4 (at) infohitsystems (dot) ltd (dot) uk
HC wrote:
| QUOTE |
| From a support ticket I just wrote: Hello, I first reported this issue via chat at 10AM Pacific on July 4. I was told repeatedly it had been solved, but it has not, and my website is still inaccessable. <Domain.com> is pointing to a server belonging to <competing web hosting company>. It should be pointing to <server>. It appears that the DNS change that was made this morning has still not been picked up by the DDNS system. If you do not solve this problem soon, I will simply sign up for an account with <competing web hosting company>. :-) Hey Mate, |
Sounds like a plan to me
Boy
In article <EOpye.107761$9A2.26684@edtnps89>, [Email Removed]
says...
says...
| QUOTE |
| From a support ticket I just wrote: Hello, I first reported this issue via chat at 10AM Pacific on July 4. I was told repeatedly it had been solved, but it has not, and my website is still inaccessable. <Domain.com> is pointing to a server belonging to <competing web hosting company>. It should be pointing to <server>. It appears that the DNS change that was made this morning has still not been picked up by the DDNS system. If you do not solve this problem soon, I will simply sign up for an account with <competing web hosting company>. :-) It takes anywhere from 1 - 72 hours for it to propagate across all the |
name servers. You need to learn some patience, or at least do your
homework before assuming it's the host's problem.
"saz" <[Email Removed]> wrote
| QUOTE |
| It takes anywhere from 1 - 72 hours for it to propagate across all the name servers. You need to learn some patience, or at least do your homework before assuming it's the host's problem. |
Actually, the web host has informed me that they're having problems with
their DDNS system. If I do an nslookup on my domain's name servers, it
shows the wrong IP, so there's nothing TO propagate yet.
"Rodney Pont" <[Email Removed]> wrote
| QUOTE |
| You'll still have the 'up to 48 hours' for the new DNS to propagate though. |
Actually, I was going to get an account at the company where the domain name
is currently pointing. :-)
"HC" <[Email Removed]> wrote in
news:EOpye.107761$9A2.26684@edtnps89:
news:EOpye.107761$9A2.26684@edtnps89:
| QUOTE |
| From a support ticket I just wrote: Hello, I first reported this issue via chat at 10AM Pacific on July 4. I was told repeatedly it had been solved, but it has not, and my website is still inaccessable. <Domain.com> is pointing to a server belonging to <competing web hosting company>. It should be pointing to <server>. It appears that the DNS change that was made this morning has still not been picked up by the DDNS system. If you do not solve this problem soon, I will simply sign up for an account with <competing web hosting company>. :-) |
The way its written it sounds like the person might have fallen prey to one
of those emails that say "your domain is about to expire, please renew
here" and switches them. Ive seen some very strange attangments occur that
way. Some which made no sense at all for anyone involved.
Gandalf Parker
| QUOTE |
| "HC" <[Email Removed]> wrote in news:EOpye.107761$9A2.26684@edtnps89: From a support ticket I just wrote: Hello, I first reported this issue via chat at 10AM Pacific on July 4. I was told repeatedly it had been solved, but it has not, and my website is still inaccessable. <Domain.com> is pointing to a server belonging to <competing web hosting company>. It should be pointing to <server>. It appears that the DNS change that was made this morning has still not been picked up by the DDNS system. If you do not solve this problem soon, I will simply sign up for an account with <competing web hosting company>. :-) The way its written it sounds like the person might have fallen prey to one of those emails that say "your domain is about to expire, please renew here" and switches them. Ive seen some very strange attangments occur that way. Some which made no sense at all for anyone involved. |
Never mind. I think I read your post wrong. You are the customer not the
service? I tend to be on the service side so I read it like many of those
Ive seen
Gandalf Parker
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.