Re: CentOS 8 DNS resolution not working as expected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Pete Biggs writes:
> On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote:
> > [root@localhost ~]# lsb_release -d
> > Description:	CentOS Linux release 8.2.2004 (Core) 
> > [root@localhost ~]# cat /etc/resolv.conf 
> > # Generated by NetworkManager
> > search subdomain.company.com company.com
> > nameserver 1.2.3.4
> > nameserver 5.6.7.8
> > 
> > [root@localhost ~]# host foo
> > foo.subdomain.company.com has address 1.2.3.4
> > 
> > [root@localhost ~]# host foo.subdomain
> > Host foo.subdomain not found: 3(NXDOMAIN)
> > 
> > [root@localhost ~]# host foo.subdomain.company.com
> > foo.subdomain.company.com has address 1.2.3.4
> > [root@localhost ~]# 
> > 
> > The expected result is that the lookup for foo.subdomain works, like it does under CentOS < 8.
> 
> man host
> 
>        -N ndots
>            The number of dots that have to be in name for it to be considered absolute. The default value is that defined using
>            the ndots statement in /etc/resolv.conf, or 1 if no ndots statement is present. Names with fewer dots are interpreted
>            as relative names and will be searched for in the domains listed in the search or domain directive in
>            /etc/resolv.conf.

As per man resolv.conf, the default setting hasn't changed. It is n=1 on all of CentOS 6/7/8.

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux