Registering Secondary DNS when virmin is master

Hi

Presuming that my virtualmin server is DNS master for <mydomain>.com

How can i setup for <mydomain>.com : sdns1.ovh.net has secondary DNS on my virtualmin instance ?

this operation seems to be mandatory to make ".fr" domain work as AFNIC verify that your domain has a master and synchronized slave dns.

bpds

That depends on whether Virtualmin will also be managing the secondary, or not.

If it will be managing the secondary, just follow these instructions:

http://www.virtualmin.com/documentation/id,dns_slave_auto-configuration_quickstart/

If it won’t be managing the secondary, and you just want Virtualmin to know about it, so it adds secondary MX records to new virtual servers, you can just set that in the Server Template(s) that you use in the BIND DNS domain section, in the field labelled “Additional manually configured nameservers”.

"so it adds secondary MX records" should obviously have been "so it adds secondary NS records".

Joe,

I ve tryed but really it is not clear at all…

And we are deeply blocked with mail account that disrupt and other major blocking problems as the AFNIC that deal with .fr block all our domains !!!

We only have to synchronize all our viryualmin’s zone to : sdns1.ovh.net as a slave DNS.

HOW TO ?

the easiest and fastest way is to buy a $20 VPS, set up webmin with bind and bring it into virtualmin as a secondary slave.

ronald many thanks for your suggestion !!!

Here we are :

Could you tell me how "can i bring it into virtualmin as a secondary slave ?"

Is it possible to declare a slave for all the hosted zone ?

In my particular case i want to setup sdns1.ovh.net as slave DNS for all the domains i host.

This operation is required to make ours ".fr" working correctly

I ve attached a pdf to this reply to show what i ve tryed.

Could you tell me if it seems correct ?

Bpds

[file name=slaveDNS.pdf size=263077]http://www.virtualmin.com/components/com_fireboard/uploaded/files/slaveDNS.pdf[/file]

I would not put sdns1.ovh.net as a slave on the same server, because it will be on the same IP/subnet. Apparently .fr regulation does not like that very much.

To comply with ".fr" regulation (same as in Pays Bas) you best buy a VPS somewhere. They are cheap in the USA. (I have one at vpslink.com, but you can get one anywhere)
Put centos on it and webmin, then bind.

The hostname of that VPS should be sdns1.ovh.net (you’ll need to register that nameserver at the registrar that holds ovh.net with the VPS’s IP)

then do this
http://www.virtualmin.com/documentation/id,dns_slave_auto-configuration_quickstart/

and it will be automated for all your domains.
This is how I did it to make it work perfectly.

There are other ways but some countries are just very strict in how you set things up (france, netherlands, germany and so on). It is much easier with .net, .com, .org etc

Hello!

I think I have the same problem like bpds.

On my rootserver at ovh.de I like (have to) use theyr secondary DNS sdns1.ovh.net, whitch is managed manually via a seperat web-form.

I added this under "Server Templates" --> "BIND DNS Domain" --> "Additional manually configured nameservers": sdns1.ovh.net.

How can I push this setting into all the Domain-Records I have on this virtualmin server? (there are 58 Domains, so I cannot do it manually)

For one Domain I did it manually:

[code:1]$ttl 38400
@ IN SOA ns38229.ovh.net. root.ns38229.ovh.net. (
1231012314
10800
3600
604800
38400 )
@ IN NS ns38229.ovh.net.
eggp.ch. IN NS sdns1.ovh.net.
eggp.ch. IN A 87.98.242.101
www.eggp.ch. IN A 87.98.242.101
ftp.eggp.ch. IN A 87.98.242.101
m.eggp.ch. IN A 87.98.242.101
localhost.eggp.ch. IN A 127.0.0.1
admin.eggp.ch. IN A 87.98.242.101
mail.eggp.ch. IN A 87.98.242.101
eggp.ch. IN MX 5 mail.eggp.de.
[/code:1]

Unfortunely this does not work. The Zonecheck tells me that the list of nameservers does not match the one I provided (ns38229.ovh.net, sdns1.ovh.net):

zonecheck denic eggp.ch

schwerer Fehler ---- Die Nameserver aus dem Auftrag stimmen nicht überein mit denen aus der Zone Die Liste der Nameserver aus dem Auftrag (ns38229.ovh.net., sdns1.ovh.net.) stimmt nicht überein mit der Liste der Nameserver aus der Zone (ns38229.ovh.net.).

