This morning I successfully converted my internal DNS to corp.avvira.us. I’m glad that I read about the whole problematic fake internal domain thing yesterday because that could rear its ugly head. I also learned about something very important. I made yet another mistake in my planning.
I’ve never designed anything that would ever grow beyond a /22 or 1022 hosts on a network. Now I find myself in a situation where I have to plan for a case where this could happen: my own business. So I read up more carefully on variable length subnet masking. Apparently, you have to estimate what your largest subnet size will be and then carve up from there. So again I planned poorly with thinking I’d just carve up 172.16.0.0/12 into a whole bunch of /24s. That would leave a large and inefficient routing table.
So it’s better to think this one through carefully. I’m seeing this now. It might make sense instead to carve this up into several /18s, and from there, further divide into smaller units as needed here and there. I guess I need someone with more advanced #NetworkEngineering experience than I have. Feel free to weigh in on this.