Date: Fri, 25 Apr 2003 18:13:20 +0100 (BST) From: William Palfreman <william@palfreman.com> To: James Lee <jlee@visi.com> Cc: freebsd-questions@freebsd.org Subject: RE:---- Sendmail not working from command line. Message-ID: <20030425175641.I632@ndhn.yna.cnyserzna.pbz> In-Reply-To: <002801c30b37$5201eab0$0100a8c0@xp> References: <002801c30b37$5201eab0$0100a8c0@xp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Apr 2003, James Lee wrote: > This is the output for nslookup localhost.com > > # nslookup localhost.com > Server: ra.myisp.com > Address: 208.98.98.98 > > Non-authoritative answer: > Name: localhost.com > Address: 10.11.12.13 There seems to be some confusion here. Both localhost.com and myisp.com are registered domain names, belonging to other people. They shouldn't really be used as names for your machines. ra.myisp.com itself resolves to 64.38.103.192. > I changed the servers name to ra.myisp.com because it points to my > providers DNS server. I also changed the address underneath server > because it was my ISPs DNS address. I don't know where to fix this > problem. I also don't know why the Non-authoritative's address is > 10.11.12.13 That is because that is the name the owners of localhost.com have chosen to have it resolve to. Localhost != localhost.com Ideally, use a domain you own for your internal DNS, or, as long as the machine is not answering queries coming in from the Internet, make up a domain like internal.intranet or mydomain.moc. I have tried using TLDs as internal-only domains, but they don't work very well. Some programs expect name.ext and don't like www.lan or user@lan, with lan. as the local-only TLD. Bill. -- W. Palfreman. I'm looking for a job. Read my CV at: Tel: 0771 355 0354 www.palfreman.com/william/cv-wfp2.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030425175641.I632>