Service domain dns setup

Hi,

I wonder how to setup the service domain dns. A service domain being the domain under which clients will get their nameservers from.

If I use the service domain for a host onto which ISPConfig is installed, for example host1.isphost123.com and I try to set up isphost123.com in ISPConfig, nothing is done in bind. For an unrelated domain it shows up in bind.

Do I have to setup bind independently of ISPConfig for the service domain?

There is nothing in the logs to identify errors. I run it on Debian wheezy.

Regards,

 

Conflict somewhere

Hi,

The log gives me this:
Writing BIND domain file failed: /etc/bind/pri.isphost123.com zone 911hosting.biz/IN: NS 'ns1.isphost123.com' has no address records (A or AAAA) zone isphost123.com/IN: NS 'ns2.isphost123.com' has no address records (A or AAAA) zone isphost123.com/IN: not loaded due to errors.

I am using the wizard with the standard template so it contains all records written in the exact same format and order as the other dummy test domains, that is weird, no?

So for any domain not related to the hostname's domain it works BUT not for the domain of the host.

Looks like some conflict somewhere, any clues?

I think the main hostname MUST already have a A record setup on another DNS server as explained at this link:
http://zonereseau.com/en/post/how-t...econdary-with-ispconfig-3-debian-squeeze--442

So this mean properlly setting up ISPConfig could require to use two temporary servers to setup DNS for the service domain, then register it as such with your registrar (Opensrs for intance will not allow that unless a DNS server can answer queries and you need 2 servers minimum). Then hopefully ISPConfig will allow to add the service domain onto the host.

Any hints?

 

Will not allow

Hi,

Ok I tried it and it failed.
I've created a proper DNS zone entry onto other servers which would resolv fine and then I tried to add that domain onto ISPConfig and I get the exact same error.

So this means if you try to run ISPConfig onto a hosts named for instance host1.isphost123.com, you cannot add and manage isphost123.com domain on this ISPConfig host.

Why is that?

Regards,

 

Is there 2 templates

Hi,

That is what you said in your first response.
Of course I've made tons of tests and why would it work fine for any and all other domains with the same template BUT not for the hostname domain?

Is there another hidden template?

Here is the .err file and it looks pretty much like the ones that are working:

cat pri.isphost123.com.err
$TTL 3600
@ IN SOA ns1.isphost123.com. hostmaster.isphost123.com. (
2013091001 ; serial, todays date + todays serial #
7200 ; refresh, seconds
540 ; retry, seconds
604800 ; expire, seconds
86400 ) ; minimum, seconds
;

isphost123.com. 3600 A 72.55.xxx.xx
isphost123.com. 3600 MX 10 mail.isphost123.com.
isphost123.com. 3600 NS ns1.isphost123.com.
mail 3600 A 72.55.xxx.xx
www 3600 A 72.55.xxx.xx

I replaced the last digit of ips with xx as well as isphost123.com is not the real domain.


Regards,

 

Still no luck

Ok I did add them (I did tested it before but I had deleted the entire zone and only used the wizard default thereafter).
Now with them as well as the proper reverse zone it still gives me the message that no ns records are defined.

I did all the proper delegation on the dns server that handles the subnet but it fails. I am not sure if this is not a catch 22 where it would check if the ns record exist BEFORE creating them, if that is the case then maybe I would need to make sure a forwarder is in place to allow that check.

See my logs:

support

cat pri.54-56.xxx.xx.72.in-addr.arpa.err
$TTL 3600
@ IN SOA ns1.isphost123.com. hostmaster.isphost123.com. (
2013091110 ; serial, todays date + todays serial #
7200 ; refresh, seconds
540 ; retry, seconds
604800 ; expire, seconds
86400 ) ; minimum, seconds
;

54 86400 NS ns1.isphost123.com
54 86400 PTR ns1.isphost123.com
55 86400 NS ns2.isphost123.com
55 86400 PTR ns2.isphost123.com

cat pri.isphost123.com.err
$TTL 3600
@ IN SOA ns1.isphost123.com. hosmaster.isphost123.com. (
2013091116 ; serial, todays date + todays serial #
7200 ; refresh, seconds
540 ; retry, seconds
604800 ; expire, seconds
86400 ) ; minimum, seconds
;

isphost123.com 86400 A 72.xx.xxx.54
isphost123.com 86400 NS ns1.isphost123.com
isphost123.com 86400 NS ns2.isphost123.com
mail 86400 A 72.xx.xxx.54
ns1.isphost123.com 86400 A 72.xx.xxx.54
ns2.isphost123.com 86400 A 72.xx.xxx.55

ISPConfig logs:

warning:Writing BIND domain file failed: /etc/bind/pri.54-56.xxx.xx.72.in-addr.arpa zone 54-56.xxx.xx.72.in-addr.arpa/IN: has no NS records zone 54-56.xxx.xx.72.in-addr.arpa/IN: not loaded due to errors.
warning:Writing BIND domain file failed: /etc/bind/pri.isphost123.com zone isphost123.com/IN: has no NS records zone isphost123.com/IN: not loaded due to errors.

I will enable a forwarder to the delegating dns server to see if it helps with this speculation.

Regards,

P.S; I also tried with the syntax:
cat pri.xxx.xx.72.in-addr.arpa.err but it failed too.
P.P.S; not working with a forwarder to the delegating server.
When I setup bind manually it works ok but somehow ISPConfig does a check it cannot complete that prevents the zone creation. This is on Wheezy

 

Any update

Hi,

Any updates?

Regards,

 

Additional issues

Hi,

This is not resolved yet but I now have an additional issue:

Since I cannot get the service domain to be created by ISPConfig despite having all proper a records setup, I had to manually set it (and it works fine, all delegation being properly done with related name servers and registrars). It works fine until I record a new domain/order/client, ISPConfig then delete my manually added zone and I have to re do it all.

Anyone have the same issues? I am on latest debian and latest ISPConfig.

Regards,