Stuart Clark wrote:
> Hi
>
> Why can't I get the fqdn on my box?
>
> The man hostname says
>
> The complete FQDN of the system is returned with hostname --fqdn.
>
> But when I do it I just get the hostname
>
>
> [EMAIL PROTECTED] root]# hostname
Hi
Why can’t I get the fqdn
on my box?
The man hostname says
The complete FQDN of the system is returned with
hostname --fqdn.
But when I do it I just get the hostname
[EMAIL PROTECTED] root]# hostname
--fqdn
server1
[EMAIL PROTECTED] root]# hostname
server1
> The problem was that the only entry I had in /etc/hosts was '127.0.0.1
> localhost'. I added the entry for newt.emeraldbiostructures.com, and
> it's working now. Thanks,
>
If this is something you want publicly available at the FQDN you mentioned
you will have
he browser to
> > | http://newt.emeraldbiostructures.com, it says that Netscape is unable to
> > | locate the server. If I point the browser to localhost, 127.0.0.1, or
> > | its local class C IP address, I get the familiar Apache start-up page.
> > | Why is httpd not recognizing the FQDN?
; Starting httpd: [Mon Feb 4 17:37:20 2002] [alert] httpd: Could not
> > determine the server's fully qualified domain name, using 127.0.0.1 for
> > ServerName
>
> I think this is the error you get when
>
> /etc/httpd/conf/ht
hy is httpd not recognizing the FQDN? I have the correct name in
> | /etc/HOSTNAME. Thanks,
>
> It's not in the DNS. Why not?
Either make sure the DNS entry is correct or that the ip and hostname are
listed in /etc/hosts so that it can
er's fully qualified domain name, using 127.0.0.1 for
> ServerName
I think this is the error you get when
/etc/httpd/conf/httpd.conf
doesn't contain the server name.
Look in that file for the line that starts out "ServerName" and put
the FQDN for your machine after it.
HT
127.0.0.1 for
| ServerName
|
| And then when I point the browser to
| http://newt.emeraldbiostructures.com, it says that Netscape is unable to
| locate the server. If I point the browser to localhost, 127.0.0.1, or
| its local class C IP address, I get the familiar Apache start-up page.
| Why i
raldbiostructures.com, it says that Netscape is unable to
locate the server. If I point the browser to localhost, 127.0.0.1, or
its local class C IP address, I get the familiar Apache start-up page.
Why is httpd not recognizing the FQDN? I have the correct name i
>1. Get Bind and install it.
it ships with redhat
>2. Edit the bind so that I have a local private domain as well as my public
>one (split DNS?)
if you want. i don't. i just define my internal domain as
, thus my machines are ,
and thus still resolves to the address defined by my
isp,
On Fri, 16 Nov 2001 [EMAIL PROTECTED] wrote:
> David Talkington wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > >> I'm just not sure what is the best way to name systems on the private side
> > >> of our LAN. We tried using just single names but some programs seem to have
David Talkington wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> >> I'm just not sure what is the best way to name systems on the private side
> >> of our LAN. We tried using just single names but some programs seem to have
> >> problems with it. Like NIS and SendMail. What is the
Patrick Nelson wrote:
-
I'm just not sure what is the best way to name systems on the private side
of our LAN. We tried using just single names but some programs seem to have
problems with it. Like NIS and SendMail. What is the best way to name
systems on a LAN behind a fire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> I'm just not sure what is the best way to name systems on the private side
>> of our LAN. We tried using just single names but some programs seem to have
>> problems with it. Like NIS and SendMail. What is the best way to name
>> systems on a L
On Wed, 14 Nov 2001, Patrick Nelson wrote:
> I'm just not sure what is the best way to name systems on the private side
> of our LAN. We tried using just single names but some programs seem to have
> problems with it. Like NIS and SendMail. What is the best way to name
> systems on a LAN behin
st way to name
> systems on a LAN behind a firewall that don't have internet names?
Give them internet names! The extension can be anything you want. For
example, foo.nelson is a valid FQDN as long your local nameserver is
authoritative for the .nelson domain.
Personally, I registered a na
Set up a zone, for which your main server is primary. You can do the same
for the reverse zone for the private network. Then, as long as you set
the main server as the primary name server in the client machines'
resolv.conf files, you should be ok.
On Wed, 14 Nov 2001, Patrick Nelson wrote:
s-hme0.home.
janus IN CNAME janus-eth0.home.
janus-eth0 IN A 192.168.1.2
IN MX 50 skaros-hme0.home.
I.e. the "real" FQDN has the interface name in it. Handy when
looking at reports.
--
Cameron Simpson, DoD#743[EMAIL PROTEC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 14 Nov 2001, Patrick Nelson wrote:
>I'm just not sure what is the best way to name systems on the private
>side of our LAN. We tried using just single names but some programs
>seem to have problems with it. Like NIS and SendMail. What is th
Hi Patrick,
> I'm just not sure what is the best way to name systems on the private side
> of our LAN. We tried using just single names but some programs seem to have
> problems with it. Like NIS and SendMail. What is the best way to name
> systems on a LAN behind a firewall that don't have in
I'm just not sure what is the best way to name systems on the private side
of our LAN. We tried using just single names but some programs seem to have
problems with it. Like NIS and SendMail. What is the best way to name
systems on a LAN behind a firewall that don't have internet names?
21 matches
Mail list logo
