Novell Home

My Favorites

Close

Please to see your favorites.

GWIA load balancing using DNS

(Last modified: 17Jun2003)

This document (10084245) is provided subject to the disclaimer at the end of this document.

goal

GWIA load balancing using DNS

fact

Novell GroupWise 5.5 EP

Novell GroupWise 6

Novell GroupWise 6.5

Novell GroupWise Internet Agent (GWIA)

symptom

GWIA is constantly busy processing inbound messages

Delay receiving inbound mails

fix

Using the DNS server MX Records with different preference ranking, you can have some form of load balancing and redundancy option.

For example, the registered domain name is abc.com and you have 3 GWIA gateways, 2 for incoming and 1 for outgoing

In the DNS MX Record table, there will be these entries :
abc.COM preference = 10 mail exchanger = gwia1.abc.com
abc.COM preference = 15 mail exchanger = gwia2.abc.com
abc.COM preference = 10 mail exchanger = gwia3.abc.com

What this means is that mail sent to any user @abc.com will be delivered to "gwia1.abc.com" or "gwia3.abc.com" first as the preference weighting for both is 10, if both of those gateways are unavailable, then it will delivered to "gwia2.abc.com".

In Gw 5.5 with Internet Addressing enabled, you can have system level GWIA and domain level GWIA. Domain GWIA always override system setting. So for outbound mail you can specific which GWIA is to be used for which domain.

Normally DNS settings are handled by an ISP so check with your ISP for this

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10084245
  • Solution ID: NOVL90304
  • Creation Date: 16Jun2003
  • Modified Date: 17Jun2003
    • NovellGroupware

Did this document solve your problem? Provide Feedback