and sofar, so good. However, at “DNS / Nameserver setup”, the very last line; “To make these active, click “Apply Zone” on the top-right”.", I get this error:
NDC command failed : rndc: connect failed: 127.0.0.1#953: timed out
How do I proceed? As in, how do I solve this? Tried google but didn’t get much wiser.
Thanks!
edit:
hmm, just found out can’t ping either on the machine, did work before installing virtualmin. So what could have caused this?
well, i restored the default iptables thing from the server and then it worked. What didn’t work, was virtualmin, but with a rule i once asked for on here I got that working too.
Another question; when the server was delivered, it had a default system hostname, which i couldn’t change yet as the domain name that I reserved for it was still not available for a few hours.
So, I followed the steps here: From Zero to Awesome: A Common-Sense Guide to Virtualmin Installatio and everything seems to work.
However, I get this:
Glue is not provided by your nameservers. This means they did not provide the IP address of your nameservers, so an extra step may be required to resolve your domain. The following nameservers did not have glue:
As far as I understand the warning, it wants your nameservers to have A records for the hostnames that are listed as NS for the domain. To make sure we’re talking about the same thing and so that I can do some diging: can you re-iterate which domain is the one in question, as in the one you’re hosting and trying to resolve?
the domain I’d like to be the main one is: penghosting.nl
So sites with nameservers ns1.penghosting.nl and ns2.penghosting.nl are sent to the server. Would be nice if it would be called something with penhosting.nl in stead of server88-208-193-145.live-servers.net.
I guess the best would be to set the system hostname in Webmin to the actual external one you wish to use now, then check the Server Template -> BIND DNS Domain in Virtualmin that it is set to use the system’s hostname as primary nameserver, and then turn the feature “DNS Domain” off and on again so that it creates new zonefiles.
Otherwise you can manually fix the zones too of course.
I did that, yesterday, but I still get these errors, so I guess I must have missed something somewhere:
Missing nameservers reported by parent FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems! server88-208-193-145.live-servers.net
Missing nameservers reported by your nameservers ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns1.penghosting.nl
ns2.penghosting.nl
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
Check out Webmin -> Servers -> BIND DNS Server -> -> Type: All and see what is listed as “NS” records there.
If that’s the “server88…” thing, then you still have the incorrect hostname somewhere in your Virtualmin config, possibly the Server Template -> BIND DNS Domain.
“Master DNS server hostname Automatic (from system’s hostname)”
there, so I’m now off to see if somehow the ‘system hostname’ is still the old one. If not, I guess I have to go into each server and change this master dns server hostname.
FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems! server88-208-193-145.live-servers.net
Missing nameservers reported by your nameservers
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns1.penghosting.nl
ns2.penghosting.nl
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
Maybe I should look into this tomorrow, as it’s almost 1:30 and i’m becoming too tired.
Hmm, in penghosting.nl “edit records file” I found this:
$ttl 38400
penghosting.nl. IN SOA ns1.penghosting.nl. lex.peng.nl. (
1294151142
10800
3600
604800
38400 )
@ IN NS server88-208-193-145.live-servers.net.
penghosting.nl. IN A 88.208.193.145
www.penghosting.nl. IN A 88.208.193.145
ftp.penghosting.nl. IN A 88.208.193.145
m.penghosting.nl. IN A 88.208.193.145
localhost.penghosting.nl. IN A 127.0.0.1
webmail.penghosting.nl. IN A 88.208.193.145
admin.penghosting.nl. IN A 88.208.193.145
mail.penghosting.nl. IN A 88.208.193.145
penghosting.nl. IN MX 5 mail.penghosting.nl.
penghosting.nl. IN TXT "v=spf1 a mx a:penghosting.nl ip4:88.208.193.145 ?all"
ns1.penghosting.nl. IN A 88.208.193.145
ns2.penghosting.nl. IN A 88.208.193.146
So that server88 thing is still there…
Driving me mad now.
Any idea how to change this ‘globally’ or should I just do it in here?
“ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns2.penghosting.nl
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).”
