On 28th May at 00:00 GMT exactly, I changed my nameservers.
Till date, all records are showing the old nameservers. Has it been over 72 hours yet?

Anyway, I've a ticket open with NameCheap where staff told me to do one thing, the other told me to do the other.
It has been over 24 hours since I last communicated with staff via the ticket and approaching live support (1st Support Level) didn't achieve much.

This has caused me downtime - but worse - loss in revenue and lack of money to pay for the server :(

What do you think I should do?

The domain in a .uk domain: www.thinkteen.co.uk (http://www.thinkteen.co.uk)

Thanks.

Please stop talking about loss in revenue. If you change nameservers and don't plan it properly (did you reduced the TTL a few days back?) and don't point the old nameservers to the new server it's mainly your fault.
Propagation takes it's time, noone can predict how long exactly.

Also you point the domain now on one server where also the nameservers are. If the server goes down, everything is down. Don't cry then again about loss in revenue. Where there is no redundancy there is downtime.

I can't reach your site. Are your correct nameservers and IP's showing in your Namecheap control panel and in the WHOIS?
Is ns1.thinkteen.co.uk a real or "virtual" nameserver? If the later have you set up the host records in your namecheap control panel? I suspect that something is not set up properly in your webhosting or namecheap control panel - possibly the IP's or host records. There should have been no reason to change your A, cname or mx records.

hi, the correct name servers are showing up in namecheap control panel but whois shows the incorrect IP for the nameservers. The technicians at Virpus checked WHM and it was fine. Namecheap tells me the info in control panel is correct

what did you mean by a virtual nameservers?

deff. something not set up right [UK nameservers are a little peculiar nowdays]
but check HERE (http://internetsupervision.com/scripts/urlcheck/check.aspx?lan=en-US&checkurl=thinkteen.co.uk&email=%3CEnter+Your+Email+Address%3E) it's simply not resolving.

I've asked Virpus to confirm the nameserver settings I should have. I am still awaiting feedback from namecheap.

Guess what, NC are trying to blame the problem on my server OR they are not reading my posts properly. I am talking about the DNS propagation - not the fact that the old IPs don't resolve :(

Guess what, NC are trying to blame the problem on my server OR they are not reading my posts properly. I am talking about the DNS propagation - not the fact that the old IPs don't resolve :(
not asking to give them out here, but do the new IPs resolve ?

They do perfectly, I can PM them to anyone who needs them :)

I'm not familiar with name cheap's control panel,
does anybody know if it is the same as enom's for creating name servers ?

I'm not familiar with name cheap's control panel,
does anybody know if it is the same as enom's for creating name servers ?

It is quite similar - however, you have to enter the nameserver and IP details manually.

It is quite similar - however, you have to enter the nameserver and IP details manually.
Not wishing to be rude, but
is it worth 'rechecking' that youve not made any typos ?

I have checked it lol - what I've done now is that, with my domain, ngwebservers.net, I have registered nameservers with the same IPs of the ones I had for ThinkTeen.co.uk. These new nameservers are my nameservers for the domain.

It should work, and will tell me roughly where the problem lies.

I'd like to announce that ThinkTeen.co.uk is now online! What I did worked!