ISPConfig3 MyDNS-ng master axfr zone transfer to bind9 slave

[JerryJones]

Hi,
sorry that i'm starting here with my question, but everybody talks only about transfers for bind as slave and mydns as master.

herre my situation:
both configs based on Centos 5.2,5.3 32bit
as in the title my configs was
1th dns master ispconfig2/bind
2th dns slave ispconfig2/bind
and now the last one:
config based on Centos 5.4 64bit
1th dns master ispconfig3/mydns

i cannot find any manual how its discribed how i can setup a secondary zone on the mydns via the gui. sorry with ispconfig 2 it was allready simple.

pleasy give me help, i think iths the soft way to make a slow migration to a modern tool like ispconfig 3

kindest regards Jerry

[till]

MyDNS does not support to be the slave for a bind master, thats why there is no such function in the ispconfig interface.

[xxfog]

Hi folks,

what do i have to enter in the notify-source field ?

My Domain-Provider uses 3 SLAVE-DNS-Servers with powerdns running on.
But I don`t get them running as slave like I need it.
I always get messages like "Zonetranfer unsuccessfull"

The Provider just tried to start AXFR manually and got this message:

dig @server.dm-o.com mv-chat.de AXFR

->
; (1 server found)
;; global options: +cmd
; Transfer failed.

How do I have to put more than just 1 secondary DNS-server in the XFER Field of ISPConfig>Zones?
Do they have to be sperated with "," or with ";" or what sign do I have to use for seperation? The german language file says "-" as seperator and the english one says ",".

I found out that the notify section is missing in my conf-file, do I have to add it too?
If yes, can I transfer the IP-Adresses I entered in ISPConfig in XFER-Field to use them as notify-IP somehow too?

Sorry for my bad english.

What I really don`t understand: if I use another (older) SLAVE Server (I guess with bind running on) than it seems to work :-(
So I thought, that the error has to be on the 3 new Nameservers of my Provider. But these new servers are there main servers and if it would be like I mentioned than 1000nds of users would be very angry. So I guess what they say is right and the error seems to be on my server / configuration :-/

My configuration file says:
.
.
allow-axfr = yes
allow-tcp = yes
allow-update = no
ignore-minimum = no
.
.
but notify-enabled = yes and notify-source are missing

So please tell me, how can I add all XFER IPs there out of the database?

thanks and best greetings

[lucani]

I dont know if anybody force this s... to work... axfr has many problems in MyDNS. Did you use this fix ? It's absolutely necessary: http://howtoforge.com/forums/showpos...8&postcount=15

[till]

No, dont apply this. This fix is for a outdated version of mydns. Instead install the latest mydns-ng that includes the fix already! If you apply this on a recent version of ispconfig and mydns, zone transfers will stop.

[lucani]

Yeah... ; / But tell me what does it mean "recent", in sourceforge I see this

mydns-1.2.8.27.tar.gz 2009-03-26

If its corrected version it means that ixfr works ? What about axfr ? I saw code and it seems that it still doesnt edited because I done it manually.

Anyway, what should I do now ? Do I have to reinstall all ? ; /

[till]

Nobody said that you should reinstall anything

I'am pretty sure that there was a mydns-1.2.8.28 available which fixed this issue, seems as if it had been removed.

In this case you are right that the mydns sources would have to be patched or you change the ispconfig sources. But as its a mydns bug (I explained thst in detail in the thread), it might be better to change the mydns sources.

[lucani]

Yes, I heard about release in last July (?). Someone saids that zonetransfers works good, have you got copy in local disks or maybe links to mirrors ?

[till]

I've searched the net and checked my vm images that I use for testing but I was not able to find it. Lets hope that the mydns project releases a fixed version soon. With the upcoming ISPConfig 3.0.2, there will also be BIND and powerdns available as alternatives.

[manarak]

that's good news, because I too was unable to find a newer version of mydns, and was unable to get the zone transfers to work.