rndc reload failed bad zone

Comments

• yomero Member

  August 2012

  I guess you need to post the zone.
  Obviously this two lines aren't the best way to get help.
• Shamli Member

  August 2012 edited August 2012

  haha.sure...just thought maybe there is someone may help without looking at the zone...

  here it is..

  $TTL        86400
         IN      SOA     ns1.mydomain.com. shamli.mydomain.com. (
                          2012080218       ; serial, todays date + todays serial #
                          28800              ; refresh, seconds
                          7200              ; retry, seconds
                          604800              ; expire, seconds
                          86400 )            ; minimum, seconds
  ;
  
  *.image 86400 A        184.xx.xxx.74
  billing 86400 A        184.xx.206.125
  docs 86400      CNAME        ghs.google.com.
  extplorer 86400 A        198.xxx.xxx.130
  eyeos9 86400 A        184.xx.236.231
  mydomain.com. 86400 A        198.xxx.xxx.34
  mydomain.com. 86400      MX    20   ALT1.ASPMX.L.GOOGLE.COM.
  mydomain.com. 86400      MX    20   ALT2.ASPMX.L.GOOGLE.COM.
  mydomain.com. 86400      MX    10   ASPMX.L.GOOGLE.COM.
  mydomain.com. 86400      MX    30   ASPMX2.GOOGLEMAIL.COM.
  mydomain.com. 86400      MX    30   ASPMX3.GOOGLEMAIL.COM.
  mydomain.com. 86400      MX    30   ASPMX4.GOOGLEMAIL.COM.
  mydomain.com. 86400      MX    30   ASPMX5.GOOGLEMAIL.COM.
  mydomain.com. 86400      MX    10   mail.mydomain.com.
  mydomain.com. 86400      NS        ns1.mydomain.com.
  mydomain.com. 86400      NS        ns2.mydomain.com.
  mydomain.com. 86400      NS        ns3.mydomain.com.
  image 86400 A        184.xx.xxx.74
  mail 86400      CNAME        mail.gmail.com.
  moon 86400 A        199.xxx.xxx.125
  stats 86400 A        199.xxx.xxx.47
  status 86400 A        199.xxx.xxx.47
  statuss 86400 A        199.xxx.xxx.47
  vks01 86400 A        198.xxx.xxx.34
  vp1 86400 A        184.xx.xxx.222
  vp10 86400 A        184.xx.xxx.125
  vp11 86400 A        199.xxx.xxx.88
  vp2 86400 A        184.xx.xxx.74
  vp7 86400 A        128.xxx.xxx.133
  vp8 86400 A        199.xxx.xxx.47
  vp9 86400 A        199.xxx.xxx.125
  webmail 86400 A        184.xx.xxx.125
  webmails 86400 A        184.xx.xxx.125
  
  
  

  I'm just disguising the domain and the IP for it to be posted here...
• NanoG6 Member

  August 2012

  I think error log make much sense for troubleshooting
• Shamli Member

  August 2012

  where do I find the error log.?
  seems like I cant find it.

  below is my named.conf.options

  options {
      directory "/var/cache/bind";
  
      // If there is a firewall between you and nameservers you want
      // to talk to, you may need to fix the firewall to allow multiple
      // ports to talk.  See http://www.kb.cert.org/vuls/id/800113
  
      // If your ISP provided one or more IP addresses for stable 
      // nameservers, you probably want to use them as forwarders.  
      // Uncomment the following block, and insert the addresses replacing 
      // the all-0's placeholder.
  
      // forwarders {
      //  0.0.0.0;
      // };
  
      auth-nxdomain no;    # conform to RFC1035
      listen-on-v6 { any; };
  };
  
  logging{
          channel query_logging {
                  file "/var/log/bind/bindquery.log" versions 10 size 30m;
                  severity debug 3;
                  print-time yes;
                  print-severity yes;
                  print-category yes;
          #   syslog syslog;
          };
  
          category queries {
                  query_logging;
          };
  };
  
• yomero Member

  August 2012 edited August 2012

  Your zone file seems fine for me. I haven't worked too much with DNS stuff, but maybe some dumb points due to my lack of knowdlege to try.

  The semicolon without comment is valid?
  The *.image entry is valid?

  And well, you always can try to remove stuff from the zone to see what entry is causing the error.

  Btw, the error log, well you can find some messages at /var/log/syslog (at least in Debian based distros)
• ExpertVM Member, Host Rep

  August 2012

  Can you run this command to check the zone data?

  /usr/sbin/named-checkzone mydomain.com /path/to/your/zone/file/mydomain.com.zone

  Thanked by 1NanoG6
• Shamli Member

  August 2012 edited August 2012

  found it...though it never happened before..
  so,I have updated the record,and it's solved....

  thanks guys...=)

  # /usr/sbin/named-checkzone mydomain.com /etc/bind/pri.mydomain.com
  zone mydomain.com/IN: NS 'ns1.mydomain.com' has no address records (A or AAAA)
  zone mydomain.com/IN: NS 'ns2.mydomain.com' has no address records (A or AAAA)
  zone mydomain.com/IN: NS 'ns3.mydomain.com' has no address records (A or AAAA)
  zone mydomain.com/IN: not loaded due to errors.
  

  @Yomero
  those are valid before...perhaps after I dist-upgrade recently that caused this....
• yomero Member

  August 2012

  Oh, I forggot that command
  +1 to ExpertVM