What DHCP does

DHCP, the Dynamic Host Configuration Protocol, is the system that hands out network settings automatically. Every device on a network needs a few things to function: its own IP address, so other devices can find it; the address of the router that leads out to the internet; and the address of a DNS server to look names up. In the old days, someone typed all of that into every machine by hand. On a network of more than a few devices, that quickly becomes a misery of clashes and mistakes.

DHCP does it for them. When a device joins, it effectively calls out “does anyone here hand out addresses?”, and a DHCP server, usually built into your router, answers with a free address and the rest of the settings, lent out for a set period called a lease. The same automatic welcome happens when someone connects over a VPN, dropped onto the office network as if they had just plugged in. The whole exchange, set out in a standard that has barely changed in decades, takes a fraction of a second.

Why “turn it off and on again” so often works

DHCP also quietly explains one of IT support’s oldest pieces of advice. When a device cannot get online and reconnecting fixes it, what often happened was a DHCP hiccup: the device never got a clean address, or its lease got into a muddle. Disconnecting and rejoining forces the whole conversation to start over from scratch, a fresh address is handed out, and everything springs back to life. It is not magic, and it is not nothing. It is DHCP getting a second go.

The same machinery sits behind a few other everyday mysteries: why two devices very occasionally claim the same address and knock each other offline, or why a network that has run out of free addresses to lend suddenly stops letting new devices on.

The bits worth knowing for a business

For the most part DHCP is happily invisible, which is how it should be. Two things are worth a business owner knowing. First, because DHCP is so trusting, a rogue device pretending to be the address-giver can quietly misdirect traffic on a network that has not been set up to prevent it, which is one more reason proper managed equipment earns its keep. Second, the few things that genuinely need a fixed, never-changing address, a server, a printer everyone relies on, certain equipment, are usually best assigned deliberately rather than left to the general pool.

Neither is something to lose sleep over. They are simply the sort of detail a well-set-up network gets right quietly, so that the only thing you ever notice about DHCP is that everything connects the moment you switch it on.

The post DHCP Explained: How Your Devices Get on The Network appeared first on Orbit Computer Solutions.

What a VPN actually does

VPN stands for virtual private network, and the idea is right there in the name. It builds a private, encrypted tunnel across a network you do not control, usually the public internet, so that two points can talk as though they were sitting on the same protected local network. Anything travelling through the tunnel is scrambled, so even if someone intercepts it along the way, all they see is noise.

For a business, the classic use is remote access. Someone working from home or a cafe switches on a VPN and their laptop behaves, more or less, as if it were plugged in at the office: it can reach internal systems, and its traffic to them is protected from whatever questionable wifi it happens to be on. A second common use is joining two offices together over the internet as if they shared one network. The modern versions lean on well-regarded encryption protocols like IPsec and WireGuard to do the scrambling.

What it does not do

This is where the marketing runs ahead of the reality. A VPN is not a magic privacy cloak that makes you anonymous or untouchable. It protects data while it is in transit between two points. It does nothing about a weak password, a convincing phishing email, malware already sitting on the laptop, or a website tracking you once you arrive. A consumer VPN that promises total privacy is mostly moving your traffic from your internet provider to the VPN company, who can now see it instead.

For business remote access there is a further wrinkle worth knowing. A traditional VPN tends to drop a remote device onto the internal network and then trust it, which means a single compromised laptop can become a doorway to everything behind it. That weakness is exactly why many organisations are shifting towards a more careful model, often called zero trust, that checks every request on its merits rather than trusting a device simply because it reached the end of a tunnel.

Getting it right for a business

None of this makes VPNs a bad idea. For plenty of businesses a well-run VPN is still the sensible way to give staff safe access to internal systems. It sits at the same edge of the network as your firewall, and the two are set up hand in hand. The difference is in the details, and the UK’s NCSC publishes clear guidance on choosing and configuring one: prefer the VPN client built into the operating system, use certificates rather than shared passwords, and make sure traffic genuinely routes through the tunnel rather than quietly leaking around it.

Put simply, a VPN is a tool, not a force field. Used well, for the job it is actually good at, it quietly protects your people when they work away from the office. Sold as a cure-all, it lulls you into trusting it for things it was never built to do.

