What you need for IPv6 to be enabled in FF is network.dns.disableIPv6 default boolean false That means that FF *will* use AAAA records and therefore try IPv6. If you flip it to true, FF will not use AAAA records and will only try IPv4. Regards Brian Carpenter University of Auckland On 2009-09-18 22:38, Alan Maher wrote:
Thanks for all replies. The issue was simple (as always) but I will post this in case others come across similar problems. In Firefox "about:config", disable ipv6, and then ipv6 will work. Strange, but true, and would appear to be one of "those" programming errors. Or someone with a perverse sense of humour.
Alan Maher
Brian E Carpenter wrote:
Yes, the IPv6 path across town is a bit comnvoluted and seems to involve Seattle.
tracert www.fx.net.nz
Tracing route to www.fx.net.nz [2402:6000:200:100::4] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 2001:df0:0:2006::254 2 <1 ms <1 ms <1 ms 2001:df0:0:201f::1022:400 3 1 ms <1 ms <1 ms 2001:df0:0:1::14:400 4 1 ms <1 ms <1 ms 2001:df0:0:1::7:be 5 1 ms <1 ms <1 ms 2001:df0:0:1::3:b2 6 1 ms <1 ms <1 ms 2001:df0:0:1::3:b1 7 12 ms 11 ms 13 ms 2404:138:0:1::2 8 11 ms 11 ms 11 ms 2404:138:0:4:214:f601:2d88:dc7e 9 159 ms 153 ms 153 ms 2404:138:2000::a 10 153 ms 153 ms 153 ms kreonet-1-lo-jmb-706.sttlwa.pacificwave.net [2001:504:b:10::6] 11 268 ms 267 ms 267 ms 2001:320:1b00:1::1 12 348 ms 348 ms 348 ms hurricaneelectric-RGE.hkix.net [2001:7fa:0:1::ca28:a19e] 13 348 ms 348 ms 348 ms gige-g0-1.tserv19.hkg1.ipv6.he.net [2001:470:0:b8::2] 14 546 ms 474 ms 474 ms fxnetworks-3-pt.tunnel.tserv19.hkg1.ipv6.he.net [2001:470:17:86::2] 15 * 474 ms 735 ms as9503.akl01.akl.VOCUS.net.au [2402:7800:110:501::3] 16 746 ms 482 ms 482 ms palmy-fw1.ip6.fx.net.nz [2402:6000:f000::100] 17 487 ms 568 ms 482 ms palmy-web1.fx.net.nz [2402:6000:200:100::4]
Trace complete.
Brian
On 2009-09-17 22:05, Blair Harrison wrote:
Hi Alan,
Do you have ipv6 enabled on your computer?
www.fx.net.nz is ipv6 enabled, and I suspect if the website is loading slowly it may have to do with faulty v6 transit. (ie, if you are accessing it over a tunnel going via the US or EU)
You could try www2.fx.net.nz which will go to the same place, but does not have a v6 DNS record.
We haven't had any DoS attacks this evening that I'm aware of.
Regards, Blair Harrison FX Networks
On Thu, Sep 17, 2009 at 7:45 PM, Alan Maher
wrote: My apologies for this (my first) post. As a former Sys Admin, I retain an interest in this area for purely personal & academic reasons. After observing the post, I attempted to access http://www.fx.net.nz/ and it timed out. And is doing so again this evening. Your thoughts? All else is functioning fine. ( I run PClos linux on my desktop & use Open DNS) Alan Maher
------------------------------------------------------------------------
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog