Hi guys, sorry for all of the posts...i have a lot to absorb. After much ado, i finally have a set of servers in place and would like to use this thread to go through my setup ironing out any potential problems you guys can see before i install WHMCS and go live (selling online hosting).
I have the following servers
host1 (Virtualmin Pro, 1 vcpu, 1.7 BG RAM, ephenumeral ip) ns1 - primary name server (virtualmin GPL, 1 vcpu, 0.6GB RAM, static IP) ns2 - secondary nameserver (Webmin, 1 vcpu, 0.6GB RAM, ephenumeral IP)
I am going to steer clear of email for now all servers will eventually be static ip addresses but for now i feel that at least ns1 must be static unless i dont use my own nameservers, which in that case i would change the static ip over to hosting server.
First things are first...I am not entirely sure about my hosts files on these machines. The configuration on all of them follows this format...
127.0.0.1 localhost.localdomain localhost
127.0.1.1 host1.mydomain.com.au host1
"my external ip" host1.mydomain.com.au host 1
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
169.254.169.254 metadata.google.internal metadata
Questions..........................
Are the first two lines ok?
"169.254.169.254 metadata.google.internal metadat" at the bottom seems to cause problems with my BIND configuration? Can i remove this metadata (it is automatically inserted by my google cloud platform when i install a new instance. Should i change it to to something else?
First two lines are fine. The addition of 127.0.1.1 has some interesting side effects, but shouldn't break anything, as long as your DNS is right.
"169.254.169.254 metadata.google.internal metadat" at the bottom seems to cause problems with my BIND configuration? Can i remove this metadata (it is automatically inserted by my google cloud platform when i install a new instance. Should i change it to to something else?
I'm not sure what that has to do with BIND. This isn't a BIND configuration file, and BIND doesn't read it. What specific error are you seeing?
And, no, you don't need to remove it. If it's ending up in the BIND configuration file, we need to sort out why, and correct the Virtualmin configuration to use the right values. Virtualmin auto-detects the hostname of the system for the first DNS NS record and configures all domains hosted on the system to use that as the first NS (by default), but I'm not sure how it would choose that as the hostname of the system. It really seems like "hostname -f" ought to return host.mydomain.au, rather than that metadata bit.
--
Check out the forum guidelines!
when you say 127.0.1.1 has interesting side affects, what are they?
As i wish to use this with WHMCS for autoprovisioning of services to clients, is there a likely problem with this configuration? Is there a better way?
https://ajecreative.com.au