home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.protocols.tcp-ip      TCP and IP network protocols.      14,669 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 13,727 of 14,669   
   glen herrmannsfeldt to KP Bhat   
   Re: Non-qualifed hostname resolution in    
   17 Mar 11 21:38:40   
   
   f40160cc   
   XPost: comp.protocols.misc, comp.sources.d   
   From: gah@ugcs.caltech.edu   
      
   In comp.protocols.tcp-ip KP Bhat  wrote:   
      
   > I have a question regarding DNS.  My experience has been that DNS   
   > servers always automatically combine a unqualified hostname with the   
   > default domain name in order to determine the fully qualified domain   
   > name.  Is this behavior specified in some RFC, or is this just how the   
   > DNS Servers are implemented?  If this is specified in some RFC, can   
   > someone kindly provide a reference?  If not, do we know of any DNS   
   > implementations for which this behavior does not hold?   
      
   As far as I know, DNS servers never do that.   
      
   DNS clients have a list of domains to append to the supplied name,   
   and will request the qualified name in turn, followed by the   
   name as given.   
      
   For unix, this is part of the resolver, specified in the   
   /etc/resolv.conf file.   
      
   Also, DHCP servers can supply the list of domains to a DHCP client.   
   IF you DNS server is also a DHCP server, then look in the DHCP   
   configuration.   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca