Project

General

Profile

Actions
Copy link

Bug #15789

closed

Adding IPv4 hostnames using the DNS Forwarder catches A record requests to the host's FQDN but not AAAA record requests

Added by Nathan Ladwig 13 days ago. Updated 13 days ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DNS Forwarder
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.x
Affected Architecture:

Description

I have an IPv4-only VLAN that is adding hostnames to DNS using the features available under the DNS Forwarder tab.

I have a domain, netham45.org, that has a wildcard pointing to Cloudflare for IPv4 and IPv6 on the public internet. Within my local network hosts should be overridden, so that <host>.netham45.org points to the internal IP. This works for A records, but I am still getting AAAA records returned from CloudFlare.

Example:

nslookup homeassistant

Server: UnKnown
Address: 192.168.3.3

Name: homeassistant.netham45.org
Addresses: 2606:4700:3037::6815:291e < Cloudflare provided AAAA record
2606:4700:3036::ac43:9f7e < Cloudflare provided AAAA record
192.168.3.144 < pfSense provided A record

I imagine there's a few ways to fix this but the one that makes the most sense to me is if pfSense knows of an A record provided by DHCP it should not provide an AAAA record from upstream.

Actions
Copy link

Also available in: Atom PDF