The post VPNs Explained : What They Actually Protect, and What They Don’t appeared first on Orbit Computer Solutions.

What SNMP actually does

SNMP, the Simple Network Management Protocol, is the shared language that lets one system keep tabs on all the others. Almost everything on a modern network speaks it: switches, routers, servers, printers, even the battery backup humming away under a desk.

The idea is refreshingly simple. Each device runs a small program called an agent that keeps a running count of how things are going, such as temperature, traffic, spare disk space and how long it has been running. A monitoring system checks in with those agents on a regular schedule and collects the numbers. Devices can also speak up unprompted: when a reading crosses a line that matters, the agent fires off an alert, known as a trap, so trouble surfaces the moment it starts rather than at the next scheduled check.

Why it earns its keep

On paper that sounds like back-office trivia. For a business it is the line between hearing about a problem from your dashboard and hearing about it from your staff.

A network wired up to SNMP and a half-decent monitoring tool is a network somebody can genuinely watch. A disk slowly filling, a line that drops for a few seconds every hour, a device quietly running too hot: each shows up as a trend long before it becomes an outage. It is also how you learn a backup link has quietly taken over before anyone noticed the first one fail. It is the engine underneath every promise of proactive support and round-the-clock monitoring. Take it away, and “we keep an eye on your systems” is mostly a hope. The same readings answer duller but useful questions too: which connection is being saturated at four o’clock, whether an ageing server is on its way out, when it is time to add capacity rather than wait for the first complaint. The same watchful eye covers the devices holding your perimeter, firewall included.

The part worth getting right

There is one catch, and it is a common one. For years SNMP came with a default password of sorts, a community string set to the word public, and plenty of kit still has it untouched. Left that way, it can hand a stranger a tidy summary of your network, and on older versions that information travels with no encryption at all.

The fix is settled: run the current version, SNMPv3, which adds proper authentication and encryption, and change the defaults. A network that is genuinely being looked after has its monitoring turned on and locked down, not one without the other.

None of this is something you should have to think about. But the quiet save, the problem dealt with before it ever reached you, has a name. Whether your own network is set up to make those saves possible is a perfectly fair thing to ask of whoever looks after it.

The post Simple Network Management (SNMP): What It Means (Simplest Form) appeared first on Orbit Computer Solutions.

So what is Spanning Tree Protocol?

Spanning Tree Protocol, usually shortened to STP, is the system that keeps the network of switches inside a building from forming loops. A loop is simply more than one path between the same two points, and on a local network a loop is surprisingly dangerous.

It was invented by Radia Perlman back in 1985 and later written into an international standard, and the basic job hasn’t changed since: let a network have backup links for resilience, while making sure those backups never quietly form a loop that brings everything down.

You can think of it as a referee for your cabling. It looks at every possible path through the network, picks a sensible set that reaches everywhere without doubling back, and benches the rest until they’re needed.

Why a loop is so dangerous

Inside an office, switches move traffic around by flooding certain messages to every port until they learn where everything lives. If there are two paths between two switches, those messages can go round and round the loop, forever, multiplying as they go.

Within seconds you get what’s called a broadcast storm: the network fills with the same traffic echoing endlessly, the switches are overwhelmed, and real traffic can’t get through. To everyone in the building it looks like the whole network has simply died, all at once.

The cruel irony is that loops are usually created with the best of intentions. You add a second cable between two switches so there’s a backup if one fails. Without something watching over it, that act of caution is exactly what creates the loop.

How STP keeps the peace

STP’s solution is rather elegant. All the switches talk to each other and elect one of them as the reference point, the root. Each switch then works out its best path back to that root and quietly switches off any other path that would create a loop. The blocked links aren’t gone; they’re held in reserve.

The clever part is what happens when something fails. If the main link a switch was using goes down, STP notices, recalculates, and brings one of those reserved backup links into service. You get the resilience of having spare cabling without the danger of a loop. The wider internet runs on the same idea one level up, healing around failures out on the backbone. You plug in two paths for safety, and STP makes sure only one of them is ever live at a time.

Why this matters if you run a business

Like a lot of networking, STP is something you’ll never touch directly. Your switches handle it, and a well-built network has it working sensibly from day one. But it’s worth understanding for two opposite reasons.

