I've had my own webpage and domain name since February of last year. The website itself recieves about 1-2 gigs of traffic per month. I added a php board to my site last year, and hosted it with a different hosting company than my domain name is on, and linked it from my webpage.

Now, my domain name host changed their plan and only allowed 1 gig of transfer per month. So in the month of December, I was over that about a week before the end of the month, so my site was shut down for being over the bandwidth allowance.

Well, the host that hosts my php board allows more bandwidth (10 gigs per month) so I figured I would move the domain name to that host and then upload all my webpage files to that server. So, my board was using about 6 gigs per month, so I figured I would add my website too it (1-2 gigs per month) and I would be fine since it would fit under the 10 gigs. So I moved the name to the new host a couple days before January 1st.

We are now 2 weeks into the month of January, and my website was just shut down again for using too much bandwidth for the month. Only 2 weeks into the month! But the wierd thing is, my php board still works, just no pages using my domain name ( I use the IP number for my forums). I went back to the old host where my domain name used to be, and signed into the control panel. It says I've used about 2.5 megs so far this month. Now, my question is, shouldnt there be NO traffic on that host since I moved the name and files to the new host? I checked it for the first couple days after I moved the name, and it looked like there was NO traffic being used. Now I come back 2 weeks later and it says I've used 2.5 gigs! What is going on here? Did I do something wrong during the domain transfer? Why is my old host still recording traffic, and has control over my website? I am kinda new to all this, so maybe I'm missing something. Please, any and all help is GREATLY appreciated! :( I can't have my site down for 2 weeks!

I was reading somewhere that when you transfer your domain to a new host, it takes a while for machines to recognize the new host, and people actually may still be getting your site from the old host? Does this make any sense?

Yes, it could take up to 3 days for the domain to propogate completely. Also, was this name based or IP based hosting? Is it possible that people are/were hitting the domain via IP?

-Dan

Oh it's been longer than 3 days, it's been about 2 weeks. Im not sure what you mean by name based or IP based. I have a domain name for my website which is how people access the website, but then I have a link to the forums which I use the IP for (ex. 216.321.116.132/phpforums.php). I just don't understand why my old host is still reporting traffic for the month of January when I moved the domain to the new host on December 27th. Like I said, my forums still work, but no pages with my domain name on them work. And I'm obviosly not over the limit because my forums would not work. But I am over the limit at my OLD host and thats why my webpages dont work. But I'm not even hosting with them anymore! :(

Name based hosting means that you share an IP address (most common form of hosting) IP based hosting, means that you have your own IP address, and you can reasch your site from it. Assuming the transfer was completed, and propagatoin happened before the end of the month, you should not have had anywhere near 2.5g, even if the site was accessable via IP. Do you have access to your raw logfiles? If you do, I'd definately get ahold of them, and run them through an analyzer before accepting the charges from your old host.

-Dan

Sounds to me like possibly your host denied the transfer.

Why not just cancel that account. Then everything will run through the 10 gig account. Have you done a who is lookup to see if your domain is on the right name servers?

shibby -- if you tell us your domain, we might be able to tell you where traffic is being directed.

I have previously had new customers who experienced both hosting and email problems because the old host never closed the zone.

This shouldn't be an issue if the DNS was setup properly on the new host, the registry name servers were updated, and it has fully propagated. When someone goes to yourdomain.com, the only way that the DNS gets resolved, is by the nameservers that the domain has set in it's registry. From there it pulls the zone file from whomever it was told to get it from.

-Dan

Are you getting hits on the non forum pages on the new account? That would tell you if your account is truly transferred.

