Adjacent and Non-Adjacent Domain

740 pts.
Tags:
Lotus Domino 7
Could you tell me anyone Adjacent and Non-Adjacent Domain works in within Single Domain with on different server or works on diff domains. I need complete help on this topic.

Answer Wiki

Thanks. We'll let you know when a new response is added.

<b>From Domino Help</b>

<b>Adjacent domain document</b> Used to restrict mail flow
Create an Adjacent domain document when you need to restrict the transfer of mail from one adjacent domain to another. The Adjacent domain document is one of the documents you create to set up Notes routing when the servers are not in the same Notes named network. Create an Adjacent domain document only if you need to specify restrictions. This document applies restrictions to messages routing from the Notes network to the adjacent domain. To prevent your servers from being used to transfer mail between other domains, you can selectively allow and deny mail routing through your domain to the domain named in the Adjacent domain document.

<b>Using Adjacent domain documents to restrict mail</b>
By default, a domain that can route mail to your domain can also route mail through your domain to another adjacent domain. When mail routes from one domain to another through your domain, it ties up your resources. To prevent your servers from being used to transfer mail between other domains, you can selectively allow and deny mail routing through your domain to the domain named in the Adjacent domain document.

The Allow and Deny fields on the Restrictions tab of the Adjacent domain document let you control the flow of messages from other domains to the adjacent domain. Entries in these fields must be the names of adjacent domains; the Router ignores entries for non-adjacent domains beyond the previous hop. If you deny a domain from sending mail through your domain, the Router denies all mail received from that domain, including messages the domain may have passed on from another, non-adjacent domain. There is no way to restrict specific users from routing to a Notes domain. Restrictions apply to all users in specified domain.

The settings in the Allow and Deny fields work in conjunction with the Allow and Deny fields on the Router/SMTP – Restrictions and Controls – Restrictions tab of the Configuration Settings document. In the event of any conflict between settings, Domino applies the most restrictive entry.
Messages may be further restricted by Adjacent Domain documents, Non-adjacent Domain documents, and Configuration Settings documents set up between domains along the routing path.

<b>Non-adjacent domain document</b> To Simplify mail delivery
Create a Non-adjacent domain document to control message routing to a non-adjacent domain. Non-adjacent domain documents serve three functions:
Specify a routing path to the non-adjacent domain by supplying next-hop domain information
Restrict mail from other domains from routing to the non-adjacent domain
Define the Calendar server used to enable free time lookups between two non-adjacent domains. For more information, see “Setting up scheduling” in the chapter “Setting Up Calendars and Scheduling.”

The Non-adjacent Domain document is used to specify a path between servers in two Notes domains that are connected by an adjacent domain. Create two Non-adjacent domain documents, one for each domain that is connecting to the intermediary domain.

U<b>sing Non-Adjacent domain documents to restrict mail</b>
Using Non-adjacent domain documents to simplify addressing makes them valuable enough. But Non-adjacent domain documents play another equally significant role. Although they are not strictly required to enable routing between non-adjacent domains, they are needed if you want to restrict routing of messages from certain domains.

By default, any domains that can route mail to your domain can also route mail to the destination domains named in a Non-adjacent domain document. Mail routed from one domain to another through your domain consumes your network resources. To prevent your servers from being used to transfer mail between other domains, you can selectively allow and deny mail routing through your domain.
The Allow and Deny fields on the Restrictions tab of the Non-adjacent domain document let you control the flow of messages from other domains to the non-adjacent domain. Entries in these fields must be the names of adjacent domains; the Router ignores entries for non-adjacent domains beyond the previous hop. If you deny a domain from sending mail through your domain, the Router denies all mail received from that domain, including messages the domain may have passed on from another, non-adjacent domain.
The “Deny mail from domains field” in a Non-adjacent domain document does not block messages that use explicit domain addressing, that is, addresses that explicitly name every domain on the routing path. A Non-adjacent domain document can only block mail that relies on information in the Non-adjacent domain document to supply the name of a a missing intermediate domain. If the entire routing path is contained in the recipient address, the Router doesn’t need to check the document to determine where to route the message, and thus cannot block it. For example, if in the previous example, the administrator in domain B creates a a Non-adjacent domain document for domain D and adds domain A to the Deny mail from domains field. Kathy Burke in domain A can still send mail to Judy Kaplan in domain D by specifying the following explicit domain address: Judy Kaplan@D@C@B.

To prevent Kathy Burke from sending this message, the administrator in Domain B would have to create an Adjacent domain document for domain C that names domain A in the Deny mail from domains field.
The settings in the Allow and Deny fields work in conjunction with the Allow and Deny fields on the Router/SMTP – Restrictions and Controls – Restrictions tab of the Configuration Settings document. In the event of any conflict between settings, Domino applies the most restrictive entry.

Messages may be further restricted by Adjacent Domain documents, Non-adjacent Domain documents, and Configuration Settings documents set up between domains along the routing path.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following