1) The dns wizard can not be used to creat subdomains. You have to edit the dns record of the existing domain and add a dns A-Record for the subdomain. Then you have to wait up to 48 hours until the dns record is propagated. It does not matter which TTL you had set, this will not speed this up.

Okay, cool - I was just concerned because under ISPC2 I could add new host records to a domain and could ping it within 5 minutes - CTLD - and now I can't - (I haven't set any transfer rights or anything like that - could that be a problem) - but if you think that it is fine, then that's cool!!

Kind regards,

Mentor

As a postscript: Added to the above, once I have followed through the methodology above, I cannot even ping the new host on the server on which it resides? I think that there may be an issue with MyDNS? Please let me know what you think as this is becoming a trifle urgent, thank you.

I am struggling to understand something related to the DNS issue that I am trying to sort out:

- I created a SOA - domainname.ctld
- I registered it with local country-registrar
- I can ping domainname.ctld as well as www.domainname.ctld
- I created a site and can go to it using either of the above URLs
- I created a sub-domain - host.domainname.ctld around four hours ago
- I cannot ping it and if I create a site for it I cannot go there
- I can DIG records for the domainname.ctld including the host.
- I cannot ping the host - even from the server on which it resides!?

What's going on? I have never experienced this before - I have used ISPConfig 2 on another platform and it just works - I can create a host and within 5 minutes I can ping it and build a site using it. I just think that somewhere I haven't configured something right - I did use the wizrd to create the domainname.ctld SOA and edited the record to manually add the new host - A-record.

I cannot dig records from my server from other hosts - they are refused - so perhaps that is part of the problem?

I have checked the MyDNS.conf file and the only change that I have made to it is to enable recursive lookups to another one of my hosts.

I am concerned as my installation is now a week overdue as a result of this problem, and I have already spent at least 12 to 18 hours over the last week trying to figure it out. It is unfortunate because there are a lot of great features in the ISPConfig 3, however if it not going to work from DNS point of view, then I cannot use it and will have rollback my new server to ISPConfig 2 or another solution. This would in my opinion be unfortunate, so if you are able to help I would really appreciate it very much, thank you.

To all who have assisted, thank you. Unfortunately we have decided that we cannot use ISPConfig 3 as it does not provide a satisfactory platform for our environment. This is very disappointing for us as it showed a lot of promise initially, however the DNS issues are proving a little to complex and long-winded to resolve.

A suggestion: ISPConfig 2 worked great with BIND - ISPConfig 3 has some really great features and a very nice front-end. Although some very good reasons have been stated for going with MyDNS, especially security, migration, simplicity, etc. it just does not not have sufficient footprint in the market to gain our vote of confidence - everyone runs BIND. Anyway, that is just my penny's worth.

I cannot dig records from my server from other hosts - they are refused - so perhaps that is part of the problem?

I have checked the MyDNS.conf file and the only change that I have made to it is to enable recursive lookups to another one of my hosts.

I am concerned as my installation is now a week overdue as a result of this problem, and I have already spent at least 12 to 18 hours over the last week trying to figure it out. It is unfortunate because there are a lot of great features in the ISPConfig 3, however if it not going to work from DNS point of view, then I cannot use it and will have rollback my new server to ISPConfig 2 or another solution. This would in my opinion be unfortunate, so if you are able to help I would really appreciate it very much, thank you.

Kind regards,

Mentor

Click to expand...

Looks as if you had a firewall enabled that blocks access to dns ports on your server.

Actually we found that the default config for recursive lookup in mydns.conf was a * or blank - I think that it was a * - I am not sure if that was meant to be changed as part of the installation process, but obviously setting it to an IP address was a good idea because dig started to work after that.

However there were still issues with not being able to ping hosts, even from the server where they were hosted, so we decided that it was too problematic to continue and stopped the project.

As I said, it is a pity because I actually like the new ISPconfig. Too bad!!

I really dont know what the problem is with your setup, but there are alredy more then 10.000 ispconfig 3 installations from the RC 2 and I know several companys which use it in production setups already and the dns system seem to work fine for these users.