Forum Moderators: mack
This is the first time ever that I have this kind of host package as I just recently strated with webdesign service.
They allocated to me my own "name servers" and asked me to "register these nameservers" with my registrar (moniker.com)
I emailed moniker, and within couple of hours, I was able to change "old name servers" to my brand new ones.
I assume this means my new neame servers are registerd now?
Today, 24 hrs later, I still can not access my websites ( 4 newly uploaded sites i made for my clients, that were never before on the net)
Now I start to worry that something is wrong with my new nameservers as from my experience, changing nameserves will affect witin 5-6 hours.
Can somebody please give me some advise on this.
Thanks!
If nothing's changed after 3 days I'd contact your hosting provider to make sure they have the domains registered properly.
You should be able to diagnose this with "whois" and "traceroute" and/or "ping", and "dig". Become familiar with these tools (or equivalent on Windows).
First, use "whois" to view your whois information. This will tell you what nameservers your domain is set to use.
Then, use traceroute or ping to see if your nameservers are accessible.
Next, use "dig" to see if your nameservers are responding to DNS requests with the DNS records you have set-up.
Finally, use "traceroute" to see if your website is accessible. First, by IP address, then by name.
By using these tools, you should be able to pinpoint just where the problem is.
That said, it's almost always a mistake to use the DNS servers provided in a reseller package. MUCH better to use either the DNS provided by your registrar or a third-party DNS service. Either is likely to provide you with greater reliability and greater geographical diversity.
In most cases, reseller package DNS is hosted on your server, and doesn't even really provide the required minimum of two nameservers. In many cases, the "secondary" server is really just a second IP address on your own server.
Now, if your server goes down, and/or you have a billing dispute with your ISP, if you want to temporarily divert your site to a different server - how do you do this if your server is down?
They allocated to me my own "name servers" and asked me to "register these nameservers" with my registrar (moniker.com)
So, you started with example.com, and they set you up with ns1.example.com and ns2.example.com?
I emailed moniker, and within couple of hours, I was able to change "old name servers" to my brand new ones.
If it's like I asked above, some registrars call it "creating" name servers. It is different from changing nameservers because you need to tell everyone that ns1 and ns2 exist. (Instead of just changing namservers that a domain uses.)
Moniker usually knows what they are doing, and if you explained what was going on, then they probably steered you in the right direction. It seems to take longer for new nameservers to start working than it does for a nameserver change.
i emailed moniker yesterday. i didn't get any response from them yet (is 36 hrs long enough to wait for some kind of feedback?)
i only assume they done their part of the job.
as suggested by you, i checked whois for these domains and for 3 of them shows my new name servers except for main one www.example.co.uk (still shows old name servers)
i resend my email to moniker again and i am hoping for some kind of reasurrance as my hosting provider says they didn't yet registered (created) these new nameservers.
ps - for ping and trace i need to make reserach, as i don't know how to do this :-(
thanks again
i emailed moniker yesterday. i didn't get any response from them yet (is 36 hrs long enough to wait for some kind of feedback?)
Just pick up the phone and call them.
I registered a domain with Moniker for the first time the other day. (A .mobi, which my primary registrar doesn't handle.) There was a problem on their web site: when you selected the "mobi" check box, and went to the next page, it would select ".bz" instead.
I called them on the phone, somebody picked up IMMEDIATELY, and the problem was solved within a minute. (They gave me another page to register from, and notified their developers of the problem.)
----
ping and traceroute are fundamental tools, well worth getting to know. (In Windows, traceroute is called "tracert").
From a Windows command line:
ping 1.2.3.4 or
ping www.example.com
tracert 1.2.3.4 or
tracert www.example.com
On Linux, use "traceroute" rather than "tracert".
There are some nice graphical tools from third parties as well, both free and shareware.
Traceroute will show you the complete "path" from your PC to a server, so it can show you where the connection is "broken" if you are not getting through.
"dig" (as well as the older "nslookup") are programs for manually querying a DNS server. These don't come with Windows, but there are third-party tools available. If you have command-line access to your hosting account (presumably Linux), you can use them from there.
thanks for good suggestion - to phone!
taked to moniker (indeed, they pick up phone straigh away - no any vivaldi four season baroque music etc..)
my request is sent to their technical department and they promiss to contact me shortly.
so, no, my name serversare not yet registered (obviously) but I hope they will be soon :-)
also, thanks for ping and trace info. i only tried it minute ago, but got " Ping is not recognized as an internal or external command, operable program or batch file" . will try again, i probably done something wrong...
