Domain
|
Zone Editor
Our Zone Editor enables you to add, remove, and change resource records for your domain name in real time, as long as one of our nameservers is used for a domain name.
It is also possible to choose your own TTL (time to live) for the whole zone file and set special TTL-values for single records.
The graphical user interface of our zone editor makes it easy to edit resource records, even for non-technicians.
As special gadget for technicians we have implemented a text-only mode in our zone editor. This mode shows the whole zone-file in BIND-notation and enables you to fast export or import large zone-files. Needless to say, input in text-only mode is checked for syntax-errors, before zones are written into our nameservers.
The SOA-record (Start of Authority) is automatically generated, based on the nameservers given for your domain-name. Thus SOA-records are automatically configured correctly. 
Supported Types of Resource Records
A
Address record which redirects a (sub-)domain to any IPv4 address. Also known as IP-Pointing.
AAAA
Address record which redirects a (sub-)domain to any IPv6 address. Also known as IPv6-Pointing.
CNAME
Record which redirects a (sub-)domain to another domain-name.
DNAME
Record which redirects a (sub-)domain to another domain-name. In addition to a CNAME-record the DNAME-record also provides the capability to map an entire subtree of the DNS name space to another domain. This type of resource record is rarely used in practice.
Please see RFC 2672 for details.
MX
Specifies a mail server responsible for accepting email messages for a respective domain-name. It's possible to create several MX-records and weight them (priority) to increase the likelihood that emails may be delivered. In practice most of the domain-names have only one MX record.
NAPTR
Extends the functionality of the common A-records by protocol-specific information. Please see RFC 2915 for details.
NS
Delegates a zone to use the given authorative nameservers.
RNAME
Email-address of the zone-administrator.
SRV
Used to publish information about 'newer services' (like XMPP, LDAP, etc.) which are available for a domain-name.
TXT
Is used to publish human-readable information via DNS. In practice it is commonly used to post SPF-specific information (Sender Policy Framework) and DomainKeys (DNSsec).
|