 |  |
Pardon my denseness, but I have a few follow up questions. I will admit
Re: Need setup help
From: Dennis J. Bonsall, Jr.
Date: Wednesday, November 17, 1999
Time: 11:15:00 pm
that
I never did read the recommended book listed in your docs, so my
apologies if
my questions are basic and something everone should know...
> This won't work, because mail.webbuilders.com is a CNAME alias. You
> can't use a CNAME alias in an MX record - it must point to a name
> that has an A record. Solutions: Either give mail.webbuilders.com an
> A record (instead of the CNAME), or use www1.webbuilders.com in the
> MX record.
Can I assign multiple A records to a single IP, such as assigning both
www1.webbuilders.com and mail.webbuilders.com as individual A records
both
pointing to 207.239.220.201? I had assumed that an A record was, in
effect,
simply a "name" for each individual IP address.
> These load balance records have two problems:
>
> 1) They only point to one host. This means that the load isn't
> balanced between multiple hosts, which makes these records pointless
> (though harmless). This could be solved by giving them more
> addresses, after you're sure everything else works right.
At the current time, until I have everything working (which includes
getting
WebCatalog code updated on all my sites), I am only load balancing a few
domains at a time, just to see what all changes I need to make. At
current,
I do not want my domain name (webbuilders.com) to load balance. I put
these
records in to stop the DNS server from reporting that the machines were
not
load balanced, and ignoring the timing pulse from the WebStar plug-in.
If I
do eventually give these hosts (www1 and www2) load balancing between
each
machine, will this cause someone who accesses www1.webbuilders.com to
randomly hit either server?
> 2) There are A records of the same name in the domain file. Because
> of the way we've implemented load balance records, you can't have
> both. Solution: remove the A records for both www1 and www2. CNAME
> records pointing to www1 will still work.
So I would use the load records as the only record to reference www1 and
www2? I do not need an A record for each IP?
> >amsoilsales.com. CNAME
> >www.webbuilders.com.
>
> No good. You can't have a CNAME record that has the same name as
> anything else. In this case, you have a CNAME record with the same
> name as your NS and MX records; won't work.
What should I name the records? Does it matter? Do I even need to have
NS
records for each domain, other than my domain (webbuilders.com), as long
as I
have load balancing records for each domain?
> In order to have an address associated with a second-level domain
> (i.e. amsoilsales.com), you need to use an A record.
Do I need an A record for each domain file, or will a load balancing
record
suffice?
> >www.amsoilsales.com. CNAME www.webbuilders.com.
> >amsoilsales.com. Load Hosts: 2
>
> You can't have a load balance record with the same name as the
> domain. This is merely a consequence of the way we've implemented
> load balance records, and it's something you just have to work around.
Again, does it matter what the name of the record is? Will it work with
whatever I name it?
> The solution to not being able to get to your web site without "www"
> on the front of the domain name is to add an A record to each domain,
> of the form:
> domain.com. A 192.168.0.1
>
> where you replace the name and the address with the correct values.
> Unfortunately, these names (without the "www") cannot be load
> balanced.
Will it work if I create 2 load balancing records, one with the www, and
one
without?
Thanks for your assistance,
Dennis
Messages In This Thread:
Return to Digital Point Solutions' Home Page