| 00:42.56 | *** join/#utah tiwula (~lane@107-1-184-110-ip-static.hfc.comcastbusiness.net) |
| 00:47.37 | *** join/#utah lane_ (~lane@107-1-184-110-ip-static.hfc.comcastbusiness.net) |
| 01:13.42 | *** join/#utah Yorokobi (~Yorokobi@pdpc/supporter/professional/yorokobi) |
| 01:20.23 | *** join/#utah mabes (~mabes@68.69.167.158) |
| 01:47.34 | *** join/#utah lane__ (~lane@107-1-184-110-ip-static.hfc.comcastbusiness.net) |
| 01:48.50 | *** join/#utah jalbretsen (~jalbretse@24.10.128.246) |
| 01:53.02 | *** join/#utah lane_ (~lane@107-1-184-110-ip-static.hfc.comcastbusiness.net) |
| 01:54.01 | jalbretsen | anyone have any recommendations for free / cheap DNS? I had a VPS doing it, but that went bye bye. |
| 01:57.30 | *** join/#utah lane__ (~lane@107-1-184-110-ip-static.hfc.comcastbusiness.net) |
| 02:08.28 | shalkie | jalbretsen: I have a linode VPS and it includes their DNS servers. I don't know if that is what you were doing. |
| 02:09.22 | shalkie | Is this DNS for work or private? |
| 02:48.05 | *** join/#utah lane_ (~lane@107-1-184-110-ip-static.hfc.comcastbusiness.net) |
| 02:56.35 | jalbretsen | shalkie: private. |
| 03:05.02 | *** join/#utah lane__ (~lane@107-1-184-110-ip-static.hfc.comcastbusiness.net) |
| 03:21.49 | shalkie | jalbretsen: Oh, well if you want I don't have an objection to hosting for you if it is private and fairly low traffic. |
| 03:23.37 | *** join/#utah Jayce^ (~jayce@74-220-196-123.unifiedlayer.com) |
| 03:37.54 | ezakimak | do you have a static ip? |
| 03:38.01 | ezakimak | you can just host it yourself w/djbdns |
| 03:47.07 | shalkie | ezakimak: Why djbdns? |
| 03:49.10 | shalkie | s/Why/Any particular reason why/ |
| 03:53.08 | shalkie | jalbretsen: Otherwise you might consider Route 53 through Amazon. I think you can use it for external sites, though I haven't played with it yet. The pricing is VERY cheap. Something like .50 for the first 25 zones per month. |
| 03:53.31 | shalkie | Sorry, .50 cents per zone for the first 25 zones. |
| 03:56.29 | jalbretsen | ya. it's a static IP, I was hosting it on a VPS, it just points to google blogs, but long story short, my VPS is gone |
| 04:08.55 | *** join/#utah Tristan_ (~Tristan@c-98-202-224-157.hsd1.ut.comcast.net) |
| 04:58.48 | *** join/#utah Nemus (~Nemus@unaffiliated/nemus) |
| 04:59.08 | *** part/#utah Nemus (~Nemus@unaffiliated/nemus) |
| 05:18.07 | shalkie | 0 |
| 05:18.20 | shalkie | blech... Wrong window. |
| 05:27.07 | *** mode/#utah [+o Jayce^] by ChanServ |
| 05:37.26 | *** join/#utah resplin_ (~resplin@166.70.213.4) |
| 07:08.12 | *** join/#utah utlemming (~ben@67.199.187.66) |
| 07:11.25 | ezakimak | shalkie, yes, because djbdns works great, is very secure, and is easy to use |
| 07:13.33 | shalkie | I haven't played with djbdns. I have heard good things though. |
| 07:13.49 | shalkie | I guess I am just used to using BIND. |
| 07:14.19 | shalkie | I will put on my "To play with" list. :-) |
| 09:55.38 | eightyeight | meh |
| 09:55.46 | eightyeight | djbdns doesn't support ipv6 |
| 11:10.20 | *** join/#utah jelliott_ (~jelliott@208.97.56.66) |
| 12:47.16 | *** join/#utah Yaawboy (~Yaawboy@199.254.238.226) |
| 13:26.23 | *** join/#utah pdayton (~Adium@63.251.sfcn.org) |
| 15:02.33 | *** join/#utah wps (~wps@199.101.224.169) |
| 16:04.03 | *** join/#utah Tristan_ (~Tristan@c-98-202-224-157.hsd1.ut.comcast.net) |
| 16:54.57 | *** join/#utah mrpull (~jpollmann@71-35-244-172.slkc.qwest.net) |
| 17:10.49 | ezakimak | there's patches for djbdns ipv6 |
| 17:11.01 | ezakimak | but who's using ipv6 yet anyways? |
| 17:17.59 | *** join/#utah tiwula (~lane@63-248-12-52.static.sdyl0420.digis.net) |
| 17:18.33 | eightyeight | like, all of china and india |
| 17:31.22 | *** join/#utah pdayton1 (~pjdayton@63.251.sfcn.org) |
| 18:28.58 | ezakimak | all? |
| 18:29.24 | ezakimak | but that does nothing to incentivize me to use it--it does not benefit me at all to use it right now |
| 18:29.30 | ezakimak | it's a giant chicken and egg problem |
| 20:02.01 | eightyeight | all minus 3 or 4 who don't have computers |
| 20:02.04 | eightyeight | :) |
| 20:08.58 | ezakimak | has anyone come up with an actual, viable, transition plan yet? |
| 20:12.26 | ezakimak | or are djb's comments from 2002 still just as applicable today? |
| 20:19.25 | ezakimak | http://cr.yp.to/djbdns/ipv6mess.html |
| 20:32.00 | *** join/#utah smcquay (~smcquay@69.169.186.70.provo.static.broadweavenetworks.net) |
| 20:32.06 | eightyeight | there are a number of patches that have essentially created dbndns |
| 20:33.25 | eightyeight | the mess only exists when you're just trying to get the two internets to communicate |
| 20:36.36 | ezakimak | but that's a *big* problem--the fact that by definition ipv6 even creates a 2nd, distinct internet in the first place |
| 20:37.53 | eightyeight | maybe |
| 20:38.20 | eightyeight | ipv6 was designed to clean up a lot of ipv4 garbage, and succeeded |
| 20:38.29 | eightyeight | so, almost by definition, they aren't going to be compatible |
| 20:39.04 | eightyeight | and it's not that big of an inconvenience to build out a dual stack, imo |
| 20:41.30 | *** join/#utah HumanCell (~Humancell@207.224.214.130) |
| 20:42.07 | ezakimak | um, i think the current situation proves otherwise |
| 20:42.29 | ezakimak | if it was so easy, everyone would have already jumped on board and done it and we'd have switched over |
| 20:42.54 | eightyeight | it's more of a 'y2k' issue than anything |
| 20:43.04 | eightyeight | laziness prevails at all levels |
| 20:43.15 | ezakimak | i disagree. with y2k, things actually broke--there was a hard deadline to fix things by |
| 20:43.21 | eightyeight | or, they don't see the need |
| 20:43.34 | ezakimak | with ipv6, well, we're all using ipv4--it *works* |
| 20:43.55 | eightyeight | "I'm in the U.S., where 70% of the internet exists, and it's ipv4. why should i do anything about it?" |
| 20:44.14 | eightyeight | "who's using ipv6 yet anyways?" |
| 20:44.17 | eightyeight | :) |
| 20:45.14 | ezakimak | so tell me: if I were to get an ipv6 address, and set up my machine to use ipv6--what services would actually be available to me, *right now* via only ipv6? |
| 20:46.01 | eightyeight | freenode and google, to start |
| 20:47.04 | ezakimak | ok. so 2. |
| 20:47.20 | ezakimak | and after i do a google search, will any of the resulting links actually work via ipv6? |
| 20:47.36 | ezakimak | or does it only present ipv6-capable results? |
| 20:48.19 | eightyeight | yeah. some will, some won't. |
| 20:48.27 | eightyeight | i'm not saying it's ubiquitous |
| 20:49.12 | ezakimak | see, and that's where imo the ipv6 designers did a major cluster-f* |
| 20:49.24 | ezakimak | seemless transition should have been goal #1 |
| 20:50.00 | ezakimak | now we have 4 billion servers that each need to be configured, and thousands of client software that has to be written specifically to work w/ipv6 also/instead |
| 20:51.29 | ezakimak | so much software already exists that will never be updated to work on ipv6--which means w/o full backwards compatibility (which it does not provide), for that software to work we have to keep the ipv4 up |
| 20:51.33 | eightyeight | and i think, meh. so what. apache, nfs, dns (minus djbdns), squid, ftp, ssh, ... all support ipv6 natively |
| 20:51.49 | eightyeight | what software doesn't work with ipv6 now? |
| 20:52.13 | ezakimak | pick a game. |
| 21:00.00 | ezakimak | pick any older binary executable |
| 21:42.01 | *** join/#utah wps (~wps@199.101.224.169) |
| 21:44.51 | Migs | I'm going to stick with ipv4 come hell or high water |
| 21:50.58 | ezakimak | the day may come that the world transitions and deprecates ipv4, providing mapping for any old ipv4-only legacy services. I'll switch then. |
| 21:53.31 | Migs | but today is not that day |
| 21:53.45 | Migs | wait, what's the line? |
| 21:53.48 | Migs | but not this day |
| 21:53.57 | ezakimak | right. |
| 21:54.27 | ezakimak | afaik, there is no service that I need that only ipv6 delivers atm. |
| 21:55.04 | ezakimak | and as far as the services i host, i don't know of any clients that would attempt to access it only via ipv6. |
| 21:56.46 | romanovic | seems like just a matter of procrastination. there's no question that we'll all need to put the effort into transitioning at some point, just a question of whether you make the effort early on, or wait until the pain of staying on ipv4 any longer is finally greater than the pain of switching |
| 21:58.09 | ezakimak | but that's the thing--I have no pain using ipv4 currently |
| 21:58.20 | ezakimak | and atm will gain nothing by implementing ipv6 |
| 21:58.34 | ezakimak | there's no carrot *or* stick |
| 21:59.27 | romanovic | I only use ipv4 as well, but i'm not a datacenter administrator either. once ipv6 becomes a necessity, the effort on my part will be minimal, so i'm not worried about it |
| 22:00.44 | romanovic | but anyone who's responsible for systems that do heavy lifting, i would sure hope they' |
| 22:00.51 | romanovic | ve started evaluating the effort involved |
| 22:05.16 | romanovic | I started messing with CJDNS recently (facilitates mesh networking, solves many of the routing issues), and it is ipv6 only. That's my incentive. |
| 22:12.27 | *** join/#utah wps (~wps@199.101.224.169) |
| 22:37.34 | findlay | ipv4 is teh sux0rz |
| 23:55.50 | *** join/#utah kendsnyder (~kendsnyde@207-224-204-229.slkc.qwest.net) |