1 Jun
2015
1 Jun
'15
12:52 p.m.
On 29.05.15. 22:49, Richard Chycoski wrote:
Here is a non-subdomained address:
> *aa6hf.ampr.org*
>
> Name: aa6hf.ampr.org
> Address: 44.17.0.128
> aa6hf.ampr.org mail exchanger = 10 aa6hf.ampr.org.
> aa6hf.ampr.org mail exchanger = 20 linux.aa6hf.ampr.org.
As I thought it is just matter of term definition. I use subdomain as
broad definiton of domain which is under some other domain.
By that definition this is subdomain. It is just hosted in the same DNS
as top level domain.
> *de.ampr.org nameserver = db0res.ampr.org.*
> de.ampr.org nameserver = db0fhn.efi.fh-nuernberg.de.
> de.ampr.org nameserver = ns.db0fhn.ampr.org.
> de.ampr.org nameserver = db0res.de.
I agree this is also subdomain.
The advantage of a delegated subdomain is that you can
update your
subdomain's DNS records without having to get someone else to do it.
The disadvantage is that someone must install, maintain, and operate a
DNS server.
Atually, there are few quite nice online DNS service that provide DNS
hosting for free.
http://afraid.org offers very simple user interface that allows anyone
with any knowledge of what domain is to set what he needs.
http://xname.org/ is full powered DNS server, also free. It does require
some advanced knowledge to set it up.
Thing is, when I asked to set ampr.org subdomain on my own DNS server,
it was refused. It was said that it is not allowed, and all subdomains
must be set on ampr portal.
My point is that prohibition should be removed. If one wants to set his
own DNS for subdomain he should be let to.
Pedja
YT9TP
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com