Yes I did do a whois, and it says it is on the new server. My domain is Bluetraxx.com. I really don't understand this, the site never even ever reached NEAR 2.7 gigs in 2 weeks! The forums use alot of bandwidth (about 6-7 gigs a month), but not the webpages. I have no idea how to get it back up, and I can't have it down for 2 weeks. :(

I don't quite follow here. If you transferred all of the data, and the domain name to the "new" host, how is your site down?

-Dan

Originally posted by serve-you
I don't quite follow here. If you transferred all of the data, and the domain name to the "new" host, how is your site down?

-Dan

That's what I'm trying to figure out. Also, I'm an idiot...I jsut checked the stats again on the OLD host, and it is 2.7 MBs, not GBs. But still, why are my www.bluetraxx.com pages down, but my forum pages are still working fine? If I go to my forums like this... http://216.118.123.112/phpBB/index.php it works. If I go like this... http://www.bluetraxx.com/phpBB/index.php they don't work. Any ideas?

Is aletia the old host or new?

-Dan

Aletia is the new host, doteasy was the old one.

Hi,

If your name is not resolving to Aletia after 2 weeks then the problem is their end, most probably a glitch in their httpd.conf file. I'd write a ticket and inform then right away.

Actually, everything looks okay. Bluetraxx.com is on Aletia's name servers:

Internet Domain Registrars WHOIS Server v.1.5

Registrant:



Domain Name: BLUETRAXX.COM



Registration Date: 12-Feb-2001 21:38:04
Expiration Date: 12-Feb-2003 21:38:04

Domain servers in listed order:

NS1.ALETIA.COM 209.53.186.31
NS2.ALETIA.COM 209.53.186.32

Aletia has a zine file for the domain:

[root@test root]# dig @ns1.aletia.com bluetraxx.com axfr

; <<>> DiG 9.1.3 <<>> @ns1.aletia.com bluetraxx.com axfr
;; global options: printcmd
bluetraxx.com. 14400 IN SOA ns1.aletia.com. root.ns1.aletia.
com. 1003627569 28800 7200 3600000 86400
bluetraxx.com. 14400 IN NS ns1.aletia.com.
bluetraxx.com. 14400 IN NS ns2.aletia.com.
bluetraxx.com. 14400 IN A 216.118.123.112
bluetraxx.com. 14400 IN MX 0 bluetraxx.com.
*.bluetraxx.com. 14400 IN A 216.118.123.112
ftp.bluetraxx.com. 14400 IN CNAME bluetraxx.com.
mail.bluetraxx.com. 14400 IN CNAME bluetraxx.com.
localhost.bluetraxx.com. 14400 IN A 127.0.0.1
www.bluetraxx.com. 14400 IN CNAME bluetraxx.com.
bluetraxx.com. 14400 IN SOA ns1.aletia.com. root.ns1.aletia.
com. 1003627569 28800 7200 3600000 86400
;; Query time: 337 msec
;; SERVER: 216.118.67.98#53(ns1.aletia.com)
;; WHEN: Thu Jan 17 19:51:11 2002
;; XFR size: 12 records


and a traceroute for www.bluetraxx.com runs to pwebtech, which is where aletia's traceroutes run:

[allan@ns1 allan]$ /usr/sbin/traceroute www.bluetraxx.com
traceroute to bluetraxx.com (216.118.123.112), 30 hops max, 38 byte packets
1 f4-1-rt2.minerva.net (206.131.224.1) 0.567 ms 0.482 ms 0.418 ms
2 f0-0-rt1.minerva.net (206.131.224.193) 1.312 ms 1.204 ms 1.198 ms
3 500.Serial1-11.GW4.TCO1.ALTER.NET (65.207.88.5) 3.069 ms 3.280 ms 3.281 m
s
4 118.at-3-0-0.XR1.TCO1.ALTER.NET (152.63.39.14) 3.321 ms 3.482 ms 3.177 ms
5 193.at-1-0-0.TR1.DCA6.ALTER.NET (152.63.34.14) 5.163 ms 4.464 ms 4.460 ms
6 121.at-7-0-0.TR1.NYC9.ALTER.NET (152.63.15.206) 9.756 ms 9.922 ms 9.940 m
s
7 187.at-1-0-0.XR3.NYC4.ALTER.NET (152.63.29.5) 10.664 ms 10.773 ms 10.580
ms
8 189.ATM7-0.GW7.NYC4.ALTER.NET (152.63.25.113) 11.849 ms 10.782 ms 10.693
ms
9 internap-gw.customer.alter.net (157.130.50.86) 11.437 ms 12.748 ms 11.571
ms
10 border11.ge2-0-bbnet1.nyc.pnap.net (209.191.128.81) 11.818 ms 12.210 ms 1
1.924 ms
11 nac-1.border11.nyc.pnap.net (209.191.130.94) 11.618 ms 11.050 ms 11.495 m
s
12 a9-0-1165.msfc1.oct.nac.net (209.123.11.10) 72.677 ms 230.425 ms 243.878
ms
13 fa0-0.core1.pwebtech.com (207.99.8.198) 13.182 ms 12.220 ms 12.211 ms
14 216.118.123.112 (216.118.123.112) 15.836 ms 13.040 ms 12.685 ms

I think the mistake is with your old host...I don't see how anyone could be going to bluetraxx.com and wind up at your old host at this point.

wow...this is terrible...I have no idea what to do. :(

Have you tried to contact your old host? It would seem to me that would be the easiest resolution.

-Dan

The only way to have this corrected is to have Aletia modify the bandwidth in WHM. There is nothing to do with your old host. This is on Aletia's end, and they need to fix it.

So should I just contact Aletia and tell them to modify it? And if/when they do, will this correct the problem and bring my site back up? I also contacted the old host last night, so I'm still waiting for a reply. Thank you so much everyone for your help so far...I wasnt getting answers from anyone else.

It's Aletia for sure. How can a visitor get directed to Doteasy when the domain is on Aletia's NS?