Dns & Ispconfig

Discussion in 'Installation/Configuration' started by captnops, Jan 18, 2008.

  1. captnops

    captnops New Member

    I am working on setting up my BIND server, and was having some trouble. I can get to my sites for domain http:// ww.justoutboards.com, but I cannot send mail to that domain from the server.

    Perfect ubuntu 7.10 server w/ispconfig.

    Do I do all the DNS administration from within ispconfig, or do I still do all DNS work through bind?

    Thank you
  2. zetnsh

    zetnsh New Member

    I recently found that for some reason I had to create the file /var/named/chroot/etc/named.conf because ISPConfig didn't create it during setup (which it ought to have done I think!)

    For ref, I just put this data in it:

    options {
            pid-file "/var/named/chroot/var/run/named/named.pid";
            directory "/var/named/chroot/var/named";
            auth-nxdomain no;
             * If there is a firewall between you and nameservers you want
             * to talk to, you might need to uncomment the query-source
             * directive below.  Previous versions of BIND always asked
             * questions using port 53, but BIND 8.1 uses an unprivileged
             * port by default.
            // query-source address * port 53;
    // a caching only nameserver config
    zone "." {
            type hint;
            file "named.ca";
    zone "0.0.127.in-addr.arpa" {
            type master;
            file "named.local";
    Then restart bind:
    /etc/init.d/named restart
    I found I could then manage DNS zones entirely within ISPConfig, although by default it doesn't create the MX record for you, which is necessary for your server to receive mail for the domain in question.

    To do that, you simply need to create a new MX record from within the DNS entry page for that domain/zone within ISPConfig. Leave Hostname blank, leave the Priority at 10 (if you have several MX records, the lowest priority hosts receive mail first), then put the internet name of your server in the Mailserver box.

    To test it, run this command as root from the box in question, replacing mydomain.com with your domain of course...

    dig @localhost mx mydomain.com
    Hope that helps somewhat,


Share This Page