Insights /Network, remote access and firewall

If only the internal DNS server is allowed to reach public port 53, does that also give employee computers internet access?

DNS resolution and web access are separate traffic flows. Allowing recursive DNS does not automatically open ports 80 or 443, but endpoint gateways, proxies, DoH, and other egress paths must still be checked.

If only the internal DNS server is allowed to reach public port 53, does that also give employee computers internet access?
Key assessment

Establish a factual baseline with “restricted recursive DNS sources” and “blocking direct public DNS from endpoints”, then move to “TCP/UDP 53 protocol coverage”. Use routing, policy, session state and real application traffic as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking restricted recursive DNS sources, blocking direct public DNS from endpoints and TCP/UDP 53 protocol coverage independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · restricted recursive DNS sourcesChecking restricted recursive DNS sources helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of restricted recursive DNS sources. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
02 · blocking direct public DNS from endpointsChecking blocking direct public DNS from endpoints helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of blocking direct public DNS from endpoints. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
03 · TCP/UDP 53 protocol coverageChecking TCP/UDP 53 protocol coverage helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of TCP/UDP 53 protocol coverage. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
04 · DoH/DoT bypass riskChecking DoH/DoT bypass risk helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of DoH/DoT bypass risk. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
05 · DNS logs and auditingChecking DNS logs and auditing helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of DNS logs and auditing. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
06 · boundary between web 80/443 and DNSChecking boundary between web 80/443 and DNS helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of boundary between web 80/443 and DNS. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.

Investigation and change sequence

  1. Capture a baseline for restricted recursive DNS sources and blocking direct public DNS from endpoints and compare it with a known-good system.
  2. Correlate evidence from TCP/UDP 53 protocol coverage and DoH/DoT bypass risk to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to DNS logs and auditing, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check boundary between web 80/443 and DNS and the real business workflow. Verify end-to-end business access, return routing and error logs, with a defined rollback check.

Validation and rollback evidence

  • Verify end-to-end business access, return routing and error logs, with a defined rollback check.
  • Recheck DNS logs and auditing and boundary between web 80/443 and DNS against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming restricted recursive DNS sources is sufficient while overlooking blocking direct public DNS from endpoints and dependent checks.
  • Changing several settings before preserving the original evidence for TCP/UDP 53 protocol coverage.
  • A successful port probe is not proof of application functionality; do not broaden access rules blindly.

Common questions and acceptance criteria

What should be checked first?

Begin with restricted recursive DNS sources and blocking direct public DNS from endpoints. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Verify end-to-end business access, return routing and error logs, with a defined rollback check.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

PreviousThe firewall port is open and a TCP test succeeds, so why does the application still fail to open?NextCan a stale WinHTTP proxy cause slow Office startup, activation, Windows Update, or service connectivity?

Need an assessment based on your actual environment?