ntpdate: error resolving ladder.local

[TrevorH]

And which of those 2 nameservers knows about ladder.local?

[n0rt0x]

The 2nd one, which is 10.18.11.2. So this means I can delete the other IP address and "localdomain" record?

[TrevorH]

Which explains your issue. DNS lookups consult the first nameserver listed and only if it does not respond with an answer will it consult the next one. Any answer at all from the first nameserver listed will stop it looking any further - so if you lookup a.a and the 1st nameserver in your list says "never heard of it" then that is the answer and it stops looking. Now you need to find out where the wrong one is coming from and remove it. Perhaps it's being handed out by DHCP?

[n0rt0x]

I checked all network config files but couldn't find any traces with a "localdomain" record in it, even through nmtui. Except for the swap config file I mentioned earlier, which I removed it there. But CentOS is still acquiring a "localdomain" record whenever I reboot the system, so I'm frankly out of idea's. The ens33 (NAT) is set on DHCP which is necessary because the Linux server needs to forward the internet connection to the Windows server, as what the school project describes. So my current work-around is to change the resolv.conf file each time I boot the system.

Are there any other relevant (config) files I can look into?

[n0rt0x]

Also noticed "localdomain" in a root mail i received this evening

Code: Select all

From root@trap1.localdomain  Fri Apr  5 22:07:05 2019
Return-Path: <root@trap1.localdomain>
X-Original-To: root
Delivered-To: root@trap1.localdomain
Received: by trap1.localdomain (Postfix, from userid 0)

[TrevorH]

It's not the localdomain thing that's your problem, it's the additional nameserver line pointing to a nameserver that doesn't know the thing you're trying to look up.

[n0rt0x]

Morning,

I'm happy to say that this issue is fixed, and it was rather easy
By toggling the DNS button on the ens33 NIC through gnome and rebooting, I'm only getting records from the internal network in the resolv.conf
Glad that this is over with. Anyway, thanks Trevor for thinking along in this matter.
This topic can be closed now.