DNS - IPv6
-
@Dashrender said:
@DustinB3403 said:
Otherwise we'd have a rather flat network if we ran IPv6. Compared to the 5 subnets we have.
I also have several subnets. But considering what I know today, I'm looking to move to a single /23 or /22. Because of switches you don't have to worry about 1000 devices being in the same subnet anymore. Sure broadcast storm could bring you down, so you have to fix those quickly, but you'd have to anyway.
I'm not looking forward to reworking my network for a /22 though, ug!
At least I only have around 200 devices. 4/5's are DHCP, but the darn phones is the biggest pain, currently not DHCP.I did this move two years ago. Don't forget about your printers... those can be a pain to deal with.
-
We have so many different subnets it's going to be take us a while to move to IPv6.
-
@scottalanmiller said:
I've done the move before, with a little good planning it is surprisingly simple and painless. Normally, at least.
Frankly I'd prefer to jump directly to IPv6, but like the rest i have many printers that don't support IPv6. I wonder if my IP phones do? Not that I need to really worry about them.
-
So glad that we are basically printerless
-
@Dashrender said:
@scottalanmiller said:
I've done the move before, with a little good planning it is surprisingly simple and painless. Normally, at least.
Frankly I'd prefer to jump directly to IPv6, but like the rest i have many printers that don't support IPv6. I wonder if my IP phones do? Not that I need to really worry about them.
I would hope so, all of our phones and printer support IPv6.
-
@coliver said:
@Dashrender said:
@DustinB3403 said:
Otherwise we'd have a rather flat network if we ran IPv6. Compared to the 5 subnets we have.
I also have several subnets. But considering what I know today, I'm looking to move to a single /23 or /22. Because of switches you don't have to worry about 1000 devices being in the same subnet anymore. Sure broadcast storm could bring you down, so you have to fix those quickly, but you'd have to anyway.
I'm not looking forward to reworking my network for a /22 though, ug!
At least I only have around 200 devices. 4/5's are DHCP, but the darn phones is the biggest pain, currently not DHCP.I did this move two years ago. Don't forget about your printers... those can be a pain to deal with.
Yep - main things that have static IPs - Printers, Phones, Server and Switches!!
-
@Jason said:
@Dashrender said:
@scottalanmiller said:
I've done the move before, with a little good planning it is surprisingly simple and painless. Normally, at least.
Frankly I'd prefer to jump directly to IPv6, but like the rest i have many printers that don't support IPv6. I wonder if my IP phones do? Not that I need to really worry about them.
I would hope so, all of our phones and printer support IPv6.
Dymo label print servers don't support IPv6
-
@Dashrender said:
Yep - main things that have static IPs - Printers, Phones, Server and Switches!!
You have phones with Staitc IPs? that's a lot of trouble for nothing.
-
@Dashrender said:
Dymo label print servers don't support IPv6
I wouldn't know, we consider those consumer grade they break too much. We use ones like these:
-
@Jason said:
You have phones with Staitc IPs? that's a lot of trouble for nothing.
I didn't set them up, the vendor did, 8 years ago.
The new building we just did uses DHCP for the phones - it was kinda nice.. there are two DHCP servers on the same LAN, the phone system has one with a small range only for the phones, and only responds to requests that have a MAC in a qualified range.How the phones don't take an IP from my Windows DHCP if it responds first, is beyond me - but so far no issues.
-
@Jason said:
@Dashrender said:
Dymo label print servers don't support IPv6
I wouldn't know, we consider those consumer grade they break too much. We use ones like these:
OMG dude! $1600? NO WAY! We have 8 Dymo's that cost a total of $300 each. I could replace every unit 5 times and still have money left over for those of those. Plus the Dymo's aren't so unreliable as to make the expense worthwhile (i.e. save support time to warrant the expense).
-
Zebra makes a great label printer. Really just a top notch machine. They come in at the same price range as Cub Printers though.
Cub seems to be a knock off though.
-
@Dashrender said:
OMG dude! $1600? NO WAY! We have 8 Dymo's that cost a total of $300 each. I could replace every unit 5 times and still have money left over for those of those. Plus the Dymo's aren't so unreliable as to make the expense worthwhile (i.e. save support time to warrant the expense).
And we haven't had to replace a single unit so far. You can just replace $25-$50 parts in them many of them are 10+ years old now because they are designed to be run so long both in build and driver support.
-
@DustinB3403 said:
Cub seems to be a knock off though.
Cub isn't a knock off, they only make stuff for industrial use.
-
How long as Cub been around, I haven't heard of them until now.
Zebra Printers have been around for a very long time, and I have units in production that are older than I am. (30 years old) that have never skipped a beat.
-
That's great, and in an industrial environment I can totally see their use. In a medial clinic, they are over kill.
If I had to replace one every year - it might, might make sense.. but I haven't had one die yet, most are 2 years old now. I expect to get 3-8 years out of them.
But I'm in a clean, non industrial environment.
-
@DustinB3403 said:
How long as Cub been around, I haven't heard of them until now.
That doesn't make them a knock off.
-
@Jason said:
That doesn't make them a knock off.
And apple's never used a patient without paying for it....
-
@DustinB3403 said:
@Jason said:
That doesn't make them a knock off.
And apple's never used a patient without paying for it....
OK kids.. play nice
-
@Dashrender said:
How the phones don't take an IP from my Windows DHCP if it responds first, is beyond me - but so far no issues.
It's called playing fast and loose. Works often, no guarantees. It's called taking a risk and walking away leaving the potential future issues for the customer to deal with.