Coyote Point Systems Equalizer Spezifikationen PDF herunterladen (Seite 515)

3. Configure the authoritative DNS server for your website’s domain with DNS records for all Equalizers in the

GeoCluster. The DNS server returns these records to clients in response to DNS requests to resolve the

website (GeoCluster) name.

DNSConfiguration

Every Web site is assigned a unique IP address. To access a website, a client needs to know what the site IP

address is. Users don't usually enter an IP address into their Web browser, but rather enter a site's domain name

instead. In order to access a requested website, a Web browser needs to be able to convert the site's domain

name into the corresponding IP address. This is where DNS comes into play.

1. A client computer is configured with the address of a preferred DNS server.

2. A requested URL is forwarded to the DNS server, and the DNS server returns the IP address for the

requested website.

3. The client is then able to access the requested site.

Local (Caching) DNSServer

In a typical GSLB configuration a local, or caching DNS server resides in the client's LAN environment. When the

client directs the browser to get to a URL (i.e., www.coyotepoint.com) the browser requests the local DNS to

resolve the name (i.e. www.coyotepoint.com) to an IP address. Once local DNS server resolves the name to an ip

address. It will first check a root name server, which returns a list of name servers for, say, the

.com

domain. The

name servers for the domain name space return the IP addresses of an Authoritative DNS server for the domain

name. Finally, the Authoritative DNS for the domain name returns the IP address of the web server, or in Envoy

SAE, the FQDN of a GeoCluster. For each GeoCluster to be balanced, an Authoritative Name Server must be

configured to return name server and alias records for Envoy SAE’s at every regional site

Configuring an Authoritative DNSName Server for Envoy

You must configure an Authoritative DNS Name Server(s) for the domains that are to be geographically load

balanced to delegate authority to the Envoy sites. You need to delegate each of the fully-qualified subdomains to

be balanced. If your DNS server is run by an Internet Service Provider (ISP), then you need to ask the ISP to

reconfigure the DNS server for Envoy. If you are running your own local DNS server, then you need to update the

DNS server’s zone file for your Envoy configuration.

This is usually the last step performed when configuring Envoy. It is recommended to set up Envoy and test your

Envoy configuration thoroughly before making changes on the authoritative name server.

For example, assume you must balance www.coyotepoint.com across a GeoCluster containing two Envoy sites,

east.coyotepoint.com (at 192.168.2.44) and west.coyotepoint.com (at 10.0.0.5). In this case, you must configure

the name servers that will handle the coyotepoint.com domain to delegate authority for www.coyotepoint.com to

both east.coyotepoint.com and west.coyotepoint.com. When queried to resolve www.coyotepoint.com,

coyotepoint.com’s name servers should return name server (NS) and alias (A) address or glue records for both

Envoy sites.

515

Equalizer Administration Guide

1 2 ... 510 511 512 513 514 515 516 517 518 519 520 ... 593 594

Keine Kommentare

Coyote Point Systems Equalizer Spezifikationen Seite 515