DNS & NTP best practice (vlans & IoT)
-
@furom said in DNS & NTP best practice (vlans & IoT):
I haven't felt the need really to switch to IPv6, and suppose it won't happen until there is a must or real benefit from doing that.
I am with you.. I see it as the future sure - but I don't believe it is on the curve to adoption that they thought it would be. I have yet to find a resource - not one that would require me to have IPv6..
I have zero use for it myself, and it is pretty much off.. My current isp doesn't even provide it native hehe.. and have not even seen any mention of it even being on their radar.. I have used a tunnel from HE for years and years for my access to Ipv6, but its only for learning and playing.. I do not use it on any of my devices in any sort of production.. I turn it on a device when I want to play/test something. I use to provide my ntp server to the pool over both ipv4 and ipv6, but have turned that off.. It was more of learning curve thing anyway.. I have no real desire to provide services to the public internet ;)
Part of the problem to be honest, is the adoption of IPv6 for stuff like phones that require a vast amount of IPs to use - how many billions of phones are on the planet.. My phone does not get an IPv4 address, it gets IPv6 only for cell data - when it wants to go to an IPv4 address the cell providers network handles that connection via their 464xlat setup..
So them moving away from IPv4 freed up a bunch of IPs to use for other stuff. There is pretty active market in selling your IPv4 space to those that need it.. And you can make some good money, I was directly involved in the sale of some of the /16 in my old company.. They really have actual need of small fraction of that space, were not using most of it. To be honest if they would be doing what arin suggests they would of returned most of that space to arin years and years ago. It was quite lucrative deal.. I got screwed out of my bonus that I should of gotten for coming up with it.. Suppose to get like 10% when you came up with any sort of out of the box thing that made the company money.. Should of gotten like 50k in that deal, they threw me a bone of 5k.. Bastards! ;)
There is just the cost for companies moving to it as well - at least internally.. And what driving force do they have - the migration sure isn't going to save them money, not even in the long run.. They have plenty of rfc1918 space to use on the company internal network.. They will not run out of that ever.. So where is the advantage of them moving to ipv6.. Sure you can play nice and throw up some public IPv6 access to your public facing servers.. That is pretty simple and easy to do, and really easy to get a /32 from Arin for your own IPv6 space.. Was involved in that whole process - has the company really done anything with it - no they have used some of it in a future project that not sure will ever go anywhere.. So some infrastructure is using IPv6 on the public internet - but there is no driving force for its use elsewhere in the company or other projects..
My new company, on the fortune 100 list, it is not a tiny network that is for sure.. While I am new and sure do not have a handle on everything going on in the company - Can tell you from study of all the network diagrams and info. IPv6 is no where that I see... And even the public site for website has no AAAA.. I might have to ask around if any IPv6 work planned anytime in the near future..
I more than for sure will retire before any real traction with IPv6 in the corporate landscape to be honest - I got 10 years.. So we will see I guess.. But if I could place a bet, I would and a very large sum that not much happens with it.. I use to see new customer networks all the time old company was a MSP.. Never once did get a customer that had used any IPv6 in their networks, nor any customers that had any real plans or drive to do so..
-
@johnpoz Oh well, as for coming up with cost savings, heck, even tech that introduced possibilities not there before - and not getting even the credit for it - been there done that, it sucks.
I also doubt I'll ever come to use IPv6 in any commercial way, and though it seems rather straightforward, it is many new things to remember and cope with. Maybe something for a really boring rainy summer, who knows... lol
I think you hit the nail there - cost of implementing. Why fix something that isn't broken? It's always hard to motivate. What I think of for myself is perhaps along the lines of future-proofing, preparing just enough to not having to do a complete overhaul if the rainy day comes... :)
-
@furom said in DNS & NTP best practice (vlans & IoT):
and though it seems rather straightforward
There is way more too it than just a longer address ;)
-
@johnpoz said in DNS & NTP best practice (vlans & IoT):
There is way more too it than just a longer address ;)
Yes, I'm aware of that, but not necessarily hard - pending on scope, just a different way of thinking (trying to stay positive about it)
