Hi there i recently got some Reseller hosting (cPanel/WHM) and got a 2-Year domain through 123-reg. The Domain is http://www.orangemanta.co.uk , so when i got the domain I changed the name servers to the servers the reseller account was on (ns1.calhosting.org and ns2) and all was hunky dory until today whilst installing a blog everything some what died ... It went really slow at first and now is not working at all.

123-Reg's status page says everything is okay WHOIS client says the name servers are correct and my reseller account is still active as i can access it via the IP address.

I've tried reinstating the name servers but to no avail what so ever. I get:


Server not found

Firefox can't find the server at orangemanta.co.uk.




So with the domain okay, name servers correctly changed and the hosting working what could be causing this?

Also when it was working i couldn't get the e-mail to set-up right either ... and the default address was my domain, not what im used to which is a default e-mail address. I have had hosting before but through companies who did it all for you including Hostgator, but im having real issues now.

If anyone could help it would gratefully appreciated as i have hosting accounts needing sub-domains and Design Customers wanting to see there starting work.

Let me know.



Thanks a lot,

Luke.

these are the warnings i get on your domain name



WARNING. The parent servers (I checked with ns4.nic.uk.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.


A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).

Hi there thanks very much for that, but i dont quite understand some of it.

I'm getting the fact the name servers are stated to be down/un-reachable, but the name servers im using are the ones provided by the master account seller. So should i ask for .co.uk name servers to be created? I'm due my own name servers but im still awaiting them from the seller.

It's just the fact it was working up until about 1:00pm (GMT), then stopped.

A little noob'like explanation would be more usefull ... Sorry about this.

Thanks,

Luke.

How long has the site been down?

It could be due to DNS circulating the net.

for nearly 12 hours now

It can take 24-48 to circulate the web.