SixXS::Sunset 2017-06-06

ReverseDNS not added
[de] Shadow Hawkins on Thursday, 07 February 2013 18:28:37
Hi all, i have setup reverse DNS and did the delegation. but it looks like there is something wrong. my reverse PTR is (according to SixXS)dig a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa. but when i do dig a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa. ns i don't get an answer of the DNS. When i search for an IP from my network like 2001:4dd0:ff00:8a9a::1 on http://www.heise.de/netze/tools/dns/ i get an timeout, but i don't see an packet on my sixxs device on the one side and also when i do show ipv6 access-list aclipv6-Extern-intern111 IPv6 access list aclipv6-Extern-intern111 permit udp any host 2001:6F8:9FA::4 eq domain sequence 40 permit icmp any any packet-too-big sequence 100 permit icmp any any echo-request sequence 110 i get an counted packet on my router. Also when i try to send an eMail to freenet it doesn't get accepted cause: relay=mx.freenet.de[2001:748:100:40::8:111]:25, delay=2.3, delays=0.04/0/2.2/0.1, dsn=4.0.0, status=deferred (host mx.freenet.de[2001:748:100:40::8:111] said: 451 DNS PTR record lookup failed for 2001:4dd0:ff00:8a9a::1 (in reply to RCPT TO command)) so what could be the error with my DNS Setup? best regards thomas
ReverseDNS not added
[ch] Jeroen Massar SixXS Staff on Thursday, 07 February 2013 18:41:10
my reverse PTR is (according to SixXS)dig a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa.
I fairly sure that SixXS indicates that as your *reverse zone delegation*. 2001:4dd0:ff00:8a9a::1 is your IP, thus the full reverse ip6.arpa label for that is: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa
$ dig +trace 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa [.. skipping root servers ...] f.f.0.d.d.4.1.0.0.2.ip6.arpa. 300 INNSns2.sixxs.net. f.f.0.d.d.4.1.0.0.2.ip6.arpa. 300 INNSns1.sixxs.net. f.f.0.d.d.4.1.0.0.2.ip6.arpa. 300 INNSns3.sixxs.net. ;; Received 153 bytes from 194.8.197.10#53(194.8.197.10) in 36 ms a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa. 14400IN NS ns0-ipv6.stegbauer.info. a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa. 14400IN NS ns1-ipv6.stegbauer.info. ;; Received 150 bytes from 2620:0:6b0:a:250:56ff:fe99:78f7#53(2620:0:6b0:a:250:56ff:fe99:78f7) in 150 ms a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa. 604800 IN SOAns0-ipv6.stegbauer.info. dnsrole.stegbauer.info. 2011090201 10800 3600 2419200 604800 ;; Received 157 bytes from 2001:6f8:9fa::4#53(2001:6f8:9fa::4) in 46 ms
You thus need to still define that label in that zone in your DNS server.
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 PTR example.stegbauer.info.
note the trailing '.' and also that you need to declare it in the stegbauer.info forward too with at least:
example AAAA 2001:4dd0:ff00:8a9a::1
inside the stegbauer.info DNS zone.
ReverseDNS not added
[de] Shadow Hawkins on Sunday, 10 February 2013 22:27:46
Hi Jeroen, my zone is defined as zone "a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa" { type master; file "/etc/bind/zonen/db.stegbauer-2001.4dd0.ff00.8a9a_64"; allow-transfer { 2001:6f8:9fa::4; }; }; also there is a entry: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0PTR intranet.stegbauer.info. but even when i do an host lookup from an other IPv6 location i don't see an IPv6 traffic to my two DNS. according to that some providers doesn't accept eMails from that machine, as they are unable to do DNS PTR request. any ideas? thomas
ReverseDNS not added
[ch] Jeroen Massar SixXS Staff on Sunday, 10 February 2013 22:32:28
$ dig +trace a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa ; <<>> DiG 9.8.1-P1 <<>> +trace a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa ;; global options: +cmd .300129INNSh.root-servers.net. .300129INNSe.root-servers.net. <snip> f.f.0.d.d.4.1.0.0.2.ip6.arpa. 300 INNSns1.sixxs.net. f.f.0.d.d.4.1.0.0.2.ip6.arpa. 300 INNSns3.sixxs.net. f.f.0.d.d.4.1.0.0.2.ip6.arpa. 300 INNSns2.sixxs.net. ;; Received 121 bytes from 194.8.194.70#53(194.8.194.70) in 67 ms a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa. 14400IN NS ns0-ipv6.stegbauer.info. a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa. 14400IN NS ns1-ipv6.stegbauer.info. ;; Received 158 bytes from 193.1.31.74#53(193.1.31.74) in 398 ms a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa. 604800 IN SOAns0-ipv6.stegbauer.info. dnsrole.stegbauer.info. 2011090201 10800 3600 2419200 604800 ;; Received 125 bytes from 2001:6f8:9fa::4#53(2001:6f8:9fa::4) in 45 ms
Thus the delegation is in place.
dig +short @ns0-ipv6.stegbauer.info. 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.9.a.8.0.0.f.f.0.d.d.4.1.0.0.2.ip6.arpa ptr intranet.stegbauer.info.
Seems to work for me....
but even when i do an host lookup from an other IPv6 location i don't see an IPv6 traffic to my two DNS.
Please note that not every system in the world can reach IPv6-only DNS servers. For the next few years you will have to have an IPv4 address on a DNS server for it to work.
according to that some providers doesn't accept eMails from that machine, as they are unable to do DNS PTR request.
Broken and misconfigured systems are not supposed to sent mail, your system is misconfigured, thus the action by those receivers is correct.
ReverseDNS not added
[de] Shadow Hawkins on Wednesday, 13 February 2013 23:52:00
Hi Jeroen, why is my system misconfigured? as i don't have IPv4 nameserver's? best regards thomas
ReverseDNS not added
[ch] Jeroen Massar SixXS Staff on Tuesday, 07 May 2013 15:01:39
why is my system misconfigured?
When reverse is not working, it is misconfigured.
as i don't have IPv4 nameserver's?
For many years more to come, one cannot expect that the remote side has IPv6 transport for DNS, thus yes, one needs IPv4 for nameservers.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker