Project

General

Profile

Actions
Copy link

Bug #11457

closed

Client DNS doesn't resolve when using VIP in place of interface IP

Added by Viktor Gurov about 3 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
02/19/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:

Description

https://forum.netgate.com/topic/161056/client-dns-doesn-t-resolve-when-using-vip-in-place-of-interface-ip:

"My inside interface is set to 192.168.1.1 and I created a VIP on .254. When I set a client device to use .254 as the gateway, I can verify the traceroute to the internet and connectivity to the internet is verified.

The problem is when I set the client device to use the VIP as the DNS host. No responses come back. All DNS entries fail to resolve. If I use nslookup and alternate between .1 (inside interface) and .254 (inside VIP) for queries, .1 always works and .254 always fails."

my test:

# dig a netgate.com @192.168.88.44
;; reply from unexpected source: 192.168.88.41#53, expected 192.168.88.44#53

192.168.88.41 - LAN IP, 192.168.88.44 - LAN CARP VIP

it's better to hide all VIPs from the DNS Resolver "Network Interfaces" list

Actions
Copy link

Also available in: Atom PDF