since futurehosting, my web host provider, is odviously retarded about how to setup their own equipment, I need some help from you guys.
on a VPS, don’t I set up all domains to use the same nameservers?
like:
ns1.tcoburn.com
ns2.tcoburn.com
for all the domains on my VPS? isn’t that what I do?
because for some reason, I am not able to ping my other domain
crohnsdaily.com, am I supposed to create ns1.crohnsdaily.com ns2.crohnsdaily.com for those too? because I thought I was supposed to use the same nameservers for all domains, I am confused.
my registrar is godaddy, and I know how to change IP addresses for NS1 and NS2 in godaddy, what I am asking is, on VPS’s, don’t you use the same nameservers for each domain on the server?Do you have a control panel?
And did you setup the domain host with godaddy to use the correct ns and ips?I have cpanel.
in Godaddy.
under “TCOBURN.COM” domain,
under “Domain host summary”,
I setup
NS1.tcoburn.com to use my primary IP
I then setup
NS2.tcoburn.com to use my second IP
then under CROHNSDAILY.COM
I setup the nameservers to be:
NS1.TCOBURN.COM
NS2.TCOBURN.COM
and left “Domain Host Summary” alone
then in WHM, under the DNS stuff,
I have zones for both ns1.tcoburn.com and ns2.tcoburn.com
and under the crohnsdaily.com zone, crohnsdaily.com is pointing to ns1.tcoburn.com and ns2.tcoburn.com
so I don’t understand whats wrong with my crohnsdaily domain? why its not pinging even?
even if cpanel/WHM BIND is setup wrong, shouldn’t I at least be able to ping crohnsdaily.com? it should at least try to ping the IP right? but its not, does that mean it setup wrong at godady then?If I remember correctly, the domain host summary is the dns you will use for all your hosted domains. Once you set that up, all other domains will use that ns.
So setup your domain host nameservers, then ensure the other domains are using that nameserver info as well.Let me chime in and respond to the concerns:
1. There is a ticket on hold with this problem. To clarify for you: you can use ns1/ns2.tcoburn.com for all your domains. This is how you currently have it setup according to dnsstuff.com
2. The domain resolves and pings for us from various locations in the U.S.
3. There was a problem with one of our new OS templates (used on a few accounts) which this account was setup on that caused the VPS to crash. To fix the issue we changed the OS template and copied over his domains to a new VPS with new IPs - so there is a need to wait for DNS propagation. A flushdns on your local computer may resolve this for you sooner. The new IPs had an rDNS setup from a former SoftLayer user that was still saved on the settings when the IPs was assigned to us and the user was able to see this. Although this doesn