Subservers do not resolve anymore

7 posts / 0 new
Topic locked
Last post
#1 Sun, 01/02/2011 - 19:18
Tortoise

Subservers do not resolve anymore

After the update of virtualmin and webmin I noticed that all subservers I have except for one do not resolve anymore. I do not know if it is related to this update because I simple did not check them recently before it.

I noticed that one of the subservers still works (staging.baasjesvoorbaasjes.nl). I created a fresh one to compare it with (tmp.vrijgezellenfeest.nl). That one however does not work.

The only special thing about staging.baasjesvoorbaasjes.nl is that it has a non-default webroot. However besides that I can not find anything that might be causing this.

Please give me some directions for me where to look for solving this problem.

Much thanks.

Sun, 01/02/2011 - 19:22
andreychek

Howdy,

If your domains aren't resolving, that sounds like a DNS issue of some sort... that would mean either something is awry with the DNS records hosted on your server, or the nameservers for your domain(s) aren't setup as expected.

You may want to start by getting a report for your domain over at intodns.com to get an idea of what's going awry... it may help point you in the right direction.

-Eric

Sun, 01/02/2011 - 19:31
Tortoise

Hi,

Thanks for the quick reply.

Intodns.com gives me for staging.baasjesvoorbaasjes.nl (functional subdomain) the response: Can't get nameservers at parent server!
I only check domains not subdomains!

However for tmp.vrijgezellenfeest.nl I get a response: ERROR: looks like you have lame nameservers. The following nameservers are lame: 109.74.195.149 178.79.144.139 SOA record No valid SOA record came back! MX Error MX Records Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers! WWW Error WWW A Record ERROR: I could not get any A records for www.staging.vrijgezellenfeest.nl!

I do not know why it gives me a response for one of them and not the other one. My conclusion would be that is not recognised as a subdomain.

Mon, 01/03/2011 - 06:35
Locutus

I did some digging here.

Firstly, the webroot has nothing to do with name resolution and can't be the cause for problems.

What I found out so far:

The netherlands NIC lists this as responsible nameservers for vrijgezellenfeest.nl.

vrijgezellenfeest.nl.   7200    IN      NS      ns2.archytas.nl.
vrijgezellenfeest.nl.   7200    IN      NS      ns1.archytas.nl.
;; Received 83 bytes from 194.171.17.2#53(ns3.nic.nl) in 16 ms

According to the responsible nameserver, ns1.linode.com, the address of ns1.archytas.nl is 109.74.195.49.

Querying this nameserver gives me:

;; ANSWER SECTION:
vrijgezellenfeest.nl.   38400   IN      A       109.74.195.149

Since a nameserver is also responsible for all its subdomains, your tmp should also be resolved by 109.74.195.49. When querying the address for tmp.vrijgezellenfeest.nl. @109.74.195.49, I only get NS records, no A record, which is incorrect. Either the query should return an A, or an NXDOMAIN error.

Consequently, trying a recursive query results in a SERVFAIL. A TRACE for tmp.vrijgezellenfeest.nl. results in an endless loop and a "BAD REFERRAL" error.

Now we need further information from your end what the involved IP addresses and hostnames are, which of those are under your control and how your BIND is configured. You should check the zone file(s) in question, and possibly BIND error logs.

Thu, 01/06/2011 - 20:58 (Reply to #4)
Tortoise

Thanks for your response.

I was wondering, is 109.74.195.49 a typo for 109.74.195.149 in your message. Otherwise where did you get this from?

Fri, 01/07/2011 - 04:11
Locutus

I'm quite sure it was no typo... To retrieve that A, I first looked up the responsible nameservers for "archytas.nl" by doing dig archytas.nl. NL +trace. The Netherlands NIC told me that those are "ns1.linode.com" to "ns5.linode.com".

And a dig ns1.archytas.nl. @ns1.linode.com returned, back then, 109.74.195.49.

Although, now, it returns 109.74.195.149. It is possible that the operators of "linode.com" had a typo there and fixed it meanwhile. So you might try your issue again if it is resolved by now. :)

Fri, 01/07/2011 - 08:33
Tortoise

I found the error, for some reason for new subdomains the following was added:

subdomain IN NS mynameserver

which adds recursion since tmp.vrijgezellenfeest.nl has its A record in the same hosts file. Now I should find out which Virtualmin/Webmin settings do add these records to the hosts file, so that it won't happen when I create a new subserver.

Topic locked