The first is resilience. STP is the mechanism that lets a network have backup links at all. A properly designed network can lose a cable or a switch and keep running, because a spare path quietly takes over. That only works if the network was built with redundancy in mind, rather than as an afterthought.

The second is fragility. When STP is missing, misconfigured, or running on cheap unmanaged switches that don’t support it, a single careless loop can take everything down.

The hospital that went back to paper

The classic cautionary tale is Beth Israel Deaconess Medical Center in Boston. In November 2002 a single application began looping data across a network built almost entirely on simple switches that leaned heavily on spanning tree. The result was a network meltdown that came and went for the best part of four days. Staff fell back to paper records, lab results that normally took 45 minutes took five hours, and the emergency department had to divert patients. The network ended up being rebuilt from the ground up.

The everyday version

Most loops are far less dramatic. The common one is mundane: someone tidies a cupboard and plugs both ends of a spare cable into the same switch, or daisy-chains a little desk switch back into the wall. On a network with STP doing its job, that mistake is spotted and the offending path is blocked before anyone notices. On a network without it, the office goes dark until someone physically finds the cable.

You add a second cable for safety, and on a network without spanning tree, that very act of caution is what takes the whole office down.

The practical takeaway

You don’t need to learn spanning tree. You need a network that was set up by someone who has. In practice that comes down to a few things:

• Use proper managed switches. The cheapest unmanaged kind often don’t run spanning tree at all, which is precisely how an accidental loop turns into an outage.
• Design in redundancy on purpose. Backup links only help if the network was built to use them, with spanning tree configured to match, not bolted on later and hoped for.
• Switch on the modern safeguards. Newer versions and features, with names like RSTP, BPDU Guard and loop protection, make the network recover faster and stop a stray cable causing chaos. A good setup turns them on, and turns off the insecure ones, like automatic trunking.
• Keep an eye on it. Knowing that a backup link has taken over, or that something has started looping, before it spirals is the difference between a non-event and a very bad afternoon.

The short version

Spanning Tree Protocol is the referee that lets your network have backup cabling without those backups forming a loop that takes everything down. You’ll never configure it, but whether it’s set up properly is the difference between a spare link that quietly saves you and a single loose cable that floors the whole office.

The bottom line

Spanning Tree is one of those quietly brilliant pieces of plumbing that has been holding networks together since the 1980s. When it’s set up well you never think about it: links fail, backups take over, and nobody notices. When it’s missing or done badly, an ordinary mistake can take down everything at once.

The lesson for a business isn’t to understand the protocol. It’s to make sure the network underneath you was built properly, with real redundancy, sensible switches and the modern safeguards switched on, so that a single cable never gets to decide how your team’s afternoon goes.

If you’d like someone to take an honest look at how resilient your network actually is, that’s exactly the kind of thing we enjoy getting stuck into.

The post Spanning Tree Protocol (STP) Explained appeared first on Orbit Computer Solutions.

So what is BGP?

BGP stands for Border Gateway Protocol. In plain terms, it’s the standardised system the internet uses to exchange routing and reachability information between large networks. That’s the textbook definition, and it really is the heart of it, so let’s unpack it.

The internet isn’t a single network. It’s tens of thousands of separate networks stitched together: internet service providers, cloud platforms, mobile carriers, universities and big companies. Each of these is called an autonomous system, and each has its own number, an ASN, a little like a telephone area code.

BGP is the common language those networks use to talk to one another. Each one announces, in effect, “here are the ranges of internet addresses I can deliver traffic to,” and BGP gathers up all of those announcements so that any network can work out a path to any other. Without it, the separate pieces of the internet would have no agreed way to find each other.

The internet’s road signs

A helpful way to picture BGP is as the road signs and sorting office of the internet, rather than the vehicles or the roads themselves.

BGP doesn’t carry your data. It works out the route that data should take. Every network advertises which destinations it can reach and which neighbours it connects to. Routers then compare the available paths and choose the one that looks best, usually the one that crosses the fewest networks to get there.

Because every route carries a record of the networks it passes through, the system can avoid sending traffic round in circles, and each network gets to apply its own preferences about which way to send things. It’s updating constantly, too. If a link goes down somewhere, BGP notices that a route has disappeared and the rest of the internet quietly reroutes around the gap, often before anyone notices.

