Project

General

Profile

Actions
Copy link

Bug #12072

closed

FQDN L2TP server address is only resolved at boot

Added by Alex BJ almost 3 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
L2TP
Target version:
2.6.0
Start date:
06/23/2021
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.01
Release Notes:
Default
Affected Version:
2.4.5-p1
Affected Architecture:
amd64

Description

Hello!

Im using "russian vpn" scheme to connect with ISP - WAN interface with DHCP (actually internal ISP network) + L2TP interface to ISP server (as real WAN). If im using FQDN as L2TP server name - it couldn't be resolved during boot up, so i have start this interface manually. Even if i put static DNS entry for this server name to DNS resolver - its still couldn`t be resolver during boot. If i use ip as server address - everything is ok and L2TP interface going up automatically during boot.

Could someone fix this problem, because ISP balancing load between L2tp servers and returns different ip for same FQDN..

Actions
Copy link

Also available in: Atom PDF