Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: problem with RDNS  (Read 3376 times)

Lefo1

  • Guest
problem with RDNS
« on: February 25, 2009, 09:47:49 AM »

Hello, I have problem with RDNS.

I have set RDNS servers to:
 ns1.lefo.linuxclan.org
 ns2.lefo.linuxclan.org
 ns3.lefo.linuxclan.org

I think my nameservers works fine:

Code: [Select]
$ dig @ns1.lefo.linuxclan.org -x 2001:470:1f0a:d92:0:115:87:1

; <<>> DiG 9.5.0b2 <<>> @ns1.lefo.linuxclan.org -x 2001:470:1f0a:d92:0:115:87:1
; (2 servers found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36939
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 6

;; QUESTION SECTION:
;1.0.0.0.7.8.0.0.5.1.1.0.0.0.0.0.2.9.d.0.a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. IN PTR

;; ANSWER SECTION:
1.0.0.0.7.8.0.0.5.1.1.0.0.0.0.0.2.9.d.0.a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 172800 IN PTR www.lefo.linuxclan.org.

;; AUTHORITY SECTION:
2.9.d.0.a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 172800 IN NS ns3.lefo.linuxclan.org.
2.9.d.0.a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 172800 IN NS ns2.lefo.linuxclan.org.
2.9.d.0.a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 172800 IN NS ns1.lefo.linuxclan.org.

;; ADDITIONAL SECTION:
ns1.lefo.linuxclan.org. 86400   IN      A       89.31.42.66
ns1.lefo.linuxclan.org. 86400   IN      AAAA    2001:470:1f0a:d92:0:115:78:1
ns2.lefo.linuxclan.org. 86400   IN      A       89.31.42.66
ns2.lefo.linuxclan.org. 86400   IN      AAAA    2001:470:1f0a:d92:0:115:78:2
ns3.lefo.linuxclan.org. 86400   IN      A       89.31.42.66
ns3.lefo.linuxclan.org. 86400   IN      AAAA    2001:470:1f0a:d92:0:115:78:3

;; Query time: 51 msec
;; SERVER: 2001:470:1f0a:d92:0:115:78:1#53(2001:470:1f0a:d92:0:115:78:1)
;; WHEN: Wed Feb 25 18:24:02 2009
;; MSG SIZE  rcvd: 312

But when I try to request it from some HE nameserver i got:

Code: [Select]
$ dig @ns2.he.net  -x 2001:470:1f0a:d92:0:115:87:1

; <<>> DiG 9.4.3-P1 <<>> @ns2.he.net -x 2001:470:1f0a:d92:0:115:87:1
; (2 servers found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63842
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;1.0.0.0.7.8.0.0.5.1.1.0.0.0.0.0.2.9.d.0.a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. IN PTR

;; AUTHORITY SECTION:
a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 86400 IN SOA  ns1.he.net. hostmaster.he.net. 2009021717 10800 1800 604800 86400

;; Query time: 189 msec
;; SERVER: 2001:470:200::2#53(2001:470:200::2)
;; WHEN: Wed Feb 25 18:17:22 2009
;; MSG SIZE  rcvd: 153

I tried to wait some days but nothing changed.
HE nameservers are still returning SOA instead of NS records.
Is there anything else that I have to do?
Logged

piojan

  • Jr. Member
  • **
  • Posts: 85
Re: problem with RDNS
« Reply #1 on: February 25, 2009, 10:33:30 AM »

Code: [Select]
host 2001:470:1f0a:d92::2
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.9.d.0.a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa domain name pointer lefo-1-pt.tunnel.tserv6.fra1.ipv6.he.net.
root@debi:/etc/raddb/log/radius# host 2001:470:1f0a:d92::1
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.9.d.0.a.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa domain name pointer lefo-1.tunnel.tserv6.fra1.ipv6.he.net.
2001:470:1f0a:d92::/48 is your p2p link with HE (and no other use)
You probably got 2001:470:1f0b:d92::/48 for your use. (a->b)
And that is working correctly (HE points to your ns)
Logged

Lefo1

  • Guest
Re: problem with RDNS
« Reply #2 on: February 25, 2009, 10:53:32 AM »

Sorry, I didnt notice the difference between 1f0a and 1f0b.
I have to change many configurations and try it again.
Sorry for stupid post.
Logged