+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Development Area (/forum-1.html)
+--- Forum: General discussion (/forum-11.html)
+--- Thread: Manual lines in DNS zone file (/thread-3727.html)
RE: Manual lines in DNS zone file - ephigenie - 05-26-2009 06:36 PM
yes. Try to find the file you like to have patched before you just stupidly type what others say.
if you already have a installed ispCP there's no configs/centos bla whatever directory .
Only sth. like in /etc/ispcp/bind/parts - please try reading the manpage for patch (man patch).
Sry for being a bit rude - but ppl not even trying to think about the obvious are driving me mad.
RE: Manual lines in DNS zone file - sfera - 05-26-2009 07:30 PM
Sorry dude, i think im correctly.
I have some problems with the english and i dont find any manual for DNS-zone patch. I dont want create probles to you.
I decide dont install the patch. I dont need help for install Isp-cp only for this problem and for translate isp to other server. Thx for try help me and sorry my bad english and for dont undertand the solution.
RE: Manual lines in DNS zone file - tuxStyle - 05-27-2009 02:19 AM
I have a problem with the MX records:
Code:
May 26 12:02:25 sync named[3773]: dns_master_load: /var/cache/bind/sync.uni.cc.db:63: ftp.sync.uni.cc: CNAME and other data
May 26 12:02:25 sync named[3773]: zone sync.uni.cc/IN: loading from master file /var/cache/bind/sync.uni.cc.db failed: CNAME and other dataZone file:
Code:
$TTL 12H
$ORIGIN sync.uni.cc.
@ IN SOA ns1.sync.uni.cc. postmaster.sync.uni.cc. (
; dmn [sync.uni.cc] timestamp entry BEGIN.
2009052600 ; Serial
; dmn [sync.uni.cc] timestamp entry END.
8H ; Refresh
30M ; Retry
4W ; Expire
3H ; Minimum TTL
)
IN NS ns1.sync.uni.cc.
IN NS ns2.sync.uni.cc.
sync.uni.cc. IN A 69.197.162.131
sync.uni.cc. IN TXT "v=spf1 a mx ip4:69.197.162.131 ~all"
localhost IN A 127.0.0.1
ns1 IN A 69.197.162.131
ns2 IN A 193.230.197.29
; CNAME for VHCS compatibility
ns IN CNAME ns1
; sub [{SUB_NAME}] entry BEGIN.
; sub [{SUB_NAME}] entry END.
; dns [1] entry BEGIN.
admin IN A 69.197.162.131
; dns [1] entry END.
; dns [2] entry BEGIN.
mail IN A 69.197.162.131
; dns [2] entry END.
; dns [3] entry BEGIN.
imap IN CNAME mail
; dns [3] entry END.
; dns [4] entry BEGIN.
pop3 IN CNAME mail
; dns [4] entry END.
; dns [5] entry BEGIN.
pop IN CNAME mail
; dns [5] entry END.
; dns [6] entry BEGIN.
relay IN CNAME mail
; dns [6] entry END.
; dns [7] entry BEGIN.
smtp IN CNAME mail
; dns [7] entry END.
; dns [8] entry BEGIN.
www IN A 69.197.162.131
; dns [8] entry END.
; dns [9] entry BEGIN.
ftp IN CNAME www
; dns [9] entry END.
; dns [11] entry BEGIN.
IN MX 10 mail.sync.uni.cc.
; dns [11] entry END.
; dns [{MANUAL_DNS_ID}] entry BEGIN.
; dns [{MANUAL_DNS_ID}] entry END.Moving the IN MX record on top, under name servers solve the problem.
Also i think:
Code:
sync.uni.cc. IN TXT "v=spf1 a mx ip4:69.197.162.131 ~all"Code:
sync.uni.cc. IN TXT "v=spf1 a mx ip4:69.197.162.131 include:mail.sync.uni.cc ~all"just in case the MX points to a different IP address.
RE: Manual lines in DNS zone file - ephigenie - 05-27-2009 04:11 AM
(05-25-2009 11:55 PM)sfera Wrote: Hi epigenie.
I try yout comment but i get the same error
ks202641:/etc/ispcp# patch -p1< basic-dns-support-1.0.0.patch.txt
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
can't find file to patch at input line 19
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -bNBru ispcp-omega-1.0.0/configs/centos/bind/parts/db_e.tpl ispcp-omega-1.0.0.patched/configs/centos/bind/parts/db_e.tpl
|--- ispcp-omega-1.0.0/configs/centos/bind/parts/db_e.tpl 2009-02-08 11:58:58.000000000 +0100
|+++ ispcp-omega-1.0.0.patched/configs/centos/bind/parts/db_e.tpl 2009-03-16 16:14:29.000000000 +0100
--------------------------
File to patch:
any idea? Thx in advanced.
yeah : the idea is to look if those files which are going to be patched exist under the path were they're sarched for.
so patch -p<num> < patchfile #where <num> specifys the directory leveldepth to rip of from the filepaths of files affected in the patch.
The configs/ directory can only be in a fresh source directory.
in an already installed ispCP there's no configs dir. But the affected files are there (at least the modified templates) .
These are below /etc/ispcp/bind/parts
So try to count how many filelevels you need to remove via <num> to make the patch apply.
RE: Manual lines in DNS zone file - yoyoucool3 - 05-29-2009 04:10 AM
I just read through the previous posts and I see people having problems and errors (and bad english,
har har). It's all very confusing. Wondering if someone can put together a simple "howto" so everyone's on the same page, or if it exists already and I haven't found it by searching, where it would be. I'm running 1.0.0 stable, I updated from RC7. Lower left-hand corner states
ispCP 1.0.0 OMEGA
build: 20090225
Codename: Priamos
Thanks for any help, this is the only feature i'm dying to get on my box.. it's production though so I don't want to mess with nightly builds (right now only have 1 running ispcp due to dns not being configurable)
Thanks!
-Brent
RE: Manual lines in DNS zone file - bpratt - 06-04-2009 09:07 AM
(05-29-2009 04:10 AM)yoyoucool3 Wrote: I just read through the previous posts and I see people having problems and errors (and bad english,
I'm running 1.0.0 stable,
Thanks for any help, this is the only feature i'm dying to get on my box.. it's production though so I don't want to mess with nightly builds (right now only have 1 running ispcp due to dns not being configurable)
Like you, I am keen to to install the same on my 1.0.0 stable system, but after reading the whole thread, it appears that most people are running it with RC6 or earlier.
I have been hoping a howto would be available so that we can upgrade to this feature without killing our systems.
Thanks in advance.
RE: Manual lines in DNS zone file - tuxStyle - 06-04-2009 12:11 PM
Is working fine with a nightly built but still have some issues.
Subdomains are not generated after a record is added.
MX records are added in in a wrong place.
Some records (ftp, pop, smtp, etc) are in template file and are not editable.
Is a lot of work to be done...
It crossed my mid to start doing some changes but i will have a new project at work so, i won't have any spare time
Let's just hope the owner will be back and finish the job.
RE: Manual lines in DNS zone file - Foggy - 06-22-2009 06:09 PM
Hm, i have same iusse with mx records with different ip.
The currently record wich will be generated looks like this:
Code:
; dns [5] entry BEGIN.
exchange IN A 123.123.123.123
; dns [5] entry END.
; dns [6] entry BEGIN.
IN MX 0 exchange.domain.tld.
; dns [6] entry END.Code:
; dns [5] entry BEGIN.
exchange IN A 123.123.123.123
; dns [5] entry END.
; dns [6] entry BEGIN.
domain.tld. IN MX 0 exchange.domain.tld.
; dns [6] entry END.So to do this, just one question, how and when will this records be generated? Cause i dont find any template for this to change the generating of mx records with domain.tld.
Ok, i came up to change line 497 from /var/www/ispcp/gui/client/edit_dns.php from
Code:
$_dns = '';Code:
$_dns = $record_domain . '.';RE: Manual lines in DNS zone file - BeNe - 06-22-2009 07:16 PM
So we need this change in the trunk ?
Greez BeNe
RE: Manual lines in DNS zone file - tango - 06-22-2009 10:19 PM
I am also waiting since 3 / 4 year