Why this matters if you run a business

You’ll almost certainly never configure BGP yourself. That job sits with your internet provider and your hosting or cloud platforms. But BGP underpins nearly everything your business relies on online: your website being reachable, your email arriving, your cloud software loading, your card payments going through.

The reason it’s worth knowing the name is that when BGP goes wrong, it tends to go wrong in a big, visible way. A few well-known examples make the point.

The day Facebook vanished

In October 2021, Facebook, Instagram and WhatsApp disappeared from the internet for around six hours. Nothing had been hacked. A faulty internal change withdrew the BGP routes that told the rest of the world where to find Facebook’s systems. The servers were still running; the directions to them had simply been erased, and for a while billions of people couldn’t load the sites at all. It rhymes with the internet’s address-book failures, where the names stop resolving instead.

Traffic sent the wrong way

Because networks largely take each other’s BGP announcements on trust, it’s possible for one to claim, by mistake or on purpose, that it can reach addresses it has no business handling. The result is a route leak or a BGP hijack: traffic meant for one place gets pulled somewhere else, causing outages or, in the worst case, giving someone the chance to snoop on it. It has happened to banks, payment networks and large online services.

The “512k day”

Back in 2014, the global list of internet routes grew past a limit that a lot of older routers had been set up to hold, around 512,000 entries. Hardware around the world started misbehaving on the same day, and chunks of the internet slowed or dropped out. It was a useful reminder that even the internet’s plumbing has finite limits that have to be managed.

BGP is one of those foundations you only ever meet on the day it fails. The rest of the time, it works silently, which is exactly why so few people have heard of it.

The practical takeaway: stay reachable

For most small and growing businesses, the lesson isn’t to go and learn BGP. It’s to make sure your business isn’t sitting on a single weak link. A few sensible habits cover most of it:

• Choose well-connected providers. Good hosting and cloud platforms reach the internet through several networks at once, so if one path has a bad day your services stay reachable through another. That’s the resilient version of what BGP makes possible.
• Have a fallback for your own connection. A second line or a mobile failover means one provider’s outage doesn’t take your whole office offline with it.
• Keep an eye on your systems. Monitoring that tells you something has become unreachable, ideally before your customers find out, turns a quiet crisis into a quick phone call.

A word on security

BGP was designed decades ago, in a more trusting era, and it largely assumes networks are telling the truth about which addresses they can reach. That assumption is exactly what makes hijacks possible.

The wider industry has been steadily fixing this with measures that let networks verify whether a route really is coming from its rightful owner. You don’t need to implement any of that yourself. It’s simply one more reason to choose infrastructure providers who take it seriously, and to treat the security of your connectivity as part of the picture rather than an afterthought.

The short version

BGP is the set of directions that lets the internet’s thousands of separate networks find one another, so your data reaches the right place. You’ll never touch it. But the providers you build on either look after it well, with good connections and sensible security, or they don’t, and that difference tends to show up on the day something breaks.

The bottom line

Almost all of the time, BGP works flawlessly and invisibly. When it does break it’s dramatic, and it’s usually entirely out of your hands. What is in your hands is what you choose to build on. Solid, well-connected hosting, a connection with a fallback, and a bit of monitoring all mean the rare bad day out on the wider internet is far less likely to become a bad day for your customers.

If you’d like a straightforward look at how resilient your connectivity and hosting actually are, with no jargon and no pressure, that’s exactly the kind of conversation we enjoy having.

The post So what is BGP? Border Gateway Protocol Explained (2026) appeared first on Orbit Computer Solutions.

First, what a trunk is

To see why DTP matters, you need the idea of a trunk, and for that you need VLANs.

A VLAN, or virtual LAN, is a way of slicing one physical network into several logical ones. The guest wifi, the staff computers, the card terminals and the security cameras can all share the same switches and cabling while behaving as though they sit on separate networks that cannot see each other. It is one of the most common and most useful boundaries in any building’s network.

Most ports on a switch carry just one VLAN. These are access ports: the computer on a desk belongs to the staff VLAN and nothing else. The links between switches, though, have to carry every VLAN at once, kept apart by a small label stamped onto each frame as it crosses. A link like that is a trunk, and the labelling follows an open IEEE standard, 802.1Q. Trunks are how a building full of switches still manages to behave like a tidy set of separate, isolated networks. Those same inter-switch links are also where spanning tree does its quiet work, keeping a redundant path from becoming a loop.

