10.3. MX and NS records The domain name used as the value of a NS resource record, or part of the value of a MX resource record must not be an alias. Not only is the specification clear on this point, but using an alias in either of these positions neither works as well as might be hoped, nor well fulfills the ambition that may have led to this approach. This domain name must have as its value one or more address records. Currently those will be A records, however in the future other record types giving addressing information may be acceptable. It can also have other RRs, but never a CNAME RR. Searching for either NS or MX records causes "additional section processing" in which address records associated with the value of the record sought are appended to the answer. This helps avoid needless extra queries that are easily anticipated when the first was made. Additional section processing does not include CNAME records, let alone the address records that may be associated with the canonical name derived from the alias. Thus, if an alias is used as the value of an NS or MX record, no address will be returned with the NS or MX value. This can cause extra queries, and extra network burden, on every query. It is trivial for the DNS administrator to avoid this by resolving the alias and placing the canonical name directly in the affected record just once when it is updated or installed. In some particular hard cases the lack of the additional section address records in the results of a NS lookup can cause the request to fail.
I will take a look when I get to the office.
Sadly IPv6 records are manual at the moment, and its entirely possible its a typo.
Paul
Leo Vegoda <leo.vegoda@icann.org> wrote:
Hi,
On 1 Sep 2013, at 07:08, Jonathan Spence <jonathan.spence@power-business.co.nz> wrote:
Hi everyone,
Google have just started enforcing PTR records for IPv6 addresses delivering to Gmail. Our IPv6 works great with Orcon but having serious issues getting delegation back to our nameservers setup. I have been told a few times that everything is setup on their end but I don't think it is.
Our IP space: 2400:4800:4017::/48 is meant to be sent to ns1.power-business.co.nz and ns2.power-business.co.nz. However it doesn't seem to.
The reverse domain for 2400:4800:4017::/48 is 7.1.0.4.0.0.8.4.0.0.4.2.ip6.arpa. Your supposition is correct and ns1.orcon.net.nz does not seem to have delegated the domain to your nameservers.
Regards,
Leo
_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
http://list.waikato.ac.nz/mailman/listinfo/nznog
--
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach Email Guard if this mail (ID 09KjUC5mG) is spam:
Spam: https://emailguard.orcon.net.nz/canit/b.php?i=09KjUC5mG&m=ae916b2c1e4b&t=20130902&c=s
Not spam: https://emailguard.orcon.net.nz/canit/b.php?i=09KjUC5mG&m=ae916b2c1e4b&t=20130902&c=n
Forget vote: https://emailguard.orcon.net.nz/canit/b.php?i=09KjUC5mG&m=ae916b2c1e4b&t=20130902&c=f
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS