Hjælp til Branded Senders DNS Delegation???

Hej Aminoer

Vi er i gang med at få lavet 4 branded senders hos Emailvision igennem vores udbyder Surftown.

Men vi kan ikke finde ud af hvordan dette gøres korrekt. Emailvision har lavet en guide som Surftown ikke forstår og Emailvision giver ikke support på dette område.

Er der nogen der er haj til dette og måske allerede har erfaring med hvodan dette gøres.

Jeg smider også lige guiden her:

I – Introduction
This document explains how to set-up the DNS entries for branded link-tracking URLs and for
branded senders.
This document contains technical information. The addition or removal of any character
(including but not limited to spaces, line breaks, commas or dots) may result in incorrect
and/or unusable configuration. It is highly recommended that non-technical personnel do not
copy-paste parts of the document, but forward it entirely.
When the sample names presented here are replaced with the actual named used in
production, special attention needs to be paid to the presence or absence of a trailing dot at
the end of each name. They will have to be preserved ( e.g. : example.com. translates to
client.com. - with a trailing dot; and example.com translates to client.com – without a trailing
dot)

II – Definitions
· DNS Zone : An entry point in the DNS configuration. It contains information concerning
one or several DNS Names
· DNS Name : Any name that can be resolved to an IP address using the DNS
· Top-Level Domain : .com, .net, .org, .info (and other similar names in use) and .XX or
.YY.XX names delegated to national organisations (e.g.: .fr, .de, .co.uk, .org.uk, .be, .us,
….)
· Domain : a DNS name, usually child of a Top-Level Domain (e.g.: Emailvision.com,
Emailvision.net). A domain is generally configured within its own DNS zone.
· Sub-domain : a DNS name, usually child of a “domain” (e.g.: news.emailvision.com).
Information concerning a sub-domain can be configured within it the parent zone or within
its own zone, in which case delegation is necessary.
· Client DNS servers : servers serving the client’s DNS zone. They may be operated by the
client itself or by a DNS hosting service (usually a service offered by registrars of Top-
Level Domains of web-hosting companies).
Please note that the difference between “domain” and “sub-domain” is only “cosmetical”,
technically there is no difference between the two. They are both DNS names.
As examples the following names will be used:
- example.com – client’s main domain.
- common.example.com – name used for both link tracking and as e-mail sender
- common – the left-most part of the previous name, ending at the first dot
They will have to be replaced with the actual names to be used by the client.
When the term clientname is used, that will need to be replaced with the client name, as
provided (and validated) by Emailvision TechOps.
Client Documentation
Client Document p4/4

III – DNS Delegation
The DNS name common.example.com will be used for both link tracking and as e-mail
sender. That name must be delegated to the Emailvision DNS servers.
Emailvision clients are reminded that as of June 2009, DNS delegation is a contractual prerequisite
for sender and URL branding.
In order to perform DNS delegation, the following steps must be followed on the DNS servers
that control the example.com zone (either registrar’s DNS management service or the
client’s own DNS servers):
1. Ensure that the example.com DNS zone does not contain any entry for
common.example.com (neither as common nor as common.example.com. ).
If there are any existing entries, they have to be removed before continuing.
2. Ensure that there is no DNS zone named common.example.com. configured on
the client’s DNS servers. If there is such a DNS zone configured, it must be removed
from the DNS servers configuration before continuing.
3. Check once again, on all the nameservers authoritative for example.com that
conditions 1. and 2. are met (no existing entries or DNS zone)
4. Add the following entries in the example.com DNS zone :
$ORIGIN example.com.
common IN NS a.ns.emailvision.net.
common IN NS b.ns.emailvision.net.
common IN NS c.ns.emailvision.net.
common IN NS d.ns.emailvision.net.
5. Do not add any other DNS names or zones named common.example.com or
ending in .common.example.com

IV – Miscellaneous Information
1. The full DNS name used (for either links or sender) should not be larger than 64
characters in length.
2. Domain name renewal is the responsibility of the client unless Emailvision is the
registrant of the domain.
3. Campaign Commander is reliant on the DNS entries being correct and the client must
ensure that no changes are to be made to the agreed DNS entries without prior
testing and approval by Emailvision.
4. Emailvision does not brand with the client’s main domain ( example.com ). Clients
must not delegate their main domain to Emailvision.