On 01.06.15. 20:25, Marius Petrescu wrote:
Allowing you to provide name services for ampr.org would mean you need to provide ALL name services for *.ampr.org, which is obviously not the case. And that restriction is valid and correctly applied and should NOT be removed (which is actually not possible btw).
The correct name servers are registered at the proper TLD, and seting an arbitrary other server would mean that anyone could alter the DNS for the domain, without asking anybody, potentially with malicious intent.
So the only option is to serve a subdomain, which means that e.g *.yt9tp.ampr.org, for which you need to provide a DNS and be proper delegated by ampr.org, without the possibility for you to alter the parent DNS..
Maybe we do not understand. I think it is perfectly valid to have for example
yt9tp.ampr.org. NS ns1.mydns.org. yt9tp.ampr.org. NS ns2.mydns.org.
That would allow me to adjust domain yt9tp.ampr.org and subdomains like
www.yt9tp.ampr.org ftp.yt9tp.ampr.org mail.yt9tp.ampr.org aprs1.yt9tp.ampr.org aprs5.yt9tp.ampr.org cluster.yt9tp.ampr.org sdr.yt9tp.ampr.org echolink1.yt9tp.ampr.org wifi.yt9tp.ampr.org
or other domains without further need to deal with ampr.org DNS server directly, but use my own.
Pedja YT9TP
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com