On 6 Feb, 07:30, Stephane M <Steph...@M.com> wrote:
> shimmyshack a écrit :
>
>
>
> > On 6 Feb, 00:36, Stephane M <Steph...@M.com> wrote:
> >> Hi,
>
> >> I think that I am close to the solution, but would beed some
>
> >> To sum up : Iam using Apache 2.0.... on CentOS v 4.4
>
> >> I am using an Name based Virtual host
>
> >> NameVirtualHost *:80
>
> >> <VirtualHost *:80>
> >> ServerNamewww.aa.tld
> >> ServerAlias aa.tld *.aa.tld localhost
> >> DocumentRoot /www/aa
> >> </VirtualHost>
>
> >> <VirtualHost *:80>
> >> ServerNamewww.bb.tld
> >> ServerAlias 192.172.x.y
> >> DocumentRoot /www/b
> >> </VirtualHost>
>
> >> Now, I have edit my Network card
> >> -----------------
> >> DNS : localhost.localdomain
> >> Primary DNS <Modem/Router IP address>
> >> ...
> >> DNS search path : localdomain
>
> >> --------------------
> >> And into Host
>
> >> <Server IP address> (Name server :www.aa.tld) (Alias : aa.tld)
> >> <Server IP address (Name server :www.bb.tld) (Alias : bb.tld)
>
> >> So now, on my WebServer machinewww.aa.tldandwww.bb.tldwork fine !!!!
>
> >> BUT, if I am on another machine, this is the mess
> >> -www.aa.tld-> seems to be OK
> >> -www.bb.tld-> go and displaywww.aa.tld(soseems to be lost )
>
> >> I suppose, that I have a DNS problem ?
>
> >> - Do you think, that what I've done is correct ?
>
> >> Thanks for your
>
> >> Stephane
>
> > by "on other machine" you mean another machine on the LAN,
> > again you must adjust this machines hosts file to point to the IP
> > address of the cent OS machine on the LAN running apache.
>
> > The basic theory is that
>
> > on LAN all requests for the domains must point to the server LAN IP
> > when out in the real world away from your LAN, the public DNS records
> > will point to you external router, which then forwards the ports onto
> > the LAN IP.
>
> > So you must either
> > *configure each internal machine's hosts file to map the domains to
> > the internal IP of your server,
> > or
> > *configure each machine to get its DNS from a LAN DNS server which has
> > its A record for that domain pointed at the internal LAN server.
>
> > If you can set up a LAN DNS server this method is easier as it
> > requires no manual modification for each LAN workstation hosts file.
>
> Hi,
>
> Thanks for that,
>
> But how can setup correctly the DNS for machines from outside my LAN ?
> I just re-direct the IP address from my Domain name provider.. is that
> enough ?
>
> Do I need to change it's DNS ??
>
> That's I don't know
>
> Thanks for your
>
> Stephane

OK, just change the A record to your public IP of the router that
protects your LAN from the internet.
Yes using the control that your hosting company, or domain name
registration company provide.


That will be enough unless you have not got a static IP from your ISP
for the public router.
If you have a dynamic IP address, then the DNS will have to keep on
changing, but obviously this isnt possible so instead use a company
like dyndns.com set up an account there, and then tell your router
what your dyndns.com details are.

Then whenever someone requests your domain name at dyndns they will
tell them what your IP is, (and your router keeps track of your
changin IP and lets dyndns know every 10mins or so)

The best thing is of course to have a static public IP address and
simply change the A record for your FQDN

One more thing you can do if you are going to start sending emails
from your server, change the rDNS (if your ISP allows this) to the
FQDN that you are going to send the emails from, (the same as the one
people will be suing to see your website)