nerdexam
IBM

000-221 · Question #11

Name resolution is not working on a given LPAR. Considering the observed behavior and configuration of/etc/resolv.conf, what is the most likely resolution?

The correct answer is B. Remove the domain line. In /etc/resolv.conf, the 'domain' and 'search' directives are mutually exclusive - having both causes the 'domain' entry to override the 'search' list, breaking name resolution for hosts in other search domains.

Troubleshooting and Problem Determination

Question

Name resolution is not working on a given LPAR. Considering the observed behavior and configuration of/etc/resolv.conf, what is the most likely resolution?

Exhibit

000-221 question #11 exhibit

Options

  • ACorrect the definition of nameserver1.
  • BRemove the domain line.
  • CVerify the syntax in /etc/nelsvc.conf.
  • DMove the search definition to the beginning of the file

How the community answered

(53 responses)
  • A
    13% (7)
  • B
    75% (40)
  • C
    8% (4)
  • D
    4% (2)

Why each option

In /etc/resolv.conf, the 'domain' and 'search' directives are mutually exclusive - having both causes the 'domain' entry to override the 'search' list, breaking name resolution for hosts in other search domains.

ACorrect the definition of nameserver1.

The nameserver directive syntax is not the source of the failure; the conflict between the 'domain' and 'search' directives is the actual problem.

BRemove the domain line.Correct

Removing the 'domain' line eliminates the conflict because resolv.conf treats 'domain' and 'search' as mutually exclusive directives. When both are present, 'domain' supersedes 'search', restricting DNS lookup to a single suffix and causing failures for any hostname not in that one domain. Keeping only 'search' restores the intended multi-domain suffix list behavior.

CVerify the syntax in /etc/nelsvc.conf.

The filename given is '/etc/nelsvc.conf', which does not exist on AIX - the correct file is '/etc/netsvc.conf', making this option invalid as written.

DMove the search definition to the beginning of the file

The position of the 'search' directive within the file does not affect resolver behavior; the mutual exclusion conflict between 'domain' and 'search' is the root cause.

Concept tested: resolv.conf domain vs search directive conflict

Source: https://www.ibm.com/docs/en/aix/7.3?topic=f-resolvconf-file

Topics

#name resolution#resolv.conf#DNS configuration#netsvc.conf

Community Discussion

No community discussion yet for this question.

Full 000-221 Practice