domain still in DB even after emptying Recycle Bin(s)

I have one domain on my server that is causing a lot of problems for some reason!

After adding it (with Create DNS on), Bind stops working with the following error in syslog:

Code:

/etc/bind/named.conf:40 zone '0.0.127.in-add.arpa': already exists

Looking at line 40 in named.conf I see this (note that I have added // line 40 in this post)

Code:

//
// a caching only nameserver config
//
zone "." {
        type hint;
        file "db.root";
};

zone "0.0.127.in-addr.arpa" {
        type master;
        file "db.local";
};

zone "100.171.81.in-addr.arpa" {
        type master;
        file "pri.100.171.81.in-addr.arpa";
};

// line 40
zone "0.0.127.in-addr.arpa" {
        type master;
        file "pri.0.0.127.in-addr.arpa";
};

When I delete the domain again, bind refuses to start until I remove the line 40 zone by hand! I also need to kill the PID for bind.

The strange thing also is that after deleteting the domain (and emptying the recyle bins in ISPconfig) the domain is still in pri.100.171.81.in-addr.arpa.

Looking at the ISPconfig DB I also see the "bad" domain that I've deleted and removed from the recycle bins,

It's only show one time in the DB within "isp_isp_domain" (I've replaced 'bad_domain.info' and 'ip_of_my_server' in the code)

Code:

INSERT INTO `isp_isp_domain` VALUES (23, 1015, '', '0', 0, NULL, '', '', 'bad_domain.info', 'ip_of_my_server', '1');

I know I should not fu** with the ISPconfig DB, but I really need to get rid of this domain..

Now everytime that I make a change Bind refuses to start until I've removed the bad part from named.conf !

What can I do??

 

Till (not sure if you got my email that I send you yesterday)

I now see what I did wrong with the DNS error.
I added a Dutch domain to the server who only needed email.
The Dutch SIDN insist that you need a A record pointing to localhost.

I've done this for all Dutch domains that I have on the server, and was never a problem.

As the new domain only needed email, I removed all other A records (so it only had as A record localhost).
This was for some reason causing the zone '0.0.127.in-add.arpa': already exists error!

I've removed the DNS record and recreated it again (with all A records), and now all is okay again.

Now back to the isp_isp_domain problem.

What can I do about 'bad_domain.info' record?
It's not showing in ISPconfig itself (not in the "ISP Manager", not in the "recycle bin(s)", and not in "DNS Manager")

Can I just delete the record from the database?

Code:

INSERT INTO `isp_isp_domain` VALUES (23, 1015, '', '0', 0, NULL, '', '', 'bad_domain.info', 'ip_of_my_server', '1');

 

Problems solved.

I've deleted the "bad" record from the DB. Normally it should also be linked from isp_nodes and isp_dep, but as it was not I think it was safe to do so!

I've tested ISPconfig after the delete action, and all looks okay for now.

I have no clue what caused the "error" in the 1st place.

Thanks go to Till