Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 2 > General

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 27th January 2009, 02:15
kwlskwlguy kwlskwlguy is offline
Junior Member
 
Join Date: Jun 2007
Posts: 2
Thanks: 1
Thanked 0 Times in 0 Posts
Default Ex-Employee Manual DB changes need help

An ex-employee was caught making manual changes to db_ispconfig and now there's an MX record lost in the DB. We keep getting the error "This or a similar MX Record does already exist in this zone." I've put a band-aid on the problem by adding the MX manually after the "MAKE MANUAL ENTRIES BELOW THIS LINE!" in the bind zone file, but we would really like to fix the issue. I'm sure also that we're bound to find more errors like this.

I've made a mysqldump before and after adding another MX entry, and made a diff of the two, to find the places where the database is changed in an attempt to locate the rogue records. dns_dep, dns_mx, and dns_nodes seem to be the relevant tables.

From what I've seen future additions in ispconfig won't be affected by these, there's an auto-increment feature that (I believe) makes new entries clean. Also re-installation isn't really an option for us, far too many domains are here already, and I don't mind slowly fixing issues for many months.

Can some one point me to more explicit documentation on the table relationships, to assist me in this? Or anything that might simplify the process?

Thank you all in advance.
Reply With Quote
Sponsored Links
  #2  
Old 27th January 2009, 11:51
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 36,769
Thanks: 840
Thanked 5,609 Times in 4,420 Posts
Default

There is no further documenatation available. Basically the dns_dep table is the cross table that links dns_mx with the dns_soa table. Here are the relations to find your phantom record:

dns_soa.doc_id = dns_dep.parent_doc_id
dns_soa.doctype_id = dns_dep.parent_doctype_id
dns_dep.child_doc_id = dns_mx.doc_id
dns_dep.child_doctype_id = dns_mx.doctype_id
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
The Following User Says Thank You to till For This Useful Post:
kwlskwlguy (3rd February 2009)
  #3  
Old 3rd February 2009, 04:28
kwlskwlguy kwlskwlguy is offline
Junior Member
 
Join Date: Jun 2007
Posts: 2
Thanks: 1
Thanked 0 Times in 0 Posts
 
Thumbs up

Great Thanks for the table relation mappings. I've used this post to eliminate 3 inconsistencies already, and feel much better about the process. Only about 4500 more entries to check, lol. I'm writing SQL queries to simplify the process so it's only a matter of time.


Again, Thank you very much.
Reply With Quote
Reply

Bookmarks

Tags
database, manual changes, table relationships

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
[bug] bind, manual entries broken by changes rachel Developers' Forum 3 24th December 2008 13:16
'Salutatory Email for Clients' wrong CP and manual URL greenpete Installation/Configuration 4 23rd March 2008 20:12
Allow entry of manual items to postfix local-host-names file through web interface catdude Feature Requests 2 21st January 2008 04:32
Manual Additions in Configuration Files DiOmega General 4 18th May 2006 11:30
Manual ISPConfig installation Jan Installation/Configuration 6 29th October 2005 12:56


All times are GMT +2. The time now is 11:14.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.