Why does the name resolve to an obscure IP address?

Question

Computer networks

Good afternoon.
The computer has one IP address set in the settings, and another one persists when pinging. What is mysticism?
Windows Server 2016. Machine name: ast-srv. domain controller.
On command , it
ping ast-srv
resolves the name to 169.254.44.214 and the ping goes.
Real server address: 192.168.2.7 . Ping to this address also works. I get a response
on command .
nslookup ast-srv

Server: ast-srv.arida.local
Address: 192.168.2.7
Name: ast-srv.arida.local
Address: 192.168.2.7

The file "C:\Windows\System32\drivers\etc\hosts" has not been modified. Adding a line to it

192.168.2.7 ast-srv

Does not help.
Here is the command output
ipconfig /all

Windows IP Setting
Computer Name . . . . . . . . . : ast-srv
Primary DNS suffix . . . . . . : arida.local Node
type. . . . . . . . . . . . . : Hybrid
IP Routing is enabled. . . . : No
WINS proxy enabled. . . . . . . : No
DNS suffix lookup order. : arida.local
Ethernet Ethernet adapter:
Environment state. . . . . . . . : The transmission medium is not available.
Connection DNS suffix . . . . . :
Description. . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical address. . . . . . . . . : D0-27-88-67-12-27
DHCP is enabled. . . . . . . . . . . : Yes
Auto tuning is enabled. . . . . . : Yes
Ethernet Ethernet Adapter 4:
Environment status. . . . . . . . : The transmission medium is not available.
Connection DNS suffix . . . . . :
Description. . . . . . . . . . . . . : D-Link DGE-528T Gigabit Ethernet Adapter
Physical address. . . . . . . . . : 14-D6-4D-1C-83-BC
DHCP is enabled. . . . . . . . . . . : Yes
Auto tuning is enabled. . . . . . : Yes
Ethernet adapter vEthernet (LAN):
Connection DNS suffix . . . . . :
Description. . . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical address. . . . . . . . . : F8-D1-11-02-98-99
DHCP is enabled. . . . . . . . . . . : No
Auto tuning is enabled. . . . . . : Yes
Link-local IPv6 address. . . : fe80::501c:d8db:8c02:7ae3%25(Primary)
IPv4 address. . . . . . . . . . . . : 192.168.2.7(Main)
Subnet mask . . . . . . . . . . : 255.255.255.0 Default
gateway. . . . . . . . . : 192.168.2.5
IAID DHCPv6 . . . . . . . . . . . : 435736849
DHCPv6 client DUID . . . . . . . : 00-01-00-01-22-3F-E1-B8-D0-27-88-67-12-27
DNS servers. . . . . . . . . . . : 192.168.2.7
192.168.0.7
NetBios over TCP/IP. . . . . . . . :
Isatap tunnel adapter enabled.{372DBB6C-F113-4C9B-8D76-0F2E22C95B2E}:
Environment status. . . . . . . . : The transmission medium is not available.
Connection DNS suffix . . . . . :
Description. . . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP is enabled. . . . . . . . . . . : No
Auto tuning is enabled. . . . . . : Yes
Teredo Tunneling Pseudo-Interface:
Environment status. . . . . . . . : The transmission medium is not available.
Connection DNS suffix . . . . . :
Description. . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP is enabled. . . . . . . . . . . : No
Auto tuning is enabled. . . . . . : Yes
Tunnel adapter isatap.{4FC361D4-8C75-490F-AFF9-8044F5A6BBFA}:
The state of the environment. . . . . . . . : The transmission medium is not available.
Connection DNS suffix . . . . . :
Description. . . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP is enabled. . . . . . . . . . . : No
Auto tuning is enabled. . . . . . : Yes
Isatap tunnel adapter.{C592122B-BCF2-47DD-B5CF-11346148A364}:
Environment status. . . . . . . . : The transmission medium is not available.
Connection DNS suffix . . . . . :
Description. . . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP is enabled. . . . . . . . . . . : Not
Auto tuning is enabled. . . . . . : Yes

How to get rid of the wrong address? Where can he fly from?

Answer 1

The server has several network cards. Despite the fact that no cables were connected to the cards, they assigned themselves an IP address. And one of those cards was responding to a ping. After turning off the cards, everything became normal.
Thanks 20ivs for the reply.