What DTP was built to do

Configuring every trunk by hand, port by port, is tedious work, especially across a large site. Cisco’s answer, years ago, was to let the switches arrange it among themselves. Dynamic Trunking Protocol, DTP for short, is a Cisco protocol that lets two switches negotiate whether the link between them should become a trunk, and how it should be labelled, with nobody configuring either end.

A port taking part in DTP sits in one of a handful of modes. In dynamic desirable it actively asks the far end to form a trunk. In dynamic auto it waits to be asked, and agrees if it is. Stand a desirable port next to an auto port, or two desirable ports together, and a trunk forms on its own. The two static modes, access and trunk, pin the port as one or the other, and a separate command can switch the negotiation off altogether. For a long time the out-of-the-box default on many Cisco switches was one of the dynamic modes, which means a switch taken fresh from the box is often willing to strike up a trunk with whatever appears on the wire.

The exact default has shifted over the years and varies by model and software version, so the honest answer to “is DTP active here?” is almost always “check, do not assume”. Plenty of live networks still have ports sitting in a dynamic mode without anyone ever having chosen it. For an engineer wiring a comms cabinet, that automatic behaviour really is convenient. The trouble is who else gets to ask.

Where the convenience becomes a hole

DTP has no meaningful idea who it is talking to. It assumes the device at the other end of the cable is a co-operative Cisco switch. There is nothing that says it has to be.

If a port is sitting in a dynamic mode, a laptop running the right tool can speak DTP back to the switch, announce itself as a switch, and negotiate a trunk. The instant that trunk comes up, the laptop stops being a single device on a single VLAN and starts receiving the traffic of all of them. The neat separation between guest wifi, internal systems and payment devices simply dissolves for that machine. This is the best-known form of an attack called VLAN hopping, and the DTP-driven version is known as switch spoofing.

None of this is hard or hypothetical. Picture the steps. Someone finds a live network socket that nobody is watching: a point in a meeting room, an unused desk in reception, the port behind a screen in a waiting area. They plug in a laptop. A free tool such as Yersinia sends the DTP frames. The switch, still in its helpful default, agrees to form a trunk. And the visitor now has a view of every VLAN on that switch. It is a standard opening move in physical penetration tests, precisely because it works so often. There is a second VLAN-hopping trick, known as double tagging, that abuses the native VLAN rather than DTP, but switch spoofing is the one DTP serves up directly.

Why a business should care

It is tempting to file all this under things for the IT team to fret about. But the reason those VLANs exist is almost always a decision the business has already made, even if it was never written down as a security policy.

Keeping card-payment devices apart from everything else is frequently a hard requirement under standards like PCI DSS, not a nice-to-have. Separating guest wifi from internal systems is the entire reason guest wifi is its own VLAN in the first place. Corralling cameras, door entry and other internet-connected gadgets onto their own segment is how a cheap device with sloppy firmware is stopped from becoming a route into everything important. When DTP lets someone trunk in, all of that quietly comes undone. The segmentation you depend on, and may well be audited against, turns out to be optional for anyone who can reach an unguarded socket.

It also sidesteps most of the controls people assume will protect them. A locked server room does nothing about a network point in an open meeting room, and a firewall sitting at the edge of the network never sees the traffic that is hopping between VLANs inside it. Put plainly: a single unattended port in a reception area should never be a master key to the whole network. Where DTP has been left switched on, that is sometimes exactly what it is.

Turning it off, and trunking on purpose

The fix is well established and costs nothing but a little attention. The rule of thumb is that a port should always be told what it is, and never left to work it out by negotiation.

For the ports that people actually plug into, that means fixing them as access ports with switchport mode access, so they stay in a single VLAN and stop speaking DTP altogether. For the real links between switches, it means declaring them trunks deliberately with switchport mode trunk and then adding switchport nonegotiate, which turns DTP off on that link so it will not auto-trunk with whoever asks. While you are in there, it is good practice to move the native VLAN off the default VLAN 1 and onto an unused one, which closes the double-tagging door at the same time.

