Virtual server url not working

14 posts / 0 new
Last post
#1 Sun, 04/19/2009 - 10:35
daniorama

Virtual server url not working

Hello, I'm new with virtualmin and it seems I forget some steps doing this. I just installed the GPL version of virtualmin in a Debian5 server.

I can access virtualmin without problems and I create a virtual server, it seems everything works ok, but I just cannot access it by its url.

I restarted apache, checked the DNS and use whois, host and dig, everyone seems ok but when I enter the url it just says "server not found" but when I use the "preview website" option in virtualmin I see the site.

I really don't know what is going on and how can I solve it. Any help? Thanks

Sun, 04/19/2009 - 10:39
andreychek

Hmm, is there any chance you could post the domain name in question, as well as the IP address it sits on?

With that, we could do some troubleshooting and hopefully nail down a cause. It could be a case of two DNS servers returning different information, for example, but I'd need to know the domain in order to figure that out :-)

Also, when you installed, did you install using the install.sh script?

Thanks,
-Eric

Sun, 04/19/2009 - 23:45 (Reply to #2)
Malouk

Hello,

I had the same problem after the last update packages.

After a new installation, the problem is still present

Mon, 04/20/2009 - 05:42 (Reply to #3)
daniorama

Those are the nameservers I always use for my dedicated server. Before webmin I used GNUPANEL and the urls worked without problems.

I used http://www.squish.net/dnscheck/ and I got many "time out" when they check KS367726.KIMSUFI.COM

The nameservers on my domains are all:
KS367726.KIMSUFI.COM
NS.KIMSUFI.COM

They are ok, and they worked always. It seems it has to be something in virtualmin or webmin. I really do not know what is going on. Neither webmin or virtualmin show problems. What should I check then?

I would like to use webmin rather than GnuPanel but I do not know how to fix this. Thanks

Mon, 04/20/2009 - 05:53 (Reply to #4)
andreychek

Well, something is wrong with the DNS service running on those nameservers.

I'm seeing the timeouts as well.

That probably means one of:

1. Firewall software (either on the server, or perhaps on a router in front of your server) is blocking UDP port 53

2. BIND isn't running for some reason

I would start there. You could also try restarting BIND, and then look in the messages log to see if any errors show up.
-Eric

Mon, 04/20/2009 - 06:23 (Reply to #5)
ronald
ronald's picture

Domaintools find both those domains on 94.23.13.135 so your settings at the registrar look okay.
intodns (which checks your box) cant find your nameservers.

KS367726.KIMSUFI.COM:
One or more of your nameservers did not respond:
The ones that did not responded are:
94.23.13.135

NS.KIMSUFI.COM (slave?)
ERROR: looks like you have lame nameservers. The following nameservers are lame:
213.186.33.199

Your hostfiles aren't correct I'd say

Mon, 04/20/2009 - 06:29 (Reply to #6)
ronald
ronald's picture

hm i can connect to any port except 53 and 5353. firewall blocking or bind not running is also a good hint.

Mon, 04/20/2009 - 08:01 (Reply to #7)
daniorama

mmm... binds seems to be up (both virtualmin and ssh say so) also I do not know how could I have a firewall, the server was totally clean, I just installed virtualmin with the script. How can I check the firewall? Is any installed with the GPL version of Virtualmin?

ns.kimsufi.com is a secondary DNS that my server provider gave me, and it worked with other Panels I had.

I updated the bind9 modules but I see no changes. I have no ideas...

Mon, 04/20/2009 - 08:38 (Reply to #8)
ronald
ronald's picture

under webmin - networking is a module for tthe linux firewall.
in the top you need
Accept If protocol is UDP and destination port is domain
Accept If protocol is TCP and destination port is domain

under webmin - servers - BIND DNS Server, stop bind and start it again from there. then look in the messages log to see if any errors show up.

Sun, 06/07/2009 - 07:52 (Reply to #9)
daniorama

Well, there was no errors with bind and port 53 was open. In other forum, someone told me this:

delete this on /etc/bind/named.conf.options:
listen-on { 127.0.0.1 };
and add this at the end:
listen-on { any; };
allow-query { any; };

and IT WORKS! I have no idea why, do you anything about how and why this worked? Thanks!

Sun, 06/07/2009 - 07:52 (Reply to #10)
daniorama

Well, there was no errors with bind and port 53 was open. In other forum, someone told me this:

delete this on /etc/bind/named.conf.options:
listen-on { 127.0.0.1 };
and add this at the end:
listen-on { any; };
allow-query { any; };

and IT WORKS! I have no idea why, do you anything about how and why this worked? Thanks!

Mon, 04/20/2009 - 03:15
daniorama

I have created 4 virtual servers. You can try any of these urls:

daniorama.com
alivelarp.com

The public_html dirs are empty, but at least I should see a forbidden error and not just "not found". It's also noticeable that the browser takes a relative long time to show the error (10-20s)

I used the install.sh script. This is the second time I installed it. The first time something weird happened, at first just some of the urls were working, but the next day none of them worked, so I decided to format the server, install and create the virtual server with virtualmin again, but now none of them work.

The server is an OVH one, and the IP is 94.23.13.135

I also saw that there is an update available to bind9 modules but I updated in my first installation and it didn't improve anything, should I update them?

Thanks

PS: it seems I posted this issue twice, my apologies.

Mon, 04/20/2009 - 04:33 (Reply to #12)
andreychek

It looks like the nameserver assigned to your domain isn't returning your desired IP addresses.

For example, the nameservers listed for daniorama.com are KS367726.KIMSUFI.COM and NS.KIMSUFI.COM.

They aren't returning information about daniorama.com, however (and in fact, the first nameserver doesn't seem to be returning at all).

So you need to look into your nameserver settings and make sure it's pointing at the correct server/IP for that.
-Eric

Mon, 04/20/2009 - 15:06
andreychek

Ahh... so, BIND was configured to listen only locally. What you changed it to caused it to listen for all requests, not just local ones.

Glad you got it!
-Eric

Topic locked