Can I do this?

[jakob]

I had many domain pointers to setup so instead of adding them one-by-one into DA, I tried this: created an appropriate domain.com.db for each domain and inserted them all into /var/named/. I then added the entries to /etc/named.conf.

The domains and proper dns files showed up on DirectAdmin but the domains won't go live.

My logs show that I don't have a name.ca file. Where does this go and what should it contain?

Any expertise in binding or my missing step/s would be appreciated. And please tell me if I can't setup the domains this way.

 

[nobaloney]

I presume you mean a named.ca file.

You shouldn't need a name.ca file if your nameserver is not running as a cacheing nameserver. You shouldn't run it as a cacheing nameserver; you should only run it as an authoritative server.

Is your server set up to be a caching nameserver? If so you should change that.

When adding files manually you need to restart the BIND daemon. Have you done that?

Jeff

 

[jakob]

Yes, the named.ca. I am not sure what nameserver I have setup, but I want the authoritative.

I rebooted the server and have tried to restart named using: service named restart but am getting Failed/Failed. Because I did this, all my domains are now down.

Here is what my named.conf file looks like now:

// generated by named-bootconf.pl

options {
        directory "/var/named";
        /*
         * 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;

	allow-transfer { none; };
};

//
// a caching only nameserver config
//
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
        type hint;
        file "named.ca";
};

zone "localhost" IN {
        type master;
       file "localhost.zone";
        allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "named.local";
        allow-update { none; };
};

include "/etc/rndc.key";

zone "domain.us" { type master; file "/var/named/domain.us.db"; };

 

[jakob]

Thanks for your insight.

I did some research and got rid of the "Failed" messages & restarted the named by doing this:
The "named.ca" file wasn't found so I downloaded the list of "root servers" from Internic, at
wget ftp://ftp.internic.net/domain/named.root.
I put it in the /var/named/ directory and edited /etc/named.conf file to use /var/named/named.root as the "hints" file for the "." zone.

 

[floyd]

Of you could have just removed from named.conf since you don't need or want it anyway:

zone "." IN {
        type hint;
        file "named.ca";
};

 

[nobaloney]

Floyd, since we don't know if he's using his local nameserver as a cacheing server or not, we really don't know if that would work. To know that we'd have to know his IP#, and the contents of his /etc/resolv.conf file, and then we could test.

Jeff

 

[floyd]

You shouldn't run it as a cacheing nameserver; you should only run it as an authoritative server.

I want the authoritative

The way he answered you he made it sound like he did not care about having caching.