Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Operating system: Fedora 16 x86_64

I am trying to understand the problems of the following. We use a local domain in our intranet (.local). The names are resolved correctly with and without .local:

$ host portal
portal.local has address 10.22.33.17
$ host portal.local
portal.local has address 10.22.33.17

However, trying to access FQDN fails:

$ ping portal
PING portal.local (10.22.33.17) 56(84) bytes of data.
64 bytes from portal.local (10.22.33.17): icmp_req=1 ttl=64 time=0.171 ms
^C
--- portal.local ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.171/0.171/0.171/0.000 ms

$ ping portal.local
ping: unknown host portal.local

/etc/resolv.conf:

search local
nameserver 10.22.33.1
nameserver 8.8.8.8
nameserver 8.8.4.4

Where can be the origin of the above DNS problem? Thanks

share|improve this question
    
/etc/nsswitch.conf? –  Ignacio Vazquez-Abrams May 30 '12 at 3:41
    
The line of interest: hosts: files dns –  Konstantin Boyandin May 30 '12 at 3:44
1  
... Wait. You're using .local without mDNS? –  Ignacio Vazquez-Abrams May 30 '12 at 3:45
    
The line hosts: files mdns4_minimal [NOTFOUND=return] dns doesn't work in exactly the same manner, .local FQDNs don't resolve. –  Konstantin Boyandin May 30 '12 at 3:46
    
I have found a solution, using hosts: files mdns4_minimal dns [NOTFOUND=return] mdns4 line instead, but can't answer my question at the moment. Thanks for the hint. –  Konstantin Boyandin May 30 '12 at 3:56
show 1 more comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.