Octet

Say this first

A stub area blocks Type 5 externals, and so Type 4, and the ABR injects a default route as a Type 3. A totally stubby area also blocks Type 3 summaries, so internal routers only see their own area plus one default. Every router in the area needs area X stub. Only the ABR adds no-summary for totally stubby.

Go deeper

Comparison

Area type	Type 3	Type 4	Type 5	Type 7	Default route
Normal	Yes	Yes	Yes	No	Only if originated
Stub	Yes	No	No	No	Type 3 from ABR, automatic
Totally stubby	Only the default	No	No	No	Type 3 from ABR, automatic
NSSA	Yes	No	No	Yes	Not automatic on IOS
Totally NSSA	Only the default	No	No	Yes	Type 3 from ABR, automatic

Config

Cisco IOS

! ABR R2, area 1 totally stubby
router ospf 1
 area 1 stub no-summary
!
! Internal router R1 in area 1
router ospf 1
 area 1 stub

Rules

The stub flag is in every hello. Every router in the area must agree or adjacencies fail.
No ASBR inside a stub area. Use NSSA if you need one.
Area 0 can never be a stub.
A stub area cannot be the transit area of a virtual link.
area 1 default-cost 10 on the ABR changes the cost of the injected default (default 1).

Result on R1

Output

O*IA  0.0.0.0/0 [110/2] via 10.0.12.2, 00:01:05, GigabitEthernet0/0/0

They will ask next

Is totally stubby a standard feature?
It started as a Cisco extension and is not in RFC 2328, but most vendors support it. Junos uses stub no-summaries on the ABR.
Do internal routers need no-summary too?
No. It only changes what the ABR originates. Adding it on an internal router does nothing.

Traps

Configuring area 1 stub on the ABR only. Internal routers then refuse the ABR's hellos.
Saying stub areas block Type 3. Only totally stubby does, apart from the default.

How did you do?