Indeed both dig commands failed here. If one of those domains still works in the browser, it’s only due to cached IP addresses. You need to check and fix your BIND zones first.
Thanks for the replies.
I went to Virtualmin > Webmin > Servers > BIND DNS Server > Existing DNS Zones > Zone > domain1.com > Check Records > results seems good with: No errors were found in the records file /var/named/domain1.com.hosts and /var/named/domain2.com.hosts.
Virtualmin > System Settings > Re-Check Configuration > needed to add 127.0.0.1 to DNS servers.
Virtualmin > Terminal > /etc/httpd/httpd.conf had little data and no logs to check.
Virtualmin > Terminal > /var/log/virtualmin > access and error logs for website.
Virtualmin > System Settings > Virtualmin Configuration > Configuration category: Network settings > Default IP address for DNS records: Automatically detect external address > Save > System Information.
Virtualmin > Webmin > Servers > BIND DNS Server > Existing DNS Zones > Zone > domain1.com > domain1.com NS - Name Server > DNS record details > Name server DNS name: (changed from localhost.localdomain. to) www.domain1.com. > Save.
Virtualmin > Webmin > Servers > BIND DNS Server > Existing DNS Zones > Zone > domain1.com > domain1.com NS - Name Server > DNS record details > Create Record of Type: NS - Name Server > Create Record of Type > DNS record details > Record name: Same as domain: www.domain1.com > Name server DNS name: ns2.domain1.com > Create.
To do any tests from my end here, I’d need to know the actual domain names and server IP addresses in question. Trying to debug an issue like this by “remote guessing” is not optimal.
Thanks, but I don’t have any money to pay for paid support.
I prefer to keep the information public on this forum for those interested in advancing technology and knowledge.
I will try the virtualmin irc, so the domain name isn’t on this forum.
Thanks, however luck is not needed.
Just fellow virtualmin forum people to work with each other to develop the software.
So, virtualmin BIND DNS server settings seem correct with nameserver 1 and nameserver 2 and A record pointing to WAN IP address. Registrat has nameservers 1 and 2 pointing to the WAN IP. How can I check the registrar is really pointing to the WAN as Locutus said the registrar is pointing to an incorrect IP address of 128.237.157.136?
“Developing the software”? You’re rather expecting free support on a very complex level here, your problems have nothing to do with Virtualmin “development”.
Ok, same issue happening again after following the Virtualmin wizard and creating a top level server and a sub-level server. intodns.com says this:
Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For ns1.domain.tld the parent reported: [‘xxx.xxx.xx.xxx’] and your nameservers reported: [‘192.168.1.145’, ‘xxx.xxx.xx.xxx’]
For ns2.domain.tld the parent reported: [‘xxx.xxx.xx.xxx’] and your nameservers reported: [‘xxx.xxx.xx.xxx’]
The domain registrar points domain1.tld to virtualserver1’s IP.
The domain registrar points domain2.tld to ns1.domain1.tld.
Ok, Virtualmin configuration works on virtualserver1, but not on virtualserver2. The DNS settings, template etc appear as per Virtualmin documentation.
The DNS troubleshooting loads virtualserver2 only when running command $ host domain2.com publicWanIP, the correct results appear.
But command $host domain2.com says: Host domain2.com not found: 3(NXDOMAIN)
Ok, taking a closer look at /var/named/domain1.hosts and /var/named/domain2.hosts and /var/named/domain2.hosts does not have
ns1.sk8parks.org.au. IN A xxx.xxx.xx.xxx (public WAN IP)
ns2.sk8parks.org.au. IN A xxx.xxx.xx.xxx (public WAN IP)
ns1.sk8parks.org.au. IN A xxx.xxx.x.xxx (LAN IP)
So, I can manually add these lines into /var/named/domain2.hosts, however why doesn’t Virtualmin add these in when creating a 2nd website?
Ok, taking a closer look at /var/named/domain1.hosts and /var/named/domain2.hosts and /var/named/domain2.hosts does not have
ns1.sk8parks.org.au. IN A xxx.xxx.xx.xxx (public WAN IP)
ns2.sk8parks.org.au. IN A xxx.xxx.xx.xxx (public WAN IP)
ns1.sk8parks.org.au. IN A xxx.xxx.x.xxx (LAN IP)
So, I can manually add these lines into /var/named/domain2.hosts, however why doesn’t Virtualmin add these in when creating a 2nd website?