Failed to contact licence server: failed to look up ip address for software virtualmin

Submitted by paulfromsurrey on Thu, 07/28/2011 - 23:40 Pro Licensee

getting error on main server

Failed to contact licence server: failed to look up ip address for software virtualmin

2nd hot server seems to fine

Please help

Status: 
Active

Comments

Submitted by andreychek on Thu, 07/28/2011 - 23:53

Howdy -- what output do you get if you run these two commands on your server:

host software.virtualmin.com
host google.com

Submitted by paulfromsurrey on Fri, 07/29/2011 - 00:01 Pro Licensee

how to run these command

can you access the server remotely and fix the issue or give me some direction how to check and fix it

Submitted by andreychek on Fri, 07/29/2011 - 09:15

If you have an SSH client such as Putty, you can access the SSH service on your server, and use that to run those two commands.

You can log in as the user "root".

Submitted by paulfromsurrey on Fri, 07/29/2011 - 20:47 Pro Licensee

Here is the out put

[root@NS1111 ~]# host google.com Host google.com not found: 5(REFUSED) [root@NS1111 ~]# host software.virtualmin.com Host software.virtualmin.com not found: 5(REFUSED)

Thanks Paul

Submitted by andreychek on Fri, 07/29/2011 - 20:53

Okay, it looks like DNS for your server isn't working.

What output do you receive if you run this command (which you can do by logging into your server as root over SSH):

cat /etc/resolv.conf

Also, is this server a VPS, or a dedicated server?

Submitted by paulfromsurrey on Wed, 08/03/2011 - 08:26 Pro Licensee

I ran the command in ssh

; generated by /sbin/dhclient-script nameserver 192.168.0.1

can you please fix this for me plz

Submitted by paulfromsurrey on Wed, 08/03/2011 - 08:31 Pro Licensee

this is stand alone server

Submitted by andreychek on Wed, 08/03/2011 - 09:37

It looks like your server is setup to use DHCP. Whenever it retrieves it's IP address from the DHCP server, that's causing it to overwrite the DNS server listed in /etc/resolv.conf.

In your case, it doesn't seem like that particular DNS server is working.

Here is where I'd start --

If you log into Virtualmin, click Webmin -> Networking -> Network Configuration -> Hostname and DNS Client.

Where it says "DNS Servers", remove the entry for "192.168.0.1", and in it's place, add "127.0.0.1".

Once you do that, click "Save".

Those steps tell your server to use it's own DNS server for performing DNS lookups.

Once you do those steps, are you able to run the "host software.virtualmin.com" command that didn't work previously?

Submitted by paulfromsurrey on Wed, 08/03/2011 - 09:57 Pro Licensee

bash command did not found

i also restarted the server no luck

Now re-checking your Virtualmin license .. .. a problem was detected : Failed to contact licence server : Failed to lookup IP address for software.virtualmin.com

Submitted by andreychek on Wed, 08/03/2011 - 09:58

Well, that's unusual, the command ran successfully a few days ago when you tried it, it just wasn't able to do a DNS lookup.

However, adding "127.0.0.1" to Webmin as described above should resolve the problem you're having.

There's one other step we need to do to make sure things continue to work moving forward -- what Linux distribution and version are you using?

Submitted by paulfromsurrey on Wed, 08/03/2011 - 10:05 Pro Licensee

when i added the 127.0.0.1 under dns server

it is not saving

it id keep going back to 192.168.0.1

plz advice

i am using centos

Submitted by Locutus on Wed, 08/03/2011 - 11:26

Did it revert to 192.168.0.1 right away, after you edited the file? Or after the next reboot?

If the former, then maybe saving the file failed due to access rights. How did you edit the file, using which program?

If the latter, then like Eric said it might be the DHCP client that keeps reverting the resolv.conf. A method to prevent that which usually works well (even if it'd be better to go a different route first, like disabling DHCP if possible) is making the file "immutable":

chattr +i /etc/resolv.conf

You can revert this change in case of problems with

chattr -i /etc/resolv.conf

Submitted by paulfromsurrey on Wed, 08/03/2011 - 11:35 Pro Licensee

i edited the file

resolve.conf

now when i run the enquiry it works ok

but still have message on my licence

Submitted by Locutus on Wed, 08/03/2011 - 11:39

What message exactly are you getting? And did you try what I suggested/asked in my previous post? Otherwise you might run into the same problems again after the next reboot.

With an incorrectly configured resolv.conf, more and nastier things will go wrong than a failed license validation. :)

Submitted by paulfromsurrey on Tue, 08/23/2011 - 20:52 Pro Licensee

Hello Jammie and Team

I am having the same issue and issue is ongoing

getting alot of issue with emails stuff like that captcha stop working bcz of dns

i change the setting add 127.0.0.1 but it goes back to 192.168.0.1

plz let me know how i can fix this issue

Thanks Paul

Submitted by paulfromsurrey on Tue, 08/23/2011 - 20:52 Pro Licensee

Hello Jammie and Team

I am having the same issue and issue is ongoing

getting alot of issue with emails stuff like that captcha stop working bcz of dns

i change the setting add 127.0.0.1 but it goes back to 192.168.0.1

plz let me know how i can fix this issue

Thanks Paul

Submitted by paulfromsurrey on Tue, 08/23/2011 - 20:52 Pro Licensee

Hello Jammie and Team

I am having the same issue and issue is ongoing

getting alot of issue with emails stuff like that captcha stop working bcz of dns

i change the setting add 127.0.0.1 but it goes back to 192.168.0.1

plz let me know how i can fix this issue

Thanks Paul

Submitted by andreychek on Tue, 08/23/2011 - 21:00

Hi Paul -- two fixes for that issue are available in the first section of this document here:

https://www.virtualmin.com/documentation/dns/faq

I suspect your issue is related to the DHCP server overwriting the DNS settings, and either of the two fixes listed in there should resolve your problem.

Submitted by JamieCameron on Tue, 08/23/2011 - 23:44

I added the line :

supersede domain-name-servers 127.0.0.1;

to /etc/dhclient-eth0.conf .. that should fix the issue.

Submitted by paulfromsurrey on Wed, 08/24/2011 - 22:19 Pro Licensee

I still have this issue

Submitted by andreychek on Wed, 08/24/2011 - 22:26

What issue are you still having specifically, the issue where your /etc/resolv.conf reverts to "192.168.0.1"?

If so, you could always try making your resolv.conf file "immutable".

First, reset your nameserver to be "127.0.0.1".

Then as root, run this command:

chattr +i /etc/resolv.conf