Confirming the current state is just as quick: a look at a port’s settings, with a command like show interfaces switchport, tells you which mode it is in and whether negotiation is on, and monitoring can flag a port that has negotiated a trunk it never should have. On an estate of any size, that check belongs in the standard build for every switch, not a one-off tidy-up.

This is not fringe or paranoid advice. Disabling features you do not use and changing insecure defaults is the heart of secure configuration, one of the five controls in the UK’s Cyber Essentials scheme, and turning DTP off specifically is set out in Cisco’s own hardening guidance and in essentially every serious switch baseline. On a network built by someone who knows the terrain, DTP is simply off, and trunks exist only in the handful of places they were deliberately created.

The pattern worth noticing

DTP is a small instance of a much larger theme. Networks are full of features designed in a more trusting time and left on by default because they smoothed the path for whoever installed the kit, back when the only things that ever plugged in were other trusted devices. Open offices, public spaces and a market full of cheap attack tools changed the threat. The defaults, very often, did not change with it.

You do not need to know which features those are. Working that out is the job of whoever designs and maintains your network. What is reasonable is to expect that the question has been asked at all, and that the convenient defaults have been switched off wherever they quietly trade your security for someone else’s saved ten minutes. If you cannot say for certain whether that has happened on your own network, it is worth finding out.

The post Cisco Dynamic Trunking Protocol (DTP): The Default Worth Turning off appeared first on Orbit Computer Solutions.

What it actually does

A firewall sits at the boundary between two networks, usually between yours and the internet, and decides what is allowed to cross. Every piece of traffic trying to get in or out is checked against a set of rules, and anything that does not match is dropped. A sensible firewall runs on a simple and slightly unfriendly principle: deny everything by default, and only allow the specific things you have chosen to permit.

That is really the whole idea. It is less a wall than a doorman with a guest list. Traffic for the services you actually run, your website answering visitors, your email coming and going, is on the list and waved through. The constant background noise of the internet, the automated scans and probes hunting for a way in, is not on the list, so it never reaches the door. Good monitoring is what turns all that blocked, invisible noise into something someone can actually review.

Why it still matters with everything in the cloud

It is tempting to assume firewalls matter less now that so much lives in the cloud. The opposite is closer to the truth: the boundary has simply moved and multiplied. There is still one around your office network, there are firewalls built into every decent cloud platform, and there is one on every laptop and server worth its salt. Each enforces the same deny-by-default rule in its own corner.

For most small businesses the firewall is the quiet workhorse behind a few things you would notice at once if they stopped: keeping the guest wifi away from the till system, stopping one compromised laptop from reaching everything else, and making sure the only ways into your network are the ones you chose (a VPN is usually one of them). Holding that perimeter is exactly what the UK’s NCSC guidance on network architecture asks for, so for many businesses it is a baseline expectation rather than a nice-to-have.

Where firewalls quietly go wrong

Firewalls rarely fail dramatically. They fail quietly, by being too generous. The classic problems are all the same theme: a rule opened up for a quick test years ago and never closed, a management page left reachable from the internet, a default setting left exactly as it shipped.

None of that shows up as an error. The firewall carries on doing precisely what it was told, which is the point. The value was never in having a firewall, since almost everyone does. It is in someone occasionally checking that its list of who gets in still matches how your business actually works today. If nobody has looked at yours in a long while, that is the part worth changing.

The post What A Firewall Actually Does (Simple Explanation) appeared first on Orbit Computer Solutions.

The internet’s address book

Computers do not find each other by name. They find each other by number, an IP address, a string like 172.217.16.196 that means nothing to a person and everything to a machine. DNS is the system that translates between the two, turning the orbit-computer-solutions.com you type into the numbered address your browser actually connects to. It is, in the well-worn phrase, the address book of the internet.

The lookup itself is a short relay race that runs behind the scenes:

1. Your device asks a resolver, usually run by your internet provider (one it was handed automatically when it joined the network), “where do I find this name?”
2. If the resolver does not already know, it works up the chain, asking the servers responsible for that domain.
3. The answer, an IP address, comes back, and gets remembered for a while so the next lookup is instant.
4. Your browser connects to that address, and the page loads.

All of that finishes in the blink before a page appears, millions of times a second, all over the world.

