Web Hosting Talk







View Full Version : DNS setup with Managed.com


kyriakos
04-24-2004, 06:41 AM
cpanel's recommendation is that I don't enable the nameserver service cause it will cause a major slow down. anyone who has done the setup on a managed.com server can guide me through the procedure?

I've set the primary and secondary dns servers at the Initial Server Setup in CPanel and I thought thats all I needed but after adding an account and pointing a domain to it it fails to resolve even after 12 hours (the dns changes did propagade cause I can't resolve it to the old server any longer).

Both directnic and ev1servers say they fail to verify the existence of the DNS servers.


I'd appreciate any help.

michaelfoo
04-24-2004, 08:16 AM
Hello,
Just wondering, are the IPs binded to your server?

kyriakos
04-24-2004, 12:39 PM
I've enabled the DNS service from CPanel, now the server's ip got accepted with the registrar's as a DNS server. Locally from the SSH session I can do an nslookup on the domain and it resolves as it should but still nothing from anywhere else (might just be the time it needs to propagade - OR I did something wrong).

athlonkmf
04-24-2004, 02:00 PM
makes me wondering. why would you want to run your own nameserver?

I've simply use an account at zoneedit.com or another free nameserver. Because IF I decide to move to another server, my sites don't have to be offline for at 24 hours before the registrars has got the newest info worked out.

I can change servers in a few minutes now.

michaelfoo
04-24-2004, 08:16 PM
I've enabled the DNS service from CPanel, now the server's ip got accepted with the registrar's as a DNS server. Locally from the SSH session I can do an nslookup on the domain and it resolves as it should but still nothing from anywhere else (might just be the time it needs to propagade - OR I did something wrong).


Do you know IPs must be binded to the IP field plus add the nameservers to the bind servers before it can be used?

Try entering the IPs in your browser and see if you are being redirected to the server. If not, you should consider adding the IPs to the IP field ;)

Thanks.

mainarea
04-24-2004, 10:25 PM
cpanel's recommendation is that I don't enable the nameserver service cause it will cause a major slow down.
That's not what it says. It says "We recommend you do not enable the nameserver unless you are going to use it. If you wish to disable the nameserver you can always turn it off in the Service Manager". There is no reason to run it if you're not going to use it, but if you want it, go ahead. I never saw any slowdowns on it with my Dual Xeon machines or my first Celeron 500Mhz machine.

- Matt

lintbox
04-25-2004, 01:30 AM
If you enable the nameservers feature in cpanel, is there anything special that needs to be done? I'll be in this same situation beginning of next month when I get my server,and was curious as to the nameserver setup..

kyriakos
04-25-2004, 08:11 AM
lintbox - since I enabled it I didn't have to do anything other than simply pointing the domain from the registrar to the server's ip address.

mainarea - thanks I'll use that and zoneedit as a backup since its free

KKHost.Net - are you referring to the additional ip's?

michaelfoo
04-25-2004, 09:00 AM
KKHost.Net - are you referring to the additional ip's?


Yes, I'm referring to the additional IPs. The reason why I asked this question is because I faced such problem with a customer who bought additional IPs from us after buying the server. Therefore, we were unable to add the IPs for him and asked him to do it himself. He added the IPs in the NS but not IP field and complained that the IPs were not working.


ps: Since you are using cPanel, click "Show IP Addresses" and see if the IPs are listed there?

kyriakos
04-25-2004, 09:17 AM
I can see the 3 ip's I've added yes. (I added them while playing around).

What do you think about the idea of using zonedit's dns and the server's own dns service as backup?

deseek
04-25-2004, 10:21 AM
anyone feel free to correct me if i made a mistake

Ive never used cpanel or anything but i can give you a rough idea....
i dont know what you used for nameservers but in order for domains to resolve to your server you have to be running your own dns server(bind). after you get bind installed and running then you would want to take a look at /etc/network/interfaces
and make sure your server is setup to use at least 2 ip addresses. then go to your registrar where your domain is registered and add domain hosts to your domain pointing to the two ip's. it would be in the "domain host summary" area in godaddy. also point your domain to those 2 host servers. after that, u setup all the info in the control panel.
if you need more in depth info maybe ill try to write a howto or something.oh also make sure there is an address record for www so www.yourdomain.com gets mapped to your ip instead of just yourdomain.com

TheTrance
04-25-2004, 11:18 AM
Originally posted by derf9o9
after you get bind installed and running then you would want to take a look at /etc/network/interfaces



you are correct, only for Linuxes though i believe.

deseek
04-25-2004, 11:44 AM
i was assuming he was using linux since managed.com only offers cpanel with linux.

kyriakos
04-26-2004, 01:08 AM
yes it is a linux server. my question here is.. whats the point of having 2 "DNS" servers since they both point to the same machine even though on a different IP? isn't redundancy the whole point of having multiple DNS servers assigned to a domain?

BoA
04-26-2004, 01:16 AM
^The point of having two nameservers is because you cannot register a domain without two.

kyriakos
04-26-2004, 01:18 AM
thats not the reason though thats a consequence

deseek
04-26-2004, 05:03 PM
well you would want redundancy but at the same time you only have 1 server :-)
the whole point of using 2 ip addresses pointing to 1 server is because registrars require 2 different domain servers in order to point a domain to a server. but if you only have 1 machine thats how u would work around it.

wouldnt make much of a difference though if you just have that 1 server anyways seeing as how if that server went down, you wouldnt be able to access the websites on it either way.
if you have another server though, then just run bind on each server and instead of 2 ips for 1 server you just setup 1 ip for each server.