Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: janhein on April 02, 2005, 11:28:29 AM
-
Hello,
I have set two domain names on my e-smith box.
One is my primary domain. (www.primary.nl)
The second is an virtual domain (www.virtualdomain.nl)
At my dns provider I set the two domain names to my ip number of my e-smith box.
When I call the primary domain from my internal network and the internet I see the website of the primary domain. That is correct.
When I call the virtual domain name from my internal network I see the website of my virtual domain. That is correct. But when I call the virtual domain name from the internet I see the website of my primary domain. What is not correct.
I made all the settings on the e-smith box right. My virtual domain is linked to the i-bay of my virtual wedsite. All the settings are good.
Is this a problem of my dns provider or is it an problem of my e-smith box?
Thanks
Jan Hein
-
janhein
Sounds like you have done everything correctly.
> I made all the settings on the e-smith box right. > My virtual domain is linked to the i-bay of my
> virtual wedsite. All the settings are good.
Where did you set this and what are the settings you made. Just checking to see if you did it correctly.
-
This is wat I have done:
- I created an i-bay cald "country"
- Made all the settings so that you can connect from the internet.(group = "everyone" , file sharing = "write/read = group" , public access = "entire internet (no password)")
- In the domains section I created an virtual domain "virtualdomain.nl". and linked it to the "country" ibay.
These are the settings on my e-smith box.
- At my dns provider I linked my domain "www.virtualdomain" to my external ip number.
I think this is the right way to do it, but I still see my website of my primary domain.
When I call My "vitualdomain.nl" from my internal network it is working. Onley when I call it from the internet, I see my "primarydomain.nl".
Just asking? Has it something to do with "wildcart" settings at my dns provider. I can not make any chanches that has something to do with "wildcart". If so, is there an other way to solve the "wildcart" problem?
Jan Hein
-
I did some testing more.
I created on my e-smithbox "subdomain.virtualhost.nl" and linked it to an i-bay.
At my dns provider I made an dns with the same subdomain and linked is to my same external ip number.
When I cal the url on the internet it cals the good i-bay.
Why does "subdomain.virtualhost.nl" work and "virtualhost.nl" calls my primary domain?
Jan Hein
-
janhein
I think the general answer is that if you setup a specific domain to point to your server be it
www.mydomain.nl
or
sub.mydomain.nl
then you have to have a specific virtual domain configured on your server that exactly matches the external domain entry record.
Someone else had this same problen recently, they wrongly assumed what you have also.
-
Can you please explane more.
At my webserver and at my dns provider are the sub and domain names the same. Can you tell me what I can do wrong?
Please help?
Jan Hein
-
I did some testing.
I created at an free domain hosting site "virtualdomain.tk", and linked it to my external ip number.
At my e-smith box I also created the virtual domain "virtualdomain.tk", and linked it to the right i-bay.
When I call the name from my internal network it shows the right site. But when I call it from the internet I also see my primary site.
So I think it is not the problem at my dns provider, but it is an problem of e-smith.
I also made an second e-smith box with version 6.5. I created everything the same as on the original. It also made the same mistakes.
It is making me sad. At the forum are people that had the same problem. Do you know howe the users solved the problem.
For your info I use SME Server 6.0.1-01.
Jan Hein
-
janhein
I thought you said you got it working in an earlier post ?
"When I cal the url on the internet it cals the good i-bay."
I have a number of virtual domains on my server and they work fine, just point your external dns record to the full domain URL.
Also use the full virtual domain name in the Domains panel.
If you can access your virtual domain locally then your server would appear to be setup correctly, that suggests your dns record or name is the problem.