Re-Check License

Submitted by wewer on Wed, 08/28/2013 - 13:31

In Virtualmin (Systeminformation) i get the message: "Failed to contact licence server : Failed to lookup IP address for software.virtualmin.com A renewal can be purchased at http://www.virtualmin.com/shop"

When I press "Re-Check License" I get the message:

.. a problem was detected : Failed to contact licence server : Failed to lookup IP address for software.virtualmin.com

Status: 
Active

Comments

Submitted by andreychek on Wed, 08/28/2013 - 13:40

Howdy -- it sounds like there's a problem with your nameservers.

What are the contents of your /etc/resolv.conf file?

Submitted by wewer on Wed, 08/28/2013 - 14:27

Thanks for quick response!

The contents are:

nameserver 127.0.0.1 nameserver 192.168.168.91

Submitted by andreychek on Wed, 08/28/2013 - 14:45

Hmm, I suspect one of those two nameservers isn't online at the moment, or is experiencing some kind of problem.

What I would try is to edit your /etc/resolv.conf file, and to comment out this line:

nameserver 192.168.168.91

Once you comment out that line, restart your own BIND service with this command:

/etc/init.d/named restart

After that, what output do you receive if you run this command:

host software.virtualmin.com

If that produces an IP address, then it appears to be working! At that point, try Re-Checking the license and see if that works now.

Submitted by wewer on Wed, 08/28/2013 - 16:57

I get the messages:

connection timed out; trying next origin connection timed out; no servers could be reached

Submitted by wewer on Wed, 08/28/2013 - 18:48

When I use the Google-Nameserver 8.8.8.8 then it produce the message:

software.virtualmin.com has address 108.60.199.107

It seems to be working but the error "Failed to contact licence server : Failed to lookup IP address for software.virtualmin.com" still exist.

Submitted by andreychek on Wed, 08/28/2013 - 19:05

Hmm, it sounds like BIND isn't working properly, for some reason.

Have any changes been made recently to the BIND configuration?

Also, when you restart BIND, does it claim to start up properly?

What output does this command produce:

netstat -an | grep :53

Submitted by wewer on Thu, 08/29/2013 - 03:39

Hi,

no changes have been made recently to the BIND configuration. I’m not very firm in Linux. So I doesn’t change anythink because I don’t know how :-(

I think the Bind-Restart don't work propertly (see screenshot src )

The netstat-result you can see in netstat.jpg. The address 192.168.122.x is unknown to me

Submitted by andreychek on Thu, 08/29/2013 - 04:51

Ah, I think I see the problem there -- what is "test.maikepiel.de"? Is that a Virtual Server on your system?

It appears as if that domain has a DNS zone file, but that zone file doesn't contain all the necessary records that a DNS zone requires.

If that is a Virtual Server, and you don't need it -- you could try deleting it.

Or, if you aren't using the DNS feature for that domain, you could go into Edit Virtual Server -> Enabled Features, and disable the "DNS Domain" feature.

If you want to be able to use it, you could disable that feature, then re-enable it.

Submitted by wewer on Thu, 08/29/2013 - 05:36

After disable the virtual server "test.maikepiel.de" and restart BIND all works fine.

Thanks a lot for your great support.

Bye, Bodo

Submitted by andreychek on Thu, 08/29/2013 - 08:16

I'm glad your DNS issue is resolved!

Regarding Bugzilla -- we're happy to help! Could you open up a new Support Ticket for that though? It helps us out to keep different topics in separate tickets. Thanks!

Submitted by wewer on Thu, 09/05/2013 - 18:26

Sorry, now I have the problem again:" Failed to contact licence server : Failed to lookup IP address for software.virtualmin.com"

With command "host software.virtualmin.com" i get an valid IP-Address.

Restart BIND start up without errors

With "netstat -an | grep :53" I get:

tcp 0 0 192.168.168.172:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN tcp 0 0 :::53 :::* LISTEN udp 0 0 0.0.0.0:5353 0.0.0.0:* udp 0 0 192.168.122.1:53 0.0.0.0:* udp 0 0 192.168.168.172:53 0.0.0.0:* udp 0 0 127.0.0.1:53 0.0.0.0:* udp 0 0 192.168.122.1:53 0.0.0.0:* udp 0 0 :::53 :::*

:-(

Submitted by andreychek on Thu, 09/05/2013 - 18:33

What is the output of this command:

cat /etc/resolv.conf

Submitted by andreychek on Thu, 09/05/2013 - 19:24

It sounds like there's a problem with the nameserver being used now... since 127.0.0.1 isn't one of the listed nameservers, your BIND configuration doesn't actually matter -- it may just be having problems contacting 8.8.8.8 for some reason.

You may want to try an alternate nameserver to use in your /etc/resolv.conf to see if that resolves the issue you're seeing.