Manual lines in DNS zone file

[CHBIE]

Thats work - Thanks!

1. missing Manual DNS support - in user_add2.php when create user without Hosting Plan
2. error in client/add_dns.php with IE7 "Your Browser does not support DOM 2 Style Sheets"

that is vor the moment all.

Gruss CHBIE

[tango]

(02-09-2009 02:06 AM)sci2tech Wrote:  How to use:
First we need some sql query to execute:

Code:

CREATE TABLE IF NOT EXISTS `domain_dns` (
`domain_dns_id` int(11) NOT NULL auto_increment,
`domain_id` int(11) NOT NULL,
`alias_id` int(11) default NULL,
`domain_dns` varchar(50) NOT NULL,
`domain_class` enum('IN','CH','HS') NOT NULL default 'IN',
`domain_type` enum('A','AAAA','CERT','CNAME','DNAME','GPOS','KEY','KX','MX','NAPTR','NSAP','NS​ ','NXT','PTR','PX','SIG','SRV','TXT') NOT NULL default 'A',
`domain_text` varchar(128) NOT NULL,
PRIMARY KEY (`domain_dns_id`)
);

ALTER TABLE `domain` ADD `domain_dns` VARCHAR( 15 ) NOT NULL DEFAULT 'no';

Then

Code:

cd /patch/where/we/have/ispcp/trunk
patch -p0< [FILENAME]

where file name is the name of the following patch: . this include all previous patches and some bug fixes. The perform an update / install or whatever you want, and you will have dns support

sorry my English is bad, one can translate to me what exactly needs to be done in order to use this feature?

[FeG]

Hi tango,

(02-20-2009 10:11 PM)tango Wrote:  sorry my English is bad, one can translate to me what exactly needs to be done in order to use this feature?

Du musst zuerst die beiden angegebenen SQL-Querys ausführen (die in der oberen Box).

Danach führst du diese beiden Befehle aus:

Code:

cd /patch/where/we/have/ispcp/trunk
patch -p0< [FILENAME]

Wobei das Verzeichnis der trunk von ispCP ist und FILENAME die heruntergeladene patch.txt datei (welche du noch entzippen musst, also patch.txt.gz -> patch.txt).

Mit diesem gepatchten trunk kannst du dann ein Update oder eine Installation durchführen, je nachdem, was du vor hast.

So.. ich hoffe, dass das jetzt halbwegs hinkommt, auch wenn ich mich nicht näher damit beschäftigt habe

Gruß
FeG

[tango]

danke werde es mal ausführen

edit:

http://www.alleslegal.net/20.02.png

one can help me ??

[geri1590]

Hi, I don't have much time with ispCP,
when i have the patch, what I should to do to apply to my server?

thnks

[xister]

@geri1590
http://www.isp-control.net/forum/showthr...3#pid45373

[tango]

I do not know what I should enter? see Post #64

Edit:

Code:

