Devlin Daley wrote:
For example, trying to get to when trying to ping www.cs.byu.edu
<http://www.cs.byu.edu/> I get a response back from
www.cs.byu.edu.mydomain.com <http://www.cs.byu.edu.mydomain.com/> .
This is very annoying. I have not changed any settings on the Linux
box, the only thing that has changed is our domain name/ email hosting
package to include sub-domains. To me it appears that it has something to do with the computer being
named server.mydomain.com, but I don't understand the correlation. Do I
need to change this? If so, what should I change it to?

Yeah, that's a problem with wildcards. What's happening is that your resolver is looking in mydomain.com before looking anywhere else. I'd say that in general wildcards are silly. You could remove the search or domain entry from resolve.conf (maybe, I'm not sure if that's allowed).

Again, wildcards are silly, I wouldn't use them.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

____________________
BYU Unix Users Group 
http://uug.byu.edu/ 
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to