[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 541
  • Last Modified:

Named.conf Include Limitations?

Hi All,

I am running DirectAdmin Web Console and I have about 20,000 sub-domains all linking off of the same site. (using Apache virtual hosts)

The short of the story is that I backed up all of our data (19,000) accounts and with sub-domains off of the name aisites.com domain.

All of these domains are linked in etc/named.conf as includes and the public URLs are resolving properly. The problem is - now that I have those in, and I add new users (adding another include line in named.conf) it won't resolve those new sub domains.

After each user is added I am restarting HTTPD, NAMED, etc and they are both restarting properly, with no errors in /var/log and no errors doing a CONFIGTEST.

Once reloaded - I can ping the sites, ie subdomain.aisites.com locally on the box and it resolves but for some reason the public URL is not resolving and by doing an NSLOOKUP from an external computer it won't resolve there either.

Anyone have any ideas what might be causing this? Is there a file size limitation I need to change?

I am running CENTOS 5.2, BIND 9, Apache 2,0

Edit here is a snippet of my Named.conf file - which is working, except for the newly added includes...
// 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; };
        allow-recursion { localnets; };

// a caching only nameserver config
controls {
        inet 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 "aisites.com" { type master; file "/var/named/aisites.com.db"; };
zone "argosysites.com" { type master; file "/var/named/argosysites.com.db"; };
zone "xx.xx.xxx.xxx.in-addr.arpa" { type master; file "/var/named/xx.xx.xxx.xxx.in-addr.arpa.db"; };
zone "aa061.aisites.com" { type master; file "/var/named/aa061.aisites.com.db"; };
zone "aa0641.aisites.com" { type master; file "/var/named/aa0641.aisites.com.db"; };
zone "aa09114.aisites.com" { type master; file "/var/named/aa09114.aisites.com.db"; };

Open in new window

1 Solution
http://www.checkdns.net/quickcheck.aspx?domain=aisites.com&detailed=1 shows a couple of minor problems, but you aisites.com zone is resolving externally just fine.

http://www.checkdns.net/quickcheck.aspx?domain=aa061.aisites.com&detailed=1 also shows some minor things, but resolves from outside.

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now