Hi linux folks, I want to host some php-mysql websites. I figure that a LAMP server will be a great choice.

I've researched into the procedure and it looks easy enough at first: register mydomain.com. Point mydomain.com to ns1.mydomain.com and ns2.mydomain.com. Install linux on server with 2 static IP addresses. Setting up the appropriate software doesn't look too hard either: just install apache, php5, mysql.

Then comes the hard part: how to make your linux box mydomain.com. So I googled around and realized that you need to configure a name server/DNS/BIND9. http://www.yolinux.com/TUTORIALS/Lin...onfig.html#DNS
But at the end of the day, I got totally confused by things like the master server, slave server, and nodes, and zones.

I only have one domain and I just need to host a simple php-mysql server. Do I really need a slave? What is a slave? nodes and zones? help!

LAMP servers are supposed to be really popular. Anyone here with experience want to help me out here? I'd really appreciate it.

-------
My favorite websites:
Buy and sell class notes, old exams, papers, lab reports, admission essays.
Ask and answer Linux questions.
Read free books without walking to the library.

You don't necessarily need to setup the secondary name server as a slave. You can in fact setup two master servers. The slave just makes it easier to keep your updates intact. Say for instance with Bind, if you update the master with DNS changes, the slave will pick up those changes, no need to edit on both servers.

Now in the case if you just setup two master servers, everytime you need to update some DNS changes, you have to edit both name servers.

I may not understand entirely, but if the 2 static IP's is for the purpose of running the two nameservers I wouldn't go that route. It is highly recommended that at the very least the 2 name servers are running on seperate servers in the event that one of the servers goes down.

Thanks. This is what I understand from what you guys said: Master is the primary name server: ns1.mydomain.com. Slave is the secondary name server: ns2.mydomain.com. The slave tries to synchronize with the master and also act as a backup. Both are physically different servers on different computers.

In this case, I think name servers are way too complicated to maintain, and my best course of action is to rent professional name servers like easyDNS.

Even with easydns, I still need to configure the bind9 in my linux box to point at the easydns name servers, right?

-------
My favorite websites:
Buy and sell class notes, old exams, papers, lab reports, admission essays.
Ask and answer Linux questions.
Read free books without walking to the library.

You trivially configure your *resolver* (via /etc/resolv.conf) to query your chosen DNS server.

Consider setting up a simple caching DNS server on your system to reduce the number of external queries.

tks for the tip. I'll look out for resolv.conf when my server is ready.

-------
My favorite websites:
Buy and sell class notes, old exams, papers, lab reports, admission essays.
Ask and answer Linux questions.
Read free books without walking to the library.

I agree with Mr. C

Setting up a caching DNS server is the easiest way to go...

But if you are unsure about DNS servers (and I know it can be daunting); and want it to "just work"; then I would recommend something like easyDNS...

-C

Ok. I am completely new to linux and attempting to manager bind9 DNS for corporate. I have a external DNS mydomain.com and have several zones within that domain. The zone im particularly having problems with is staging.mydomain.com.

At times most sites resolve and can be access. Other times these same sites cannot be accessed or resolved via ping. What can possibly cause this. The sites that do not work tend to come back up eventually, give or take 15-30 minutes.

Pls advise.

You are confusing name resolution with the ability to send/receive ICMP packets to and from a host. Focus on one or the other.

If you are trying to diagnose network connectivity, ping an IP address to remove DNS from the equation.

If you are trying to diagnose DNS hostname to IP translation, ping is the wrong tool - use dig, host, or nslookup.

Why bother with a slave? The user's need seems simple, just backup your conf files...Especially the zone files.

Also DNS takes time to replicate, sometimes between 30 minutes to 3 hours. Be patient if you make a change, and don't forget to update the serial numbers everytime you make a change in the zone files.


Might help:

http://orangespike.ca/?q=node/53