Installing PowerDNS (With MySQL Backend) And Poweradmin On Fedora 12 - Page 2
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 22.214.171.124 to server1.example.com, create a record under List zones and fill in 126.96.36.199 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
for more details), e.g. as follows:
dig @localhost mx example.com
[root@server1 ~]# dig @localhost mx example.com