Revision as of 19:27, 19 May 2016 edit Nimbex (talk \| contribs) Extended confirmed users 927 edits m remove parenthetical word ← Previous edit		Revision as of 06:40, 9 June 2016 edit undo Bgwhite (talk \| contribs) Extended confirmed users 547,151 edits Remove blank line(s) between list items per WP:LISTGAP to fix an accessibility issue for users of screen readers. Do WP:GENFIXES and cleanup if needed. Discuss this at WT:WCAG#LISTGAP using AWB Next edit →
Line 24: Thus, a production server in Minneapolis, Minnesota would be nnn.ps.min.mn.us.example.com, or a development server in Vancouver, BC, would be nnn.ds.van.bc.ca.example.com. Large networks often use a systematic naming scheme, such as using a ___location (e.g. a department) plus a purpose to generate a name for a computer. For example, a web server in NY may be called "nyc-www-04.xyz.net". Line 32: ''(city-function-number.___domain.name)'' '''[[~~List_of_airports_by_IATA_code~~List of airports by IATA code\|City Code IATA link]]''' * nyc-pdc-201.xyz.net Line 40: If you have many offices in a city distinguish the offices designate * 100–199 ABC ___location Line 48: * 700–799 Extranet * 800–899 DMZ * 900–999 Internet * <tt>gpc</tt> - General PC * <tt>prn</tt> - Printer

Computer network naming scheme: Difference between revisions