-------------- > https://virtualmin.com/node/44970
OK, I Think I figured this whole thing out and Now I have run into a glitch.
When I do the bind, I get error
Adding (SERVER IP) .. Server (SERVER IP) is not running Webmin version 1.202 or above.
This is not true, I tested this with the newest version of webmin only and with the newest version of Virtualmin,
How can I bypass this so It will ignore this confusion?
Well I think I got it, just gotta wait for new propagation to check.
The above issue was related to firewall not having both TCP and UDP ports open for the range of 10001 - 10010, Only having UDP for the connection of said ports doesn't work and causes to flag the error for the wrong version check. So had to open both.
I may still be lost on a few things, But we shall see after propagation.
As it stands for now. In godaddy, I have the nameserver IPs pointed to the respective Server locations for each dns.
In webmin, I have the servernames on each server set to dns.domain.com and dns2.domain.com to match what I have in godaddy.
I have the servers binded together with bind and dns2 is the slave to dns1.
All of that is functioning.
Shouldn't be much more , will update.
This does not seem to be working, when I use DNSCHECKER.ORG
The dns2 is showing up as dns1 in the check for NS (nameservers) Does anyone know if that's normal?
Not sure why.. Although it is showing the ip address for DNS2 if I check the A record for DNS2.
Going to give it more time before I fiddle with it.
Was a port problem causing the issues with propagation.
TCP and UPD port 53 needed opened for NEW connections, didn't realize DNS needed this port.
I think I am in the clear, websites are starting to propagate now.
READ THIRD COMMENT