Re: ICANN registrar supporting v6 glue?
Barrett == Barrett Lyon [EMAIL PROTECTED] writes: Barrett Apparently GoDaddy does not support v6 glue for their customers, Barrett who does? I know that gkg.net does. And entering them is via the same web form as v4 addresses. -JimC -- James Cloos [EMAIL PROTECTED] OpenPGP: 1024D/ED7DAEA6
Re: The Choice: IPv4 Exhaustion or Transition to IPv6
In article [EMAIL PROTECTED] you write:
John Curran wrote:
Steve -
For the first end site that has to connect via IPv6,
it will be very bad if there is not a base of IPv6
web/email sites already in place.
As the network administrator for a Web hosting company, I've not seen
any coherent (and useful) information about how I can provide both IPv6
addressing and IPv4 addressing for the sites I host. I'm in the process
of doing OS upgrades, and IPv6 is included...but currently I shut off
IPv6 because I don't have a IPv6 firewall solution yet.
Well there are lots of firewalls that support IPv6. If you can't
find one you really have not searched.
That includes DNS, by the way. I'm deploying new DNS servers, and would
be *very* interested in how to convince BIND 9.2.4 to answer IPv6 queries.
listen-on-v6 { any; };
If you want finer acls than that in listen-on-v6 then you want
BIND 9.3 (currently 9.3.4) or BIND 9.4 (currently 9.4.1).
Another issue: the Plesk Web control panel software from SW-Soft
doesn't seem to have any support for IPv6. The CPanel Web Host Manager
at least lets me create records in zone files, so roughly 1/3 of my
customers *could* have IPv6 capability.
Lurkers: tutorials welcome.
Re: ICANN registrar supporting v6 glue?
Barrett Lyon wrote: =20 Apparently GoDaddy does not support v6 glue for their customers, who does? I don't think requiring dual-stack v6 users perform v4 queries t= o find records is all that great. At least eNom does. There are a few others but it tends to be that you have to raise a support ticket to actually get the records in, most webinterfaces don't support it yet unfortunately. One note here is that even though you can get glue into com/net/org using this method, there is no IPv6 glue for the root yet, as such even if you manage to get the IPv6 glue in, it won't accomplish much (except sending all IPv6 capable resolvers over IPv6 transport :) as all resolvers will still require IPv4 to reach the root. One can of course create their own root hint zone and force bind, or other dns server, to not fetch the hints from the real root, but that doesn't help for the rest of the planet. (Root alternatives like orsn could fix that up but apparently their main german box that was doing IPv6 is out of the air) You don't change the hints you just provide zones that override B.ROOT-SERVERS.NET, F.ROOT-SERVERS.NET, H.ROOT-SERVERS.NET, K.ROOT-SERVERS.NET and M.ROOT-SERVERS.NET or just use your own ROOT-SERVERS.NET zone with the s added in. In the few couple of years I've only seen two outages with the IPv6 root instances. In both cases they were fixed soon after reporting the outage. Mark B.ROOT-SERVERS.NET. 3600IN A 192.228.79.201 B.ROOT-SERVERS.NET. 3600IN 2001:478:65::53 F.ROOT-SERVERS.NET. 3600IN A 192.5.5.241 F.ROOT-SERVERS.NET. 3600IN 2001:500::1035 H.ROOT-SERVERS.NET. 3600IN A 128.63.2.53 H.ROOT-SERVERS.NET. 3600IN 2001:500:1::803f:235 K.ROOT-SERVERS.NET. 3600IN A 193.0.14.129 K.ROOT-SERVERS.NET. 3600IN 2001:7fd::1 M.ROOT-SERVERS.NET. 3600IN A 202.12.27.33 M.ROOT-SERVERS.NET. 3600IN 2001:dc3::35 Note also that various ccTLD's are able to add glue to your zone on request (notably .fr/.ch/.nl/.se do so already for quite some time) Greets, Jeroen --enig28DE1EA6E1A720C65610D130 Content-Type: application/pgp-signature; name=signature.asc Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Jeroen Massar / http://unfix.org/~jeroen/ iHUEARECADUFAkaFMZMuFIAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy b2VuQHVuZml4Lm9yZwAKCRApqihSMz58Ixw1AKC8ycHIGT3Nzs296Xf4XeeDvq+m agCeM0cnyTZxnh0QbnuQXVwhw2kil1o= =UGVO -END PGP SIGNATURE- --enig28DE1EA6E1A720C65610D130--
Re: ICANN registrar supporting v6 glue?
On Sat, Jun 30, 2007 at 11:16:40PM +1000, Mark Andrews wrote: Barrett Lyon wrote: =20 Apparently GoDaddy does not support v6 glue for their customers, who does? I don't think requiring dual-stack v6 users perform v4 queries t= o find records is all that great. At least eNom does. There are a few others but it tends to be that you have to raise a support ticket to actually get the records in, most webinterfaces don't support it yet unfortunately. One note here is that even though you can get glue into com/net/org using this method, there is no IPv6 glue for the root yet, as such even if you manage to get the IPv6 glue in, it won't accomplish much (except sending all IPv6 capable resolvers over IPv6 transport :) as all resolvers will still require IPv4 to reach the root. One can of course create their own root hint zone and force bind, or other dns server, to not fetch the hints from the real root, but that doesn't help for the rest of the planet. (Root alternatives like orsn could fix that up but apparently their main german box that was doing IPv6 is out of the air) You don't change the hints you just provide zones that override B.ROOT-SERVERS.NET, F.ROOT-SERVERS.NET, H.ROOT-SERVERS.NET, K.ROOT-SERVERS.NET and M.ROOT-SERVERS.NET or just use your own ROOT-SERVERS.NET zone with the s added in. I've read your email twice and I dont follow. Either you are telling me a) Provide my own hints with included (you specifically say thats not what you mean tho) or b) Serve my own root zone. From a root operator, surely thats not right either (I hope!)? In the few couple of years I've only seen two outages with the IPv6 root instances. In both cases they were fixed soon after reporting the outage. So there are v6 roots out there? Where are they hiding and why arent they being provided in the hints file or NS queries on . ? Steve B.ROOT-SERVERS.NET. 3600IN A 192.228.79.201 B.ROOT-SERVERS.NET. 3600IN 2001:478:65::53 F.ROOT-SERVERS.NET. 3600IN A 192.5.5.241 F.ROOT-SERVERS.NET. 3600IN 2001:500::1035 H.ROOT-SERVERS.NET. 3600IN A 128.63.2.53 H.ROOT-SERVERS.NET. 3600IN 2001:500:1::803f:235 K.ROOT-SERVERS.NET. 3600IN A 193.0.14.129 K.ROOT-SERVERS.NET. 3600IN 2001:7fd::1 M.ROOT-SERVERS.NET. 3600IN A 202.12.27.33 M.ROOT-SERVERS.NET. 3600IN 2001:dc3::35 Note also that various ccTLD's are able to add glue to your zone on request (notably .fr/.ch/.nl/.se do so already for quite some time) Greets, Jeroen --enig28DE1EA6E1A720C65610D130 Content-Type: application/pgp-signature; name=signature.asc Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Jeroen Massar / http://unfix.org/~jeroen/ iHUEARECADUFAkaFMZMuFIAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy b2VuQHVuZml4Lm9yZwAKCRApqihSMz58Ixw1AKC8ycHIGT3Nzs296Xf4XeeDvq+m agCeM0cnyTZxnh0QbnuQXVwhw2kil1o= =UGVO -END PGP SIGNATURE- --enig28DE1EA6E1A720C65610D130--
Re: ICANN registrar supporting v6 glue?
Stephen Wilcox wrote: On Sat, Jun 30, 2007 at 11:16:40PM +1000, Mark Andrews wrote: [..] You don't change the hints you just provide zones that override B.ROOT-SERVERS.NET, F.ROOT-SERVERS.NET, H.ROOT-SERVERS.NET, K.ROOT-SERVERS.NET and M.ROOT-SERVERS.NET or just use your own ROOT-SERVERS.NET zone with the s added in. I've read your email twice and I dont follow. Either you are telling me You want option c: c) Serve your own version of root-servers.net containing 's This never occurred to me but it indeed is the best way to do it. All the root-servers have names in root-servers.net, as such just make your own master zone containing: B.ROOT-SERVERS.NET. 3600IN A 192.228.79.201 B.ROOT-SERVERS.NET. 3600IN 2001:478:65::53 F.ROOT-SERVERS.NET. 3600IN A 192.5.5.241 F.ROOT-SERVERS.NET. 3600IN 2001:500::1035 H.ROOT-SERVERS.NET. 3600IN A 128.63.2.53 H.ROOT-SERVERS.NET. 3600IN 2001:500:1::803f:235 K.ROOT-SERVERS.NET. 3600IN A 193.0.14.129 K.ROOT-SERVERS.NET. 3600IN 2001:7fd::1 M.ROOT-SERVERS.NET. 3600IN A 202.12.27.33 M.ROOT-SERVERS.NET. 3600IN 2001:dc3::35 + optionally the other roots-servers as found on www.root-servers.org And presto. You don't even have to turn of glue fetch etc, as the above zone will override the glue then anyway. Good one Mark, thanks. Greets, Jeroen signature.asc Description: OpenPGP digital signature
Re: Cable-Tying with Waxed Twine
On Wed, Jan 24, 2007 at 09:41:22PM -0700, Larry Beaulieu wrote: Lacing is a lot slower than using platic ties, and doing it is rough on your fingers. If you're lucky you know a data tech who can show you how to do it properly, it's really not something that you can just describe in writing. Sounds like a good use for youtube. -- That is not dead which can eternal lie, and with strange aeons even death may die. - H.P. Lovecraft, The Call of the Cthulhu URL:http://www.subspacefield.org/~travis/ -- dharma advaita For a good time on my UBE blacklist, email [EMAIL PROTECTED] pgpFoNUkDEFFt.pgp Description: PGP signature
Re: messy
On Tue, Jan 30, 2007 at 03:48:18PM -0500, Robert E. Seastrom wrote: Lucy Lynch [EMAIL PROTECTED] writes: and hard to read... http://www.ntia.doc.gov/osmhome/allochrt.pdf I had the same reaction at first. Incidentally, you can get this for cheap from the GPO. I have it on my wall as reference art. It came in handy the other day when looking for the possibility of interference between cell phone and wifi. different frequencies of RF have different performance characteristics. unlike ip addresses, a 1 mhz allocation at 180 mhz and a 1 mhz allocation at 6.5 ghz are not fungible. Plus, large installed bases; xceivers for different frequencies are not always interchangable, even with PLL/xtal changes. But yeah, any HAM can tell you that different bands do different things... some bounce off the ionosphere (shortwave/HF) and some penetrate walls better than others (low frequencies). Some are refracted and diffused by rain, and some aren't, etc. Heck, some can be bounced off the moon (it's called moonbounce, but don't expect anything but morse to be understandable). I think I read somewhere that the USS Liberty SIGINT ship had a large dish for this kind of communication (makes direction-finding fairly difficult). As a consequence, you find bands for radiolocation (RADAR) and mobile radio and such spread all over the place. If you're 300 miles from civilization, and it's raining, and all the mobile radio bands were in the range ruined by rain, and someone suffered a life-threatening injury, that would be bad. There are a lot of lobbyists and vested interests in allocation fights, but I think that's a smaller factor than the others mentioned above. -- That is not dead which can eternal lie, and with strange aeons even death may die. - H.P. Lovecraft, The Call of the Cthulhu URL:http://www.subspacefield.org/~travis/ -- dharma advaita For a good time on my UBE blacklist, email [EMAIL PROTECTED] pgp8FgBxsBKgi.pgp Description: PGP signature
