mrbusy
Technical User
- Dec 10, 2003
- 118
I recently joined a company with a very badly configured network infrastructure - particularly in the area of security, DNS, DHCP and address space.
At the moment we're using a mass of ranges which cross networks owned by INTEL, EDS and the US gov as the "network admin" has assinged entire class B size networks to remote sites.
Appart from the obvious non-conformity to the best practices laid down in RFC1918 can anyone think of a list of good reasons why we shouldn't have our network configured this way?
I'm trying to build a case to change to proper public spaces before our network gets any bigger and more complex.
Any thoughts would be greatfully received.
At the moment we're using a mass of ranges which cross networks owned by INTEL, EDS and the US gov as the "network admin" has assinged entire class B size networks to remote sites.
Appart from the obvious non-conformity to the best practices laid down in RFC1918 can anyone think of a list of good reasons why we shouldn't have our network configured this way?
I'm trying to build a case to change to proper public spaces before our network gets any bigger and more complex.
Any thoughts would be greatfully received.