Re: OT: DNS Records

On 21/10/05 8:26 am, in article dja581$jq2$1@xxxxxxxxxxxxxxxxxxxxx, "Richard
Watson" <tinnedmeat@xxxxxxxxxxxxxxxx> wrote:

> Andy Jacobs wrote:
>
>> 1. Load balancing - albeit in a non controllable way. i.e. half the
>> visitors go to ns.domain1.com and half go through ns.domain2.com. (Maybe
>> not half, but 'some' proportion)
>
> Yes, that would be too far back really. If you wanted to do something
> similar to load balancing you would create an A record for the www host
> with more than 1 IP number.
>
>> 2. Redundant - ns.domain1.com is down so requests go to ns.domain2.com
>
> DNS always works in this kind of way. It's one of the good things about it.
>
>> And what about e-mails? Could you get a case where an e-mail lands in
>> the popbox on the backup server and the client can't pick it up until
>> his machine decides to take the route to the second machine?
>
> Well of course you can have a separate host for the mail as well that
> doesn't change.
>
> I don't really understand what you're trying to achieve. DNS fails over
> automatically. Nothing else will fail over unless you put something in
> place to make it so. DNS doesn't have a priority like MX records do, so
> to the outside world there isn't a primary and secondary, only 2 equal
> name servers.
>
> One way to fail over would be to have a shortish TTL on the www record
> so that if something went down you could update the DNS and fail over to
> the secondary host.

Just to illustrate my fear, take the example of a database driven site using
a CMS. The client logs into www.mydomain.com/cmsadmin, hits server a and
makes some changes. The database gets updated. A visitor comes along and
views the site but doesn't see the updates as the random element means that
they end up hitting server b and don't see the changes, or vice versa.

I think the upshot is that it ain't gonna work :o)

Andy

.

Relevant Pages

  • Re: Windows 2000 file/AD problem - urgent
    ... effect where other services dependent on it subsequently fail as well. ... > This is my File/Print server and Domain Controller with DNS. ...
    (microsoft.public.win2000.general)
  • Re: DNS resolution not working
    ... Also noticed that these computers that fail to lookup, ... So 4 computers fail to look up a dns record for one specific server, ... DNS is working, as nslookup works from the affected pcs. ...
    (microsoft.public.windowsxp.network_web)
  • Re: user Authenication question
    ... We have a site that has a domain controller which serves as GC, DNS, ... Maybe the file server could be better moved ... NO FAIL or WARN messages when run locally on that DC. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2K3 revDNS problem
    ... Does it work for any forward query and fail on any reverse query? ... DNS server primary for any reverse zones? ... I have a strange problem with DNS service. ...
    (microsoft.public.windows.server.dns)
  • Re: OT: DNS Records
    ... > Andy Jacobs wrote: ... > DNS always works in this kind of way. ... So we have server a and server b. ... server a would ALWAYS be the primary server and server b would only come ...
    (uk.net.web.authoring)