NOT FOUND biz domains bug?

9 posts / 0 new
Last post
#1 Sat, 02/28/2009 - 08:18
pronisis.com

NOT FOUND biz domains bug?

Hello:

I have a problem I have Virtualmin 3.66 gpl installed in a vps with ubuntu 8.04. Everything works fine...

But all the biz domains have problems... I received a "Could not connect to remote server" error, all the other domains with .com, .net, .in, etc. extensions Don't have problems only the domains with biz extension.

I don't know if I made a mistake or if this is a bug.

Can you help me with this problem.

Thank you,

Best regards,

Victor

Sat, 02/28/2009 - 09:21
andreychek

Hi Victor,

Do you think you could offer an example of a .biz domain that's not working, as well as a .com domain that does work?

The .biz domains should work fine, I have one setup on my server here. So with the info above, I'll do some checking on the DNS settings and such to see if I can figure out what's not working correctly.
-Eric

Sat, 02/28/2009 - 22:16 (Reply to #2)
pronisis.com

Hello Eric & Joe:

Thank you for all your help!!!

I can tell you that I don't touch the DNS information, also I have the same problems with a new virtualmin installation.

For example the domains:

pronisis.com
b-global.net
bolet.in

Works fine!!!

But all the domains with biz extension like:

meshima.biz
avaluos.biz

Have problems!!!

Other thing I made an email account:

test@meshima.biz

and this email account can receive and send emails, then I don't know why the web server can not find this address!!!

I don't know if this will be a nameserver problem, but if this is a nameserver problem I'll have problems whit the emails, but the server can handle the emails. Do you know how to know if this is a problem of the domain registration company?

Thank you for all your help.

Best regards,

Victor.

Sun, 03/01/2009 - 04:49 (Reply to #3)
andreychek

Okay, so, all of your glue records (the "nameserver" fields in your registrar) seem to have something odd going on with them.

The glue records being used for meshima.biz and avaluos.biz don't resolve -- you'll need to make sure any DNS records you're using are created in Services -> DNS Domain.

The glue records for pronisis.com resolved on one system I tested from, but not the other.

So you'll need to go through and make sure all the nameserver addresses you're attempting to use are all setup properly.
-Eric

Mon, 03/02/2009 - 08:28 (Reply to #4)
pronisis.com

Hello Eric:

Thank you for all your help!!!

I don't know why, but at the beginning I use the same nameserver for all the domains, and work fine, but with the biz domains I always receive an error. I change the nameservers of avaluos.biz and now this domain works good.

Eric, thank you for all your help, you are really a good person.

Have an excellent day.

Best Regards,

Victor

Mon, 03/02/2009 - 13:05 (Reply to #5)
ronald
ronald's picture

seems there are a few things left to fix
---------
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!
pronisis.com
---------
Error
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.pronisis.com
ns2.pronisis.com
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).
---------
Stealth NS records were sent:
pronisis.com
---------
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:
NS3.avaluos.biz
NS4.avaluos.biz
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).
---------
I cannot reach avaluos.biz. Gives an invalid controller...
---------
The SOA record is:
Primary nameserver: pronisis.com

this doesn't look like a correct nameserver. should be ns1.pronisis.com ?

Mon, 03/02/2009 - 13:07 (Reply to #6)
ronald
ronald's picture

this is the url coming back

<div class='quote'>http://pronisis.com/pronisis_com/default/index</div>

Wed, 03/04/2009 - 11:33 (Reply to #7)
pronisis.com

Hello ronald:

Thank you very much for all your help!!!

I'll check all the nameservers.

Yo fix this problem.

Thank you,

Best Regards,

Victor.

Sat, 02/28/2009 - 10:07
Joe
Joe's picture

As Eric mentioned, Virtualmin has no problem with .biz (or any other TLD). Virtualmin doesn't care what the TLD is--it doesn't even know what a TLD is. They are all just names to Virtualmin. (You could even make up your own TLDs, and assuming you had local DNS infrastructure for it, they would work fine--not for the outside world, but within your local network. I do this for testing.)

Have you gone through the &quot;Troubleshooting Common Problems&quot; guide in the Documentation section? There's also a guide for troubleshooting DNS problems in the Webmin wiki here:

http://doxfer.com/Webmin/BINDTroubleshootingTools

I suspect you have misconfigured glue records at your registrar, but without knowing the domain we can't confirm that (but you can, using the tools discussed in the docs).

--

Check out the forum guidelines!

Topic locked