Bug 55942 – dig -X RFC 1918 private ranges fails

Bug 55942 - dig -X RFC 1918 private ranges fails


Summary:	dig -X RFC 1918 private ranges fails

Status:	RESOLVED DUPLICATE of bug 54796

Product:	UCS
Classification:	Unclassified
Component:	DNS
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-04-04 12:02 CEST by Mirac Erdemiroglu
Modified:	2023-10-09 09:22 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.057
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2023030921000226
Bug group (optional):	Regression
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Comment 1 Philipp Hahn

2023-10-09 09:22:28 CEST

192.168/16 is a *private* network, e.g. not routed. No *public* DNS server can and will provide an answer for such networks. Therefore it is considered rude to even forward such queries to *public* DNS servers. BIND therefore already blocks them internally by default, which can be disabled by setting `empty-zones-enable: no;`.

See https://kb.isc.org/docs/aa-00800

*** This bug has been marked as a duplicate of bug 54796 ***