Network

The DNS tutorials have always been a bit of a monster and in need of better organization. There’s a lot to how DNS works and there are a lot of individual tutorial pages in that section of the site. I’ve updated the DNS tutorial and reorganized it. The reorganization means that if you’ve bookmarked the DNS pages, the bookmark probably isn’t working any more because the page moved.

The DNS tutorial was organized as a set of pages in one folder. I’ve now grouped them into categories. I still need to go through and sort the pages into the correct reading order and update some scripts so that the ‘next page’ functionality works properly. At one time, I looked into converting the static pages into WordPress ‘pages’, but there are over 800 individual pages within this site and WordPress apparently has problems handling more than 160 pages (WordPress would crash and I’d have to wipe out the installation, reset MySQL and reinstall it).

Click here to go to the DNS Tutorials

Time for another question from my Ask InetDaemon mailbox:

Thanks for the excellent article on TCP, this was the best ever explanation
I've found. Could you please provide me with the C++ implementation code for
TCP handshake protocol?

The handshaking is a function of the TCP protocol, and not really a protocol unto itself.  Thus, handshaking is not a standalone piece of code.  It’s integrated in the actual TCP software, first implemented in Berkeley BSD UNIX.

If you want a copy of the source code, you should learn to use a CVS client to download (sync) a copy of the BSD source in the CVS repository, provided you’re using a BSD compatible computer and operating system. The Berkeley Sockets implementation is the de-facto standard for TCP.

See:
Synchronizing Your Source.

–InetDaemon

Another reader asks:

What is the difference between an IP datagram and a TCP segment?

Mostly, its terminology used in the standards documentation, though upon transmission a TCP segment gets created first from the application layer data and an IP datagram contains the TCP segment in the payload section of the IP datagram.  I’ve got lots of tutorials on these subjects in this website.

Our new house has CATV and network wiring on the main floor but none of the network wiring is terminated (the previous owners stripped the jacks off the wires for some strange reason).  I originally deployed the entire suite of computers to my office. The list includes:

  • The root and secondary Windows AD domain controllers
  • Dual 21″ Flat Panels
  • The print server and printer
  • The RAID5 file server
  • All the four workstations
  • Three Laptops

My office is a small 10×12 room with only one A/C vent for cooling.  There’s barely enough room for me and the computer gear.  As a housewarming present, my Father-in-law purchased and installed a dual fan in the transom above the door to blow out the hot air all that hardware generates, but I can’t close the door or the room gets too warm.

I decided I should move my computer lab from my stuffy office to the freezing, air-conditioned basement. The move would lower my heat load in the office and maybe will moderate the temperature in the basement.   One of the first things I needed to do was to get some Category 6 cable pulled into the basement room.  My father-in-law has never pulled cable, and was curious and wanted to learn.  We got the cable pulled, I showed him how to terminate Cat 6 by putting one end on myself, then I let him terminate the other end. When he finished, we tested the cable and it works perfectly.

Now all I need to do is move the computers.

Support InetDaemon.Com