Your search returned no hits.
95% of all problems already have a solution in our knowledgebase
Added: 10.03.2014 23:26:29 Last updated: 11.06.2017 14:42:24
This guide details how to proceed to make changes to the zone file for a domain which uses our name servers via DNS control. The guide assumes that you have already logged in to the client portal for your customer number.
Click on "Domains", as shown in the screenshot below.
Find the domain (dittdomene.net in our example) and click on "DNS control".
On this page the whole zone for the domain is listed, and you have access to add new records, change current ones, as well as delete records/listings.
When you open DNS control for your domain, you will see "Add new record" over the records in the zone file. In this example we will add a record for a subdomain for dittdomene.net.
The new record we have added will be shown like in the picture below.
If you try to add a new record, but it does not show up under DNS control, you have made a mistake when writing it. You should always check that the listing is correct after adding a new and/or made changes in existing listings. It could also be a good idea to compare existing records when adding a new one.
Explanation of types of records:
Every line in DNS control makes up a record. There are several kinds of records. The different records that can be used in DNS control are given with an explanation below.
TTL is Time To Live and specifies how long the record can stay saved on computers online before the record must be checked for updated data. The time is specified in second. 14400 (4 hours) is the standard value for TTL in records in zone files on our name servers.
The most common type of record. Points names towards a 32-bit IPv4 address.Example
We want www2.dittdomene2.com to point towards IP 18.104.22.168. We add the following data and record these:
Alias of one name to another.Example
We want xxx2.dittdomene2.com to point towards www2.dittdomene2.com. We add the following data and record these:
Notice how there is a dot at the end of the data field. This has to be present for the record to be valid.
Specifies where email for the domain should be delivered.Example
We want all email to dittdomene2.com to be delivered to server by the name mail.dittdomene2.com. We add the following data and record these:
Notice how there is a dot at the end of the data field. This has to be present for the record to be valid. The field Priority specifies where it should try to deliver email first if there are more than one MX record. Lowest value is tried first.
|AAAA||Points name towards a 128-bit IPv6 address.|
We want www3.dittdomene2.com to point towards IPv6 2001:db8:1f70::999:de8:7648:6e8. We add the following data and record these:
|NS||Delegates the zone to make use of set authorative name server.|
Our zones are set up with the name servers ns1.proisp.no and ns2.proisp.no. If we add for ns1.proisp.no, the following data will be added:
|TXT||record originally made for human readable data, but has gradually gone over to computer readable data. Used for SPF (which has become its own record) and DomainKeys, among other things.|
We want to add a certain DomainKey. We add the following data and record these:
Notice the quotation marks around the text in the Data field. These has to be present for the record to be valid.
|SRV||Generalized server localization record used for newer services instead of protocol specific records like MX.|
Look here for example and explanation of SRV records.
We have now been through how to make changes in the zone file for a domain name via DNS control.