Project

General

Profile

Actions

Bug #14288

closed

Setting system DNS servers can incorrectly modify routes for interface addresses

Added by Marcos M about 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.05.1
Release Notes:
Default
Affected Version:
2.5.1
Affected Architecture:

Description

Tested on 23.01

Using an address on lo0 (e.g. a localhost VIP or simply @127.0.0.1) as a DNS sever under System / General Setup results in a missing route for the specified address.

Example below after adding 127.0.0.1 (persists reboots):

[23.01-RELEASE][root@router.lab.arpa]/root: netstat -rn4
Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
default            10.0.5.1           UGS        vmx1
10.0.5.0/24        link#2             U          vmx1
10.0.5.75          link#2             UHS         lo0
172.19.0.0/20      192.0.2.4          UGS        vmx2
192.0.2.0/28       link#3             U          vmx2
192.0.2.1          link#3             UHS         lo0
192.0.2.200/29     link#11            U      vmx3.522
192.0.2.201        link#11            UHS         lo0
192.0.2.240/28     link#9             U      vmx3.521
192.0.2.241        link#9             UHS         lo0
192.168.0.0/20     198.51.100.2       UGS        vmx0
198.51.100.0/28    link#1             U          vmx0
198.51.100.1       link#1             UHS         lo0

Actions

Also available in: Atom PDF