WWW Content
failure
1x weight
estimate
WWW Content. DNS name not resolving (can't even reach the web server)
Website cannot be reached
Events
1,470
Pts per check
1.4
Pts missed
2,041.7
Teams hit
9/13
Authority mappings
Which work roles, knowledge units, and EWU courses this error pattern touches. Hover for context, click to drill in.
DCWF roles:
CE-463 Host Analyst
CS-622 Secure Software Assessor
IT-421 Database Administrator
IT-451 System Administrator
SE-461 Systems Security Analyst
What the message means
The scoring engine is trying to fetch `http://team<N>.ncaecybergames.org/` by DNS name (not IP). The name isn't resolving. This is a DNS EXT FWD problem masquerading as a WWW Content problem. Fix DNS first.
Why the service is down
- External DNS A record for team<N>.ncaecybergames.org is not resolvable.
- Your BIND serves a different name than the scoring engine queries.
- Router port 53 not forwarded (so no one can query your DNS).
Commands in order
-
1. 1. What name is the scoring engine querying?
# from the packet: typically team<N>.ncaecybergames.org # Confirm by checking halftime-report or post-comp reportExpecte.g., team14.ncaecybergames.orgInterpret and nextLock this in. students will test against it next. -
2. 2. Does your DNS serve this name?
dig @<router-external-IP> team<N>.ncaecybergames.org A +shortExpectYour web server's IP (e.g., 172.18.<N>.X)Interpret and nextEmpty = either router forwarding missing OR zone file doesn't have this A record. -
3. 3. Verify the A record is in the zone file
grep -r 'team<N>' /etc/bind/db.*ExpectLine: team<N>.ncaecybergames.org. IN A <web-IP>Interpret and nextMissing = add the record, bump the SOA serial, reload BIND. -
4. 4. If DNS is fine but scoring still fails
curl -v http://team<N>.ncaecybergames.org/ 2>&1 | headExpectResponse body or headersInterpret and nextIf it works locally but fails externally, go back to router NAT for port 80.
Decision tree
Answer each question to route to the right fix.
Q: Does dig for team<N>.ncaecybergames.org return an IP?
Yes:
Curl externally. If that also works, scoring will pick up in next tick.
No:
Fix DNS first (EXT FWD playbook).