Last login: Mon Feb 23 03:14:28 2009
admin:~# cd /var/www/ispcp
admin:/var/www/ispcp# patch -p0< patch.txt
patching file gui/include/ispcp-functions.php
Hunk #1 FAILED at 123.
Hunk #2 FAILED at 140.
Hunk #3 FAILED at 172.
Hunk #4 FAILED at 190.
4 out of 4 hunks FAILED -- saving rejects to file gui/include/ispcp-functions.php.rej
patching file gui/include/client-functions.php.orig
patching file gui/include/client-functions.php
Hunk #1 FAILED at 40.
1 out of 3 hunks FAILED -- saving rejects to file gui/include/client-functions.php.rej
patching file gui/themes/omega_original/admin/hosting_plan_edit.tpl
Hunk #1 succeeded at 121 (offset -1 lines).
patching file gui/themes/omega_original/admin/hosting_plan_add.tpl
Hunk #1 succeeded at 113 (offset -1 lines).
patching file gui/themes/omega_original/orderpanel/package_info.tpl
patching file gui/themes/omega_original/reseller/hosting_plan_edit.tpl
Hunk #1 succeeded at 127 (offset -1 lines).
patching file gui/themes/omega_original/reseller/domain_details.tpl
Hunk #1 succeeded at 67 (offset -1 lines).
patching file gui/themes/omega_original/reseller/hosting_plan_add.tpl
Hunk #1 succeeded at 118 (offset -1 lines).
patching file gui/themes/omega_original/reseller/domain_edit.tpl
Hunk #1 succeeded at 88 (offset -1 lines).
patching file gui/themes/omega_original/client/domains_manage.tpl
Hunk #1 succeeded at 140 (offset -1 lines).
patching file gui/themes/omega_original/client/menu_manage_domains.tpl
patching file gui/themes/omega_original/client/edit_dns.tpl
patching file gui/admin/hosting_plan_edit.php
Hunk #2 FAILED at 117.
Hunk #4 succeeded at 198 with fuzz 1.
Hunk #5 FAILED at 228.
Hunk #6 succeeded at 277 (offset 32 lines).
Hunk #7 succeeded at 296 (offset 32 lines).
Hunk #8 succeeded at 349 (offset 32 lines).
Hunk #9 succeeded at 372 (offset 32 lines).
2 out of 9 hunks FAILED -- saving rejects to file gui/admin/hosting_plan_edit.php.rej
patching file gui/admin/hosting_plan_add.php
Hunk #1 FAILED at 34.
Hunk #2 FAILED at 52.
Hunk #3 FAILED at 106.
Hunk #4 FAILED at 141.
Hunk #5 FAILED at 190.
Hunk #6 succeeded at 220 (offset -6 lines).
Hunk #7 succeeded at 274 with fuzz 2 (offset -6 lines).
Hunk #8 FAILED at 298.
6 out of 8 hunks FAILED -- saving rejects to file gui/admin/hosting_plan_add.php.rej
patching file gui/orderpanel/package_info.php
Hunk #3 succeeded at 171 (offset 6 lines).
patching file gui/reseller/hosting_plan_edit.php
Hunk #4 FAILED at 244.
Hunk #5 succeeded at 295 (offset 32 lines).
Hunk #6 succeeded at 323 (offset 32 lines).
Hunk #7 succeeded at 366 (offset 32 lines).
Hunk #8 succeeded at 376 (offset 32 lines).
1 out of 8 hunks FAILED -- saving rejects to file gui/reseller/hosting_plan_edit.php.rej
patching file gui/reseller/orders_update.php
patching file gui/reseller/orders_add.php.orig
patching file gui/reseller/orders_add.php
patching file gui/reseller/user_add3.php.orig
patching file gui/reseller/domain_details.php.orig
patching file gui/reseller/domain_details.php
patching file gui/reseller/hosting_plan_add.php
Hunk #3 FAILED at 108.
Hunk #4 FAILED at 143.
Hunk #5 FAILED at 192.
Hunk #8 succeeded at 292 with fuzz 2.
3 out of 8 hunks FAILED -- saving rejects to file gui/reseller/hosting_plan_add.php.rej
patching file gui/reseller/user_add3.php
Hunk #1 succeeded at 238 with fuzz 2.
patching file gui/reseller/domain_edit.php.orig
patching file gui/reseller/domain_edit.php
Hunk #6 FAILED at 230.
1 out of 10 hunks FAILED -- saving rejects to file gui/reseller/domain_edit.php.rej
patching file gui/client/domains_manage.php
Hunk #2 succeeded at 308 (offset -11 lines).
Hunk #3 succeeded at 332 (offset -11 lines).
patching file gui/client/add_dns.php
patching file gui/client/edit_dns.php
patching file gui/client/delete_dns.php
patching file configs/fedora/bind/parts/db_e.tpl.orig
can't find file to patch at input line 5181
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: configs/fedora/bind/parts/db_e.tpl
|===================================================================
|--- configs/fedora/bind/parts/db_e.tpl (revision 1475)
|+++ configs/fedora/bind/parts/db_e.tpl (working copy)
--------------------------
File to patch:

what am I doing wrong?

[hnn]

i noticed a bug within this patch.

My subdomains are disappearing when i add manual DNS records. They completly stop working.

[greatman]

Getting bugs with the new 1.0 ispcp .

Code:

