Current time: 04-24-2024, 11:08 AM Hello There, Guest! (LoginRegister)


Post Reply 
Manual lines in DNS zone file
Author Message
sci2tech Away
Senior Member
****

Posts: 1,285
Joined: Jan 2007
Reputation: 23
Post: #101
RE: Manual lines in DNS zone file
It`s not mine work so Blondak has all credits for this Wink. First MX is default setting for domain. Second MX record point to a secondary mail server for load balancing or fail backup.
05-04-2009 01:54 AM
Visit this user's website Find all posts by this user Quote this message in a reply
tomdooley Offline
Development Team
*****
Dev Team

Posts: 332
Joined: Sep 2007
Reputation: 7
Post: #102
RE: Manual lines in DNS zone file
(05-04-2009 01:54 AM)sci2tech Wrote:  It`s not mine work so Blondak has all credits for this Wink. First MX is default setting for domain. Second MX record point to a secondary mail server for load balancing or fail backup.

Argh... OK, that will not suite my needs, but perhaps for others. A different mailserver for a domain does also need other things to do (removing domain from postfix domains, ...) Should I create a ticket for this (new) request? :-)
05-04-2009 02:07 AM
Visit this user's website Find all posts by this user Quote this message in a reply
aseques Offline
Member
*****
Dev Team

Posts: 330
Joined: May 2008
Reputation: 4
Post: #103
RE: Manual lines in DNS zone file
Thanks for your work guys, can't hardly wait to have a new stable release and drop plesk from all my servers Smile

Oh, and I see that now, you are using $timestamp = time(); instead of previous function. So now ticket http://www.isp-control.net/ispcp/ticket/1785 can be closed.

Good jog
05-04-2009 05:31 AM
Find all posts by this user Quote this message in a reply
Blondak Offline
Junior Member
*****
Dev Team

Posts: 84
Joined: May 2008
Reputation: 5
Post: #104
RE: Manual lines in DNS zone file
(05-04-2009 02:07 AM)tomdooley Wrote:  
(05-04-2009 01:54 AM)sci2tech Wrote:  It`s not mine work so Blondak has all credits for this Wink. First MX is default setting for domain. Second MX record point to a secondary mail server for load balancing or fail backup.

Argh... OK, that will not suite my needs, but perhaps for others. A different mailserver for a domain does also need other things to do (removing domain from postfix domains, ...) Should I create a ticket for this (new) request? :-)

Now, then is my update in trunk we can do more thinks. Now we can remove MX records from db_master_e.tpl file and insert them to the database, so you can edit MX as you want, same for FTP, WWW, ....
What dou you think about this idea?
05-04-2009 07:48 PM
Visit this user's website Find all posts by this user Quote this message in a reply
sunsus Offline
Junior Member
*

Posts: 23
Joined: Jun 2007
Reputation: 0
Post: #105
RE: Manual lines in DNS zone file
Maybe the best thing would be to store all dns information in the DB.
If some one add a subdomain or a alias just store it to the DB with a pointer to the record (subdomain/alias), for the del porcess.
Then you are flexibel and can change, delet dns records as you like!

In ispcp-rqst-mngr build the DNS zone files form the DB.
As well it would be nice to include the option for fix dns server to be rfc conform!

In advanced a interface for the secondery dns could be usefull!
05-04-2009 08:15 PM
Visit this user's website Find all posts by this user Quote this message in a reply
pongraczi Offline
Junior Member
*

Posts: 80
Joined: Jul 2008
Reputation: 2
Post: #106
RE: Manual lines in DNS zone file
Hi,

Finally I found this thread, very good!
At this moment I manually hacked the dns template to get the possibility to change mail dns settings and add my secondary dns entires to all domains.

So, I can see the progress and I am really happy about it Smile

Anyway, I do not know, why I lost all subdomains from apache when I recreate apache config........ Maybe I only missed something. I use the nightly, some days before....
05-08-2009 06:29 PM
Visit this user's website Find all posts by this user Quote this message in a reply
sci2tech Away
Senior Member
****

Posts: 1,285
Joined: Jan 2007
Reputation: 23
Post: #107
RE: Manual lines in DNS zone file
Try rebuild are your config files. How did you update?
05-09-2009 01:00 AM
Visit this user's website Find all posts by this user Quote this message in a reply
pgentoo Offline
Member
*****
Dev Team

Posts: 326
Joined: Mar 2007
Reputation: 0
Post: #108
RE: Manual lines in DNS zone file
pongraczi, I think i logged a bug that got fixed on this, but maybe not...

When you regenerate your configs, you need to set domains and subdomains to "CHANGE" or you'll lose all your subdomains. If you put them both as CHANGE, then everything will regen. I thought this was fixed...

-
pgentoo
05-09-2009 11:00 AM
Find all posts by this user Quote this message in a reply
pongraczi Offline
Junior Member
*

Posts: 80
Joined: Jul 2008
Reputation: 2
Post: #109
RE: Manual lines in DNS zone file
Hi,

I use the nightly upgrade script from the Howto section in middle of January but not the super lazy one Smile
Usually this sciprt completed the job correctly, without any problem. Anyway, if I add a new domain, I will lost every aldomains again Smile

I forgot to update the tpl files (under parts directory) before, but I checked it some days ago and I found some changes. I made a test environment (I use openvz virtualization as basis) from the live system and I will update everything to the latest version.

So, I have to do a nice upgrade to the latest nightly trunk version before confirm the bug or PEBCAK.
I will check that 'CHANGE' flag too.
Thanks guys!
05-09-2009 09:44 PM
Visit this user's website Find all posts by this user Quote this message in a reply
sci2tech Away
Senior Member
****

Posts: 1,285
Joined: Jan 2007
Reputation: 23
Post: #110
RE: Manual lines in DNS zone file
Please try super lazy one (automated version), or use from automated version queries Wink. The other is not updated for some time, and this causes the problem.
05-09-2009 10:25 PM
Visit this user's website Find all posts by this user Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: