Le 16/09/2011 16:45, m...@smtp.fakessh.eu a écrit : > Le vendredi 16 septembre 2011 00:12, mouss a écrit : >> Le 15/09/2011 03:34, m...@smtp.fakessh.eu a écrit : >>> hello list >>> hello guru of postfix >>> >>> >>> I think I have correctly configure bind for IPv6. but I still can not >>> connect with telnet on my server >>> >>> all testimonials are welcome >> >> well, it is hard or us to see what "bind" have to do with "can not >> connect". "bind" is about names. connection is about IP. different beasts. >> >> you need to tell us more. what "can not connect" exactly means? show >> transcripts and logs. > > mouss thank you. > I precise I did not fit ipv6 in my apartment > I see you in my ipv6 traffic logs (logwatch, xtail) > my ns secondary servers are not connected with ipv6 but one that has serious > problems with the serial refresh of the zone > ie it is always late for several days or weeks > I have yet properly declare a reverse zone ipv6 and aaaa in my area > so I do not know if traceroute -6 ping6 and runs on my server > so > [*****@localhost ~]$ host -t aaaa fakessh.eu > fakessh.eu has IPv6 address 2002::5762:bae8 > [******@localhost ~]$ host -t aaaa fakessh.eu 8.8.8.8 > Using domain server: > Name: 8.8.8.8 > Address: 8.8.8.8#53 > Aliases: > > fakessh.eu has IPv6 address 2002::5762:bae8 > > since my command line r13151 telnet down with no trace in maillog > and trace in message > Sep 16 16:42:02 r13151 kernel: Shorewall:fw2net:ACCEPT:IN= OUT=eth0
I've never used shorewall and I'll never will.... I don't understand a single point of what you're saying. if you have a dns issue, this is not the place to ask for help. this list is about postfix.
