Re: [44net] Bad MX records in the ampr.org DNS

It is normal for you to be refused. 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.. Marius, YO2LOJ -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of YT9TP - Pedja Sent: Monday, June 01, 2015 19:53 To: AMPRNet working group Subject: Re: [44net] Bad MX records in the ampr.org DNS ... 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