patching file configs/centos/bind/parts/db_dns_entry_b.tpl
patching file configs/centos/bind/parts/db_dns_entry_e.tpl
patching file configs/centos/bind/parts/db_dns_entry.tpl
patching file configs/centos/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file configs/debian/bind/parts/db_dns_entry_b.tpl
patching file configs/debian/bind/parts/db_dns_entry_e.tpl
patching file configs/debian/bind/parts/db_dns_entry.tpl
patching file configs/debian/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file configs/fedora/bind/parts/db_dns_entry_b.tpl
patching file configs/fedora/bind/parts/db_dns_entry_e.tpl
patching file configs/fedora/bind/parts/db_dns_entry.tpl
patching file configs/fedora/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file configs/freebsd/bind/parts/db_dns_entry_b.tpl
patching file configs/freebsd/bind/parts/db_dns_entry_e.tpl
patching file configs/freebsd/bind/parts/db_dns_entry.tpl
patching file configs/freebsd/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file configs/gentoo/bind/parts/db_dns_entry_b.tpl
patching file configs/gentoo/bind/parts/db_dns_entry_e.tpl
patching file configs/gentoo/bind/parts/db_dns_entry.tpl
patching file configs/gentoo/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file configs/openbsd/bind/parts/db_dns_entry_b.tpl
patching file configs/openbsd/bind/parts/db_dns_entry_e.tpl
patching file configs/openbsd/bind/parts/db_dns_entry.tpl
patching file configs/openbsd/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file configs/opensuse/bind/parts/db_dns_entry_b.tpl
patching file configs/opensuse/bind/parts/db_dns_entry_e.tpl
patching file configs/opensuse/bind/parts/db_dns_entry.tpl
patching file configs/opensuse/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file configs/redhat/bind/parts/db_dns_entry_b.tpl
patching file configs/redhat/bind/parts/db_dns_entry_e.tpl
patching file configs/redhat/bind/parts/db_dns_entry.tpl
patching file configs/redhat/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file configs/ubuntu/bind/parts/db_dns_entry_b.tpl
patching file configs/ubuntu/bind/parts/db_dns_entry_e.tpl
patching file configs/ubuntu/bind/parts/db_dns_entry.tpl
patching file configs/ubuntu/bind/parts/db_e.tpl
Hunk #1 succeeded at 32 (offset 2 lines).
patching file engine/ispcp-als-mngr
patching file engine/ispcp-dmn-mngr
patching file gui/client/add_dns.php
patching file gui/client/delete_dns.php
patching file gui/client/domains_manage.php
Hunk #2 succeeded at 308 (offset -11 lines).
Hunk #3 succeeded at 332 (offset -11 lines).
patching file gui/client/edit_dns.php
patching file gui/include/client-functions.php
Hunk #1 FAILED at 40.
Hunk #3 succeeded at 443 (offset 31 lines).
1 out of 3 hunks FAILED -- saving rejects to file gui/include/client-functions.p                                                                             hp.rej
The next patch would create the file gui/include/client-functions.php.orig,
which already exists!  Assume -R? [n]

[NecromanX]

Hello all,

i am new too ispcp and offcourse this forum. But i found a little issue in this patch.
I have a second nameserver configured to slave all zones from the primary nameserver. But in this patch if i would add 4 or 5 records in 1 day the serial would still remain the same! this is an issue if you want your second nameserver to get the updated zones. And offcourse it just isnt correct to keep the zone's serial identical after multiple modifications.

i fixed this issue by adding a new field in the table domain:
field: last_session [varchar:10] at the end of the table. this field stores the last used session and if the used timestamp is equal to this last_session of smaller then fill in the TIMESTAMP serial tag with last_session + 1
Here is my diff file between my ispcp-dns-mngr and the one after this rc7 patch

Code:

382a383
>       my $dmn_id       = @$dmn_data[0];
384a386
>       my $last_serial  = @$dmn_data[22];
423a426
>
426a430,438
>       #Is our Timestamp outdated? did we edit the zone allready this day?
>       if ($time2 eq $last_serial || $time2 <= $last_serial){
>               $time2 = $last_serial + 1;
>       }
>
>       my $sql_fix = "update domain set last_serial='$time2' where domain_id = $dmn_id";
>       my $data_fix = undef;
>       ($rs, $data_fix) = doSQL($sql_fix);
>
3632c3644
<               t1.domain_cgi, t2.ip_number FROM domain AS t1, server_ips AS t2 WHERE t1.domain_ip_id = t2.ip_id
---
>               t1.domain_cgi, t2.ip_number, t1.last_serial FROM domain AS t1, server_ips AS t2 WHERE t1.domain_ip_id = t2.ip_id

If anyone would be so kind to modify the current patch with my diff and the alter table instructions.
I would create the patch myself but i should look up how to create a propper patch. What command should i use?

I Hope this is of any use to someone

Greets,
David