#3789 Can not properly cache zones info for large named.conf

1.520
open
5
2010-10-29
2010-10-29
No

OS: Centos 5.5.
webmin :1.520

While caching zones info from named.conf bind8 module misses about 200 zones.

[root@ns bind8]# wc zone-names
2902 14279 207264 zone-names
[root@ns bind8]# grep zone /etc/named.conf | wc
3158 12749 110003

Thus search can not find new added zones and potentially breaks named.conf because it allows to add multiple zone definitions to named.conf.
I have a suggestion : create 2 different cache files - one for master zones another one - for slave zones to work around possible limitation.

Discussion

  • Jamie Cameron

    Jamie Cameron - 2010-10-30

    You should check your named.conf file for any syntax errors, like a missing ; or } .

    Sometimes Webmin stops parsing named.conf when it runs into an error like this, even if BIND is capable of parsing past it. If you can work out the last domain that appears in Webmin's list, the error is probably around there..

     
  • Anonymous

    Anonymous - 2010-10-30

    I'm sorry, but this this live primary ns for the company - it does not have any syntax errors - since webmin failed after every change it been checked manually with named-checkconf.
    On another server I have similar problem - all zones are cached but I can add same slave zone 2 times with webmin and it doesn't catch it.
    We've had that many zones for years and webmin was working properly the problem started 7 days ago.

     
  • Jamie Cameron

    Jamie Cameron - 2010-10-30

    If you compare the zones in named.conf and those in zone-names , can you work out which ones are missing? It would be useful to figure out where in named.conf Webmin stops parsing.

    The cause may be some options in named.conf that Webmin is unable to parse.

     
  • Anonymous

    Anonymous - 2011-02-03

    Actually I found the reason for this when situation became unbearable - on master server webmin cache was missing about 650 zones.
    I did some named.conf formatting and it didn't help at all.
    What resolved the problem is switchign zone file path to relative in module config and forcing all zone file path in named.conf to relative.
    Am I right in the assumption that webmin takes zone file path configuration (absolute/relative) from module configuration not from actual named.conf?
    Also some "genius" managed to create "*.somestupidcomain.com" virtual host via virtualmin on some dedicated server and it blindly created slave zone record on master dns server.
    I hope this information will help.

     

Log in to post a comment.