|
How to use the DNS Zone Editor
Domain names, or DNS servers, use so-called records to convert (host)names into IP addresses to locate what you want to find. If for instance you want to browse to http://www.google.com a DNS server is needed to convert the name www.google.com into an IP address so your browser client knows where to go to. This simple record uses an A record.
For mail servers a different type of record is needed. If you send mail to bill@microsoft.com then the DNS server is queried for an MX (Mail eXchanger) record. This MX record should give at least one (host)name to where mail should be deliverd. This (host)name should then again have an A record to know its IP address.
The DNS service at www.public-servers.com
As soon as you have at least one domain added to our webinterface you may edit/add DNS records (be sure that the registred DNS server from your domain do point to at least 2 of our nameservers (NS01.WARP3.COM, NS02.WARP3.COM or NS03.WARP3.COM).
If you selected the 'default' template several sample records will already exists.
These records include 2 NS records (pointing to our nameservers), an MX record (needed for mail forwarding), an URL record to show an example of URL redirection and several A records that are needed to resolve the (host)names used in the sample config to their IP addresses.
Setting up URL redirection
The following setup shows how to redirect http://www.yourdomain.com to http://web.someisp.com/~myname/site. Asuming you have already added your domain via the user-interface you first need to have an A record for www.yourdomain.com that points to the IP address of our web-redirector (83.98.163.41). You then need to setup an URL (URL Redirection) record with the correct value of the destination site (http://web.someisp.com/~myname/site).
In the record list it will then show like:
www.yourdomain.com A 83.98.163.41 86400
www.yourdomain.com URL http://web.someisp.com/~myname/site 86400
Similair to this, if you wish to setup a frame redirection record, it will show as:
www.yourdomain.com A 83.98.163.41 86400
www.yourdomain.com SURL http://web.someisp.com/~myname/site 86400
This will use frames to redirect your pages, also often known as cloacked redirection or stealth forwards.
Setting up MAIL redirection
Much like the URL redirection, but you need to add an MBOXFW (Mail Forwarding) record and. A total of 3 records is needed. First of all the MX record need to point to mail.yourdomain.com to specify the mail server. Secondly an A record so that the MX can be resolved to an IP address (83.98.163.41). And third the MBOXFW record as explained above.
In the record list it will then show like:
mail.yourdomain.com A 83.98.163.41 86400
yourdomain.com MX mail.yourdomain.com 50 86400
user@yourdomain.com MBOXFW user@someisp.com 86400
Anti Virus and Spam Checking
Once a mail has been received that needs to be forwared, it is checked for virusses by our McAfee antivirus engine. Prior to this it is filtered through our spam detection software. We first use a so-called Spam Repellent by making incoming SMTP connection be placed on hold for a short time. Most spam-sending software won't like this waiting and will disconnect. We check for SPF Records as well as Microsoft's caller ID to try and determine if the incoming connection is valid.
We then use SpamAssassin and SpamEliminator, as well as some often used keywords, to reject detected spam messages.
Fallback MX (commercial service)
To use the fallback MX server, a second record for MX should be present, and then with a higher value for the priority. In the control panel, you just need to insert the domain name to submit it. It can't be any more simple.
An example of a correct setup, using the domain name example.com:
example.com. MX mail.example.com 50 86400
example.com. MX mx2.warp3.com 100 86400
Secondary DNS (commercial service)
In order for your own nameserver to send the correct NOTIFY to our nameservers there are a few simple configuation options needed.
- Your primary nameserver should be set as primary in the SOA record.
- Your nameserver needs to be configured to send updates (notifies) to its slaves.
- The IP and FQDN name of your primary DNS server (the one sending the notify) should be known to us.
Note: do not add the domain manually to 'My Domains' else the domain can not be created/set for secondary DNS.
It is recommended that your primary nameserver is running BIND or PowerDNS (mainly for your own convenience). We have thoroughly tested the following (authorative) nameservers that work correctly with our secondary DNS service:
- BIND v9
- PowerDNS 2.9.20+
- djbdns 1.05
Example DNS records if your domain would be called: example.com.
example.com. 2560 IN SOA ns01.example.com. postmaster.example.com.
1198762444
7200
2048
1048576
21600
example.com. 172794 IN NS ns01.example.com.
example.com. 172794 IN NS ns02.example.com.
ns01.example.com. 172622 IN A 100.200.300.400
ns02.example.com. 172622 IN A 83.98.163.40
In here, your own (primary) DNS server, the ns01.example.com, is specified in the SOA record, and has an A record of 100.200.300.400 (change this to your own IP address offcourse). The ns02.example.com record here is listed only with an NS record, and is therefor a slave, or secondary, DNS server. Its IP is here is 83.98.163.40. This is important. To use our secondary DNS service, you may choose 83.98.163.40, 82.98.163.23 or 83.98.163.43 (or any combination if you like). Finally, you need to add your master DNS server through the webinterface here at public-servers.com with your real addresses (from this example, it would be 100.200.300.400 and ns01.example.com).
You do NOT need to add the domain within out webinterface in public-servers.com, it will be picked up automaticly the first time you are sending a NOTIFY to our service.
Important: Be sure you use the correct IP address if your server has multiple network interfaces or virtual addresses. Unless you can tell your DNS server to specify what IP address it needs to use for outgoing notify's, you need to add your default outgoing network cards IP address.
| 
