[Samba] host command output showing wrong domain (Samba4)

[Harry Jede]

On 11:13:52 wrote Fosiul Alam:
> Hi
> I never seen this before, and dont understand where too look for
> 
> Please share some light on this.
> 
> the host output is adding a extra domain.
> 
> example bellow, its showing right IPs followed by NXDOMAIN !!!
> 
> 
> [root at 171-SYSLOG ~]# host  171-dc-a.xxxx.acc
> 171-dc-a.test.acc has address 10.254.228.226
> 171-dc-a.test.acc has address 10.254.225.45
> Host 171-dc-a.test.acc not found: 3(NXDOMAIN)
> Host 171-dc-a.test.acc not found: 3(NXDOMAIN)
> 
> now if i do host -v , look how its works
> 
> 
> 
> [root at 171-SYSLOG ~]# host -v  171-dc-a.test.acc
> Trying "171-dc-a.test.acc"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15208
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;171-dc-a.test.acc.          IN      A
> 
> ;; ANSWER SECTION:
> 171-dc-a.test.acc.   900     IN      A       10.254.228.226
> 171-dc-a.test.acc.   900     IN      A       10.254.225.45
> 
> Received 70 bytes from 10.254.228.226#53 in 1 ms
> Trying "171-dc-a.test.acc"
> Received 38 bytes from 10.254.228.226#53 in 0 ms
> Trying "171-dc-a.test.acc.test.acc"   
> ------------------------------------ Host 171-dc-a.test.acc not
> found: 3(NXDOMAIN)
> Received 50 bytes from 10.254.228.226#53 in 0 ms
> Trying "171-dc-a.test.acc"
> Received 38 bytes from 10.254.228.226#53 in 0 ms
> Trying "171-dc-a.test.acc.test.acc"
> -----------------------------------------
> Host 171-dc-a.test.acc not found: 3(NXDOMAIN)
> Received 50 bytes from 10.254.228.226#53 in 0 ms
> [root at 171-SYSLOG ~]#
> 
> 
> As you can see its adding double domain.
> 
> Trying "171-dc-a.test.acc.test.acc"
> 
> any idea why host output doing this ??
> 
> dig command is good
> 
> [root at 171-SYSLOG ~]# dig +short 171-dc-a.test.acc @10.254.228.226
> 10.254.228.226
> 10.254.225.45
> [root at 171-SYSLOG ~]#
> 
> Note : here bellow 2 ips are same server ip
> 
> 10.254.228.226
> 10.254.225.45

host reads /etc/resolv.conf, dig does not.
So check your local resolv.conf at 171-SYSLOG.

-- 

Gruss
	Harry Jede