إله من الآله

February 2009
M	T	W	T	F	S	S
		Mar »
	1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28

27 Feb 2009 @ 8:58 AM

Installing PowerDNS (With MySQL Backend) And Poweradmin On CentOS 5.2 - Page 2

On the next screen the installer asks you to execute a MySQL query. We don’t have to do that because we’ve done something similar in chapter 3 already (the two GRANT statements) so we are set. Click on Go to step 6:

Click on Go to step 7:

The installation is now finished…

… but for security reasons we must delete the install directory:

rm -fr /var/www/html/poweradmin/install/

Now you can go to http://server1.example.com/poweradmin or http://192.168.0.100/poweradmin and log in with the username admin and the password you created during the installation:

This is how the Poweradmin web interface looks:

To create a zone, go to Add master zone and fill in the domain name (e.g. example.com). You can already fill in the IP addresses for the www A record (”webserver”) and the MX record (”mailserver”) for that zone. If you leave the Create zone without applying records-template checkbox unchecked, Poweradmin will automatically create some NS, A (e.g. www) and MX records for that zone:

Go to List zones afterwards. You should now see the new zone there, and it already has eight records. Click on the edit icon to see these eight records:

These are the records that are created automatically unless you check the Create zone without applying records-template checkbox when you create a zone. You can now edit them or add and delete records:

Of course, you can as well create all records one-by-one manually - just leave the IP address fields empty and check the Create zone without applying records-template checkbox on the Add master zone page:

On the List zones page you will see that the new zone has just one record (the SOA record). Click on the edit icon…

… and then on Add record to add further records, …

…, e.g. NS records…

… and A records (e.g. for mydomain.com (leave the Name field empty!) and www.mydomain.com)…

… and MX records:

To create PTR records, go to the Add master zone page and create a zone called in-addr.arpa (leave the IP address fields empty and check the Create zone without applying records-template checkbox):

To create a PTR record that points from the IP 1.2.3.4 to server1.example.com, create a record under List zones and fill in 4.3.2.1 in the Name field (that’s the IP in reverse order) and server1.example.com in the Content field:

After you’ve created your records, you can check them with the dig command (see

man dig

for more details), e.g. as follows:

dig @localhost mx example.com

[root@server1 ~]# dig @localhost mx example.com

; <<>> DiG 9.3.4-P1 <<>> @localhost mx example.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46586
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;example.com. IN MX

;; ANSWER SECTION:
example.com. 86400 IN MX 10 mail.example.com.

;; ADDITIONAL SECTION:
mail.example.com. 86400 IN A 1.2.3.4

;; Query time: 44 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jan 15 18:54:35 2009
;; MSG SIZE rcvd: 66

[root@server1 ~]#