The day the address book went down

The best way to appreciate DNS is to watch what happens when it fails. On 21 October 2016, a company called Dyn, which ran the DNS for a large slice of the web, was hit by a huge attack. The websites themselves were perfectly fine. Their servers were running and their data was intact. But with Dyn’s DNS knocked offline, the rest of the internet could no longer look up where they were. For much of a day, Twitter, Spotify, Reddit, Netflix and dozens of others were unreachable for millions of people, not because they were down, but because nobody could find them.

That is the strange power of DNS. It does not store your website or your email. It only holds the directions to them. Lose the directions, and everything else may as well not exist. It is the same fragility behind the internet’s great routing outages, where the paths between networks vanish rather than the names.

Why it matters for your business

You depend on DNS far more than you might think, and usually through a handful of records most business owners have never seen. One record points the world at your website. Another, the MX record, tells the world where to deliver your email. Others quietly vouch that your email is genuine and help it land in inboxes instead of spam folders. Set out in the standards back in the 1980s and barely changed since, these records are the foundation almost everything else sits on.

Which is exactly why DNS mistakes hurt so much. A single mistyped record can send your email into a black hole. A lapsed domain can take your entire online presence offline overnight. A change made carelessly can take hours to ripple out across the world’s resolvers, a delay known as propagation, during which some visitors see the new version and some the old. None of these are exotic failures. They are ordinary slips, and they are common precisely because DNS is so easy to ignore until it bites.

Looking after it

For a business, DNS is not something to manage day to day. It is something to get right once and then leave well alone, in the hands of someone who treats it with care. In practice that comes down to a few quiet habits: never letting the domain registration lapse, knowing exactly who controls your DNS records, changing them deliberately rather than in a rush, and using a dependable DNS provider rather than whatever came bundled years ago. It is also worth checking it does not quietly slip out of the tunnel when your team is on a VPN.

It is unglamorous, and that is rather the point. Good DNS is invisible. The only time you are likely to think about it is the day something goes wrong, and the entire aim is to make sure that day never arrives.

The post DNS Explained: the internet’s address book, and the day it failed appeared first on Orbit Computer Solutions.

The switch: the office’s internal post room

A switch connects the devices inside your network to each other. The computers, printers, phones, servers and wifi access points all plug into it, and its job is to move data between them quickly and only to the right place. When your laptop sends a document to the printer down the hall, the switch is what makes sure it reaches that printer and not everyone else’s screen.

Think of it as the post room of the building. It knows which desk is which, takes an internal envelope, and delivers it straight to the right recipient without bothering anybody else. It is fast, it is local, and it has no real interest in the world outside the building. A bigger office simply has more switches, or larger ones, all doing the same neighbourly job. Wire several together with a spare link for resilience, though, and something has to stop that redundancy becoming a loop.

The router: the office’s front door to the world

A router does something different. It connects your network to other networks, above all to the internet. Where a switch moves traffic within the building, a router decides how traffic gets between buildings, and finds a path out to wherever it is heading. Every time someone loads a website or sends an email beyond the office, it leaves through the router.

If the switch is the internal post room, the router is the front door and the mailroom that deals with the outside world. It handles everything coming in and going out, works out where external post should be sent, and is usually where your firewall and your connection to your internet provider live. There is generally just one main one, and it is the thing that genuinely matters on the morning “the internet is down”.

Why the distinction is worth knowing

In a small office the two often arrive fused into a single unit. The box your internet provider supplies is usually a router, switch and wifi access point rolled into one, right down to handing out every device’s address, which is exactly why the words get muddled. That is perfectly fine when you are small. It tends to stop being fine as you grow, when one shared box is trying to do three demanding jobs at once and doing none of them especially well.

The practical value of telling them apart is that it makes problems, and upgrades, far easier to reason about. Slow file transfers between machines in the office point at the switching side. Trouble reaching the outside world points at the router or the connection. Keeping the guest wifi separate from the till system, or adding a resilient backup internet line, are decisions about how those boxes are arranged. You do not need to design any of that yourself. But knowing there are two jobs here, not one, is the difference between a network that was thrown together and one that was actually planned.

The post Routers and Switches Explained: What Each One Actually Does appeared first on Orbit Computer Solutions.