n00b nameserver questions Options

[alpeb]

Hi,

I'm trying to configure a domain name I've got with the planet, that should point to a server I've got elsewhere. The server runs a nameserver, and has the zone file for my domain name.
On the other hand, I can see in orbit I that the domain name has also zone file, with the A records pointing correctly to the server IP, but the NS entries pointing to ns1.theplanet.com and ns2.theplanet.com. Should I put there my nameservers domains instead? Or, if I already have a zone file for my domain in the planet, does it mean I don't need to run my own nameserver?

Also, there's another section under orbit where I can edit the nameservers for my domain. Since there is already a zone file, can I ignore that section, or should I enter my nameservers there as well?

Thanks in advance.

[Jeff]

The main thing is to decide whether you want to run your own nameservers in the long run or whether you want to use the planet's nameservers. If you decide to run your own nameservers, then you just need to point the domain to ns1.yourdomain.com and ns2.yourdomain.com. If you decide instead to use the planet's nameservers, then you enter the appropriate a records to point yourodmain.com and www.yourdomain.com to the ip where apache is setup and the mx record for mail, etc.

If you have more than one server and run a control panel, I'd choose to run my own dns. On one hand it's one more service that you have to montior, update, and run, but on the other hand it makes it a lot easier to add new sites, subdomain, etc. on the fly and makes it easier in the future should you want to change servers, providers, etc. to have everything pointing to dns servers you control.

If you only have one server, I'd use the planet's nameserver cluster. While it's been stated that "Technically the DNS servers are considered as value added services and aren't covered by the SLA" like the servers, network, or power systems, you can expect the cluster would be more reliable than a single server which would have no redundancy (causing problems if you rebooted it for example where mail would fail instead of being queued up.)

[jpgauvin]

I'm now the administrator of 3 servers under The Planet

And I'm also a n00b with DNS

I'm trying to figure out how to fix some issue with the DNS setting on those servers

they each host several websites, some with .com and some with .ca

I would like to know why the person I'm replacing used ns1.theplanet.host as a name server ?
Why did he used ns1 and ns2 on the same ip address? I think it's a bit pointless

Does somebody can show me a good way to setup a DNS and a Nameserver

Thanks

[theuruguayan]

You most likely need to check which nameservers are actualy being used in the domain name.

He most likely used theplanet dns servers since the ns1.theplanet.host is not a valid nameserver name.

[Tomy Durden]

I'm now the administrator of 3 servers under The Planet

And I'm also a n00b with DNS

I'm trying to figure out how to fix some issue with the DNS setting on those servers

they each host several websites, some with .com and some with .ca

I would like to know why the person I'm replacing used ns1.theplanet.host as a name server ?
Why did he used ns1 and ns2 on the same ip address? I think it's a bit pointless

Does somebody can show me a good way to setup a DNS and a Nameserver

Thanks

Chances are, when the server was originally ordered they requested the hostname of ns1 and ns2 but didn't specify a domain name. Our provisioning systems append 'theplanet.host' on the end to keep certain packages from complaining about using a non-FQDN(Fully Qualified Domain Name). If you look in /etc/hosts this will be defined there as well.2

Depending on how familiar you are with the various configuration files involved, you could define a real FQDN and then change all instances of ns1.theplanet.host. Be advised that things can get a bit broken when changing config files.

[jpgauvin]

Thank you for the answers

@theuruguayan the server point to ns1.theplanet.com and ns2.theplanet.com witch make me wondering how's the server still running

@Tomy Durden so ns1.theplanet.host is only pointing to the server IP itselft ?

Another thing I found odd, it's that the mail entry seem to be right with CNAME but work only half the time with a .ca address but work fine with a .com address.

Is it because we use opensrs.net for .ca and mydomain.com for .com addresses ?

thank

JP

[theuruguayan]

They are still running because they are using the nameserver/dns provided by theplanet. The one you configure from the orbit protal.

[niknok]

hi,
i'm also having trouble setting up my dns nameservers..Does DNS have a tool to check if my dns configurations are correct? is it essential to open port 53 for the DNS nameservers to work? Thanks. any response is greatly appreciated.

[Gary Simat]

hi,
i'm also having trouble setting up my dns nameservers..Does DNS have a tool to check if my dns configurations are correct? is it essential to open port 53 for the DNS nameservers to work? Thanks. any response is greatly appreciated.

dnsstuff.com is a good tool to check your DNS zone.

Yes port 53 must be open if you run DNS locally.

[niknok]

dnsstuff.com is a good tool to check your DNS zone.

Yes port 53 must be open if you run DNS locally.

thanks for the response. what do you mean by running DNS locally? does it mean local intranet settings? thanks again..

[Jeff]

The port must be open if you are running a dns server on the server in question so the DNS server can be reached by the outside world.