← Security and privacy

Names and addresses

Every device on the internet has an IP address, and every packet carries the address it is going to. DNS turns a name like school.edu.au into that address, and routers use their tables to send each packet the right way. A name that only looks right gets a different address, and a different computer.

You type a website's name, but computers find each other by numbers. Who turns the name into the number, and what happens if one letter is wrong?

On the internet, devices find each other by IP addresses: numbers such as 203.0.113.10. Every packet carries the address it is going to. People use names instead, so a DNS server (the Domain Name System) looks up the address for each name. Routers then read the address on each packet and use their tables to choose where to send it.

PredictRead the problem and decide what you think before you try anything. A wrong guess is fine: it shows you what to look for.

One letter different

An email links to **schoo1.edu.au** (a number 1 instead of the letter l). The real site is **school.edu.au**. Where will the link take you?

TryTry it on the board and compare the result with your prediction.

Try: look them up

Was your prediction right? Compare the router table row each one used.

Try it yourselfYour edits are saved in this browser.

Press Go for school.edu.au, then look up schoo1.edu.au. Where does each one go?

Use the board. This ticks when you get there.

InvestigateWork out why it happens, one step at a time.

Worked example: following a name

Worked exampleBefore each step, say what you think comes next.
  1. school.edu.au→DNS\text{school.edu.au} \to \text{DNS}Your laptop asks a DNS server for the name's address.

Now say what DNS does.

What does DNS do?

Sam decides an email link is safe. Click the line where it first goes wrong.

Your laptop at home is 192.168.1.23, but websites see 198.51.100.7. Why?

ModifyChange the problem on purpose and see what happens.

Vary: one name at a time

Try it yourselfYour edits are saved in this browser.

Look up library.school.edu.au. Which router row sends it?

Use the board. This ticks when you get there.

Look up weather.example.

Use the board. This ticks when you get there.

Look up a name that doesn't exist, such as nowhere.example.

Use the board. This ticks when you get there.

Why does the router only look at the start of the address?

PractiseA few on your own, to check you have it.

Names and addresses

Which link goes to the real school site **school.edu.au**?

What does an IP address identify?

Review: where does HTTPS encrypt your data?

MakeMake your own problem using what you have learned. Expect a few tries; that is normal.

Check before you click

Then: write one rule for checking a link before you click it.

Try it yourselfYour edits are saved in this browser.
Need a hint?

Look up each name and compare its address with the school's.

Another hint

The school's portal is at 203.0.113.10.

Another hint

A name that ends in exactly school.edu.au goes to the school.

An email offers these links: schoo1.edu.au, school.edu.au, library.school.edu.au. Look up all three, and finish on one that reaches the real school portal.

Use the board. This ticks when you get there.

For teachers

Students look up names in a DNS board and follow each packet's address through a router table, to explain how domain names and IP addresses get data to the right computer and why a lookalike name is dangerous (AC9TDI10K01 node 2). About 40 minutes.

Open the teacher guide: answers, solutions, slides and a worksheet.

Students will be able to

Before class

Try the board yourself. Every address on it comes from the ranges kept for documentation and examples (192.0.2.x, 198.51.100.x, 203.0.113.x), so none is a real site.

The one idea: names map to addresses through DNS, packets carry addresses, routers forward by the start of the address. Lookalike names (phishing) reach other computers.

Hands-on: on a school computer, nslookup or ping a well-known site to see a real address (check the school network allows it).

Running the lesson

  1. Predict: students who chose "DNS fixes typos" hold Sam's misconception.
  2. Try: ask whose computer 198.51.100.66 might be.
  3. Worked example: compare the router table with postcodes.
  4. Vary: ask why nothing is sent for a name that doesn't exist.
  5. Make: collect students' rules for checking links.

The hard part (on purpose)

The difference between a name looking right and being right. Make students read names character by character, aloud.

When students get stuck

Stretch and support

Stretch: IPv4 addresses have four numbers from 0 to 255. How many is that, and why did the world run out? (About 4.3 billion; look up IPv6.)

Support: Show a name split into parts (library . school . edu . au) and read it right to left.

Where it leads

Next: Who are you, and what may you do? (sign-in and permissions).

Builds on: Networks (packets and routers). Links to Data representation: each part of an IPv4 address is one byte.

What each step is for

Now you can
Next lesson3. Who are you, and what may you do?Access control has two parts. Authentication proves who you are (a password, and with multi-factor sign-in a code from your phone too). Authorisation (permissions) then decides what you may do. Give each role only what its job needs: least privilege.