Problem using DNS Slave Auto-Configuration

6 posts / 0 new
Last post
#1 Sun, 07/20/2008 - 18:38
petar.j

Problem using DNS Slave Auto-Configuration

I'm using Virtualmin GPL a few months for testing purposes and I tried various combinations just to get used the features and get familiar with the interface. Now I want to use it in production.

First, let me explain the infrastructure that I have:

I have a separate machine with firewall software with public IP addresses from ISP. There is a NAT with port forwarding to two servers in DMZ zone with private IP addresses. One server is ns1 (Virtualmin) as hosting and primary BIND server, and the other one is ns2 (Secondary BIND server with Webmin).

Public IP addresses (ISP): ns1: x.y.z.55 ns2: x.y.z.56

Private IP addresses: ns1: 192.168.x.1 ns2: 192.168.x.2

I'm having a small problem with creating a new Virtual Server.

I followed the "DNS Slave Auto-Configuration Quickstart" guide. "Default master server IP for remote slave zones" is configured with public IP address for ns1.

I also used the "Operating Virtualmin Behind a Firewall" section from "Virtualmin Administrator's Guide". "Default IP address for DNS records" is configured with public IP address for ns1.

When I try to create a new Virtual Server I get an error:

Failed to create virtual server: A slave DNS zone cannot be created until a default master IP address has been specified in the server template (in the Plugin options section)

Ok, I followed the explanation and I configured the "Default slave zone masters" option in Plugin section in Default Template with the Public IP address for ns1.

I tried again to create a new Virtual Server and now there is a different error:

Failed to create virtual server: Both the slave and master DNS zone features cannot be enabled for the same domain.

I know how to configure a slave dns server manually and not to use the "DNS Slave Auto-Configuration", but using it is much faster.

Could someone explain me, what I'm doing wrong :)

Thanks

Mon, 07/21/2008 - 02:32
ronald
ronald's picture

What is the point of having a slave nameserver on the same location?
Why not use the 2 public IP's on 1 server? and use the second server for instance as a failover.
just wondering

Mon, 07/21/2008 - 12:18 (Reply to #2)
Joe
Joe's picture

As ronald mentioned, it makes no sense to run two name servers on the same host--if the host goes down, you lose name service anyway.

Just run a second IP, and add the additional name server on the Server Template BIND page.

--

Check out the forum guidelines!

Sun, 06/07/2009 - 07:27
petar.j

Good point Ronald and Joe :)

I know that from the beginning, thatâ

Sun, 06/07/2009 - 07:27
petar.j

Good point Ronald and Joe :)

I know that from the beginning, thatâ

Sun, 06/07/2009 - 07:27
Joe
Joe's picture

<div class='quote'>I&acirc;

--

Check out the forum guidelines!

Topic locked