Re: DNS, HTTPD & POP

[Ahbaid Gaffoor <ahbaidg guyana net gy>]

Some more info.

Okay, I've removed all of the tabs and used spaces instead, still no working dns,

uname -a yields the following:

Linux linux 2.0.34 #1 Fri May 8 16:05:57 EDT 1998 i586 unknown

What am I doing wrong????

Ahbaid Gaffoor wrote:

> Firstly, thanks,
>
> I'll proceed to answer your questions in the hope that this may narrow down my
> problems...
>
> "Jose M. Sanchez" wrote:
>
> > ----- Original Message -----
> > From: Ahbaid Gaffoor <ahbaidg guyana net gy>
> > To: redhat list <redhat-list redhat com>
> > Sent: Saturday, April 03, 1999 11:45 AM
> > Subject: DNS, HTTPD & POP
> >
> > > Hi All, I'm trying to get a few things working, but I'm beginning to
> > > wonder if they are
> > > inter-related and being affected by the same problem.
> >
> > Yes, they ARE.
>
> I guess this is more good than bad :)
>
> > > 1) I'm attempting to setup DNS on a small LAN with three PC's:
> > >     199.1.1.1 - NT Server box
> > >     199.1.1.2 - Linux
> > >     199.1.1.3 - Win 98 client
> > >
> > >      199.1.1.2 is the linux box, where DNS is hosted, my domain name is
> > >       abdelsoft.com,
> > >
> > >       I followed the example given in the Network Administrator's Guide,
> > > but
> > >       I can't get it to work. After completing the entires for the
> > > named.ca, named.hosts,
> > >       named.rev and named.local files I stop named via ".
> > > ./etc/rc.d/init.d/named stop"
> > >       and restart via. ". ./etc/rc.d/init.d/named start".
> >
> > Which editor did you use to create the files?
>
> I used vi and yes, I'm guilty of tabbing like crazy, nice alignment... I'll fx
> these...
>
> >
> >
> > DNS is very sensitive to the use of TABS...
> >
> > Personally I use "joe" to edit the files...
> >
> > Another option is to use the updated linuxconf program with the DNS modules.
> > This is easier to utilize.
> >
> > >       At this stage I get no error messages, however when I type
> > > "nslookup" to
> > >       test, I get the following error message:
> > >
> > >       "*** Can't find server name for address 199.1.1.2: Server failed"
> > >       "*** Default servers are not available"
> > >
> > This normally means that your NS record is not pointing to the 199.1.1.2
> > address... Check your files...
> > You should have one NS record for each "interface" which will answer DNS
> > queries. This includes 127.0.0.1...
> >
> > PERIODS ARE VERY IMPORTANT. Make sure you have correctly specified
> > records...
> >
> > > 2) When I try to start the http daemon, I get the followin error
> > > message:
> > >      "httpd: cannot determine local host name."
> > >      "Use ServerName to set it manually."
> > >
> >
> > What does "uname -a" produce. It should result int the full name of the syst
> > em. Http uses the hostname part to determine the interface(s) it is to
> > server queries on, unless you specifically specify an interface...
> >
> > >      What does this mean and could it be what's affecting my DNS setup?
> > >
> > > 3) I loaded the IMAP RPM and set up a user, sent him some mail, and
> > > fired up
> > >     Netscape Messenger, I set up a POP account, I could only get mail,
> > > when I try
> > >     to send mail to another user on the Linux box, I get the following
> > > error message:
> > >
> >
> > Do you have a REGISTERED Domain?
>
> No I don't, this is all for a LAN only without a need for a registered domain.
>
> >
> >
> > Did you "make up" the ip's??? (If so this is a BIG no-no.)
>
> Could you please explain this a bit more? I set the IP's statically on each
> machine. I
> do not use DHCP.
>
> >
> >
> > >     First it tries to contact the host machine (199.1.1.2), this takes a
> > > while and then
> > >     I get the usual:
> > >
> >
> > Reverse lookups as well as forward lookups are not working because your DNS
> > is not answering queries, hence the timeouts..
> >
> > >     "There was no response. The server could be down or is not
> > > responding."
> > >     "If you are unable to connect again later, contact the server's
> > > administrator."
> > >
> >
> > The inability to connect to an ip normally indicates that your networking is
> > not working...
> >
>
> > Worry about (in this order)
> >
> > 1) Pinging other machines via IP's - OKAY
>
> >
> > 2) Pinging the internet via IP's - No internet connectivity required.
>
> > 3) Getting nslookup to respond to local host names...
> > 4) Getting ping to work, on your DNS machine to remove machines, via host
> > names...
> >
> > THEN after everything else is working, deal with MAIL and HTTP services...
>
> I'll retry DNS and uname tonight, thanks again for all of your help... If you
> can throw
> anything else my way, please do,
>
> again thanks,
>
> Ahbaid.
>
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
>                 http://www.redhat.com http://archive.redhat.com
>          To unsubscribe: mail redhat-list-request redhat com with
>                        "unsubscribe" as the Subject.