–> sdns1.ovh.net./213.251.188.140

Also the zonecheck complains about the serial number beeing in a wrong format, but that is just a warning…
(Die Serialnummer 1231012314 scheint nicht im Format JJJJMMTTnn zu sein.)

Best Regards!
Chris

Post edited by: Prefect, at: 2009/02/26 02:59

Post edited by: Prefect, at: 2009/02/26 03:00<br><br>Post edited by: Prefect, at: 2009/02/26 14:34

i had a lot of issues with .nl domains. It is lots easier with non-country specific domains.

If you have a second IP on the same box, what I did was create a virtual interface (eth0:1) under webmin-networking-network configuration ->network interfaces. And under Host Adresses also use the ns1.domain.fr or whatever you have, next to the servers hostname.

Then add this (${DOM}. 38400 IN NS ns1.domain.fr.) to the server template under BIND DNS domain

If you have 1 IP the process is actually the same, but I dont know if your registrar will accept 2 nameservers on the same IP.
For a separate box I switched to Namecheap.com which would accept this.

Although the above worked for me for .nl domains, I did get a cheap VPS which acts solely as a (third) nameserver. So this ended all ‘confusing’ workarounds and no problems with any registrar.

i had a lot of issues with .nl domains. It is lots easier with non-country specific domains.

If you have a second IP on the same box, what I did was create a virtual interface (eth0:1) under webmin-networking-network configuration ->network interfaces. And under Host Adresses also use the ns1.domain.fr or whatever you have, next to the servers hostname.

Then add this (${DOM}. 38400 IN NS ns1.domain.fr.) to the server template under BIND DNS domain

If you have 1 IP the process is actually the same, but I dont know if your registrar will accept 2 nameservers on the same IP.
For a separate box I switched to Namecheap.com which would accept this.

Although the above worked for me for .nl domains, I did get a cheap VPS which acts solely as a (third) nameserver. So this ended all ‘confusing’ workarounds and no problems with any registrar.

i had a lot of issues with .nl domains. It is lots easier with non-country specific domains.

If you have a second IP on the same box, what I did was create a virtual interface (eth0:1) under webmin-networking-network configuration ->network interfaces. And under Host Adresses also use the ns1.domain.fr or whatever you have, next to the servers hostname.

Then add this (${DOM}. 38400 IN NS ns1.domain.fr.) to the server template under BIND DNS domain

If you have 1 IP the process is actually the same, but I dont know if your registrar will accept 2 nameservers on the same IP.
For a separate box I switched to Namecheap.com which would accept this.

Although the above worked for me for .nl domains, I did get a cheap VPS which acts solely as a (third) nameserver. So this ended all ‘confusing’ workarounds and no problems with any registrar.

i had a lot of issues with .nl domains. It is lots easier with non-country specific domains.

If you have a second IP on the same box, what I did was create a virtual interface (eth0:1) under webmin-networking-network configuration ->network interfaces. And under Host Adresses also use the ns1.domain.fr or whatever you have, next to the servers hostname.

Then add this (${DOM}. 38400 IN NS ns1.domain.fr.) to the server template under BIND DNS domain

If you have 1 IP the process is actually the same, but I dont know if your registrar will accept 2 nameservers on the same IP.
For a separate box I switched to Namecheap.com which would accept this.

Although the above worked for me for .nl domains, I did get a cheap VPS which acts solely as a (third) nameserver. So this ended all ‘confusing’ workarounds and no problems with any registrar.

i had a lot of issues with .nl domains. It is lots easier with non-country specific domains.

If you have a second IP on the same box, what I did was create a virtual interface (eth0:1) under webmin-networking-network configuration ->network interfaces. And under Host Adresses also use the ns1.domain.fr or whatever you have, next to the servers hostname.

Then add this (${DOM}. 38400 IN NS ns1.domain.fr.) to the server template under BIND DNS domain

If you have 1 IP the process is actually the same, but I dont know if your registrar will accept 2 nameservers on the same IP.
For a separate box I switched to Namecheap.com which would accept this.

Although the above worked for me for .nl domains, I did get a cheap VPS which acts solely as a (third) nameserver. So this ended all ‘confusing’ workarounds and no problems with any registrar.