Debian Stretch, roundcube 1.2.3+dfsg.1-4+deb9u1
Roundcube has created new user_id, with mail_host as FQDN and not
localhost as previously. last_login with user where mail_host is
localhost was 21. March, today login is mail_host FQDN.
Can I fix this in the database so address books etc of
On Fri, Aug 26, 2016 at 7:08 PM, Mark Fletcher wrote:
>
>
> On Sat, Aug 27, 2016 at 8:38 AM John T. Haggerty
> wrote:
>
>> Any thoughts for or against Amazon?
>>
>>
> Please don't top post on this list, it breaks up the flow of the thread
> for people who read the thread after it's finished. The
On Sat, Aug 27, 2016 at 8:38 AM John T. Haggerty wrote:
> Any thoughts for or against Amazon?
>
>
Please don't top post on this list, it breaks up the flow of the thread for
people who read the thread after it's finished. The primary purpose of the
list is to get your questions answered, but the
gt;I have the following issue (seems to be common although my details seem
> >to
> >differ):
> >
> >1. I recently registered a new domain as WWW.whatever.org or whatever.
> >
> >2. Postfix gets installed.
> >
> >3. "Internet site " is enabled
I have been able to create websites, and am able to use the fqdn to show up
my web page I have hosed on the server. I just have to have ddclient update
the ip address with the dns settings. I just have the box NATed behind the
router.
On Fri, Aug 26, 2016 at 4:47 PM, emetib wrote:
> On Thurs
; 3. "Internet site " is enabled fqdn added.
>
> 4. Email cannot be sent out to my Gmail address since it magically "times
> out" when contacting the servers (even though telnetting to mine and Gmail's
> works fine at port 25)
>
> 5. In theory thus shou
;
>2. Postfix gets installed.
>
>3. "Internet site " is enabled fqdn added.
>
>4. Email cannot be sent out to my Gmail address since it magically
>"times
>out" when contacting the servers (even though telnetting to mine and
>Gmail's works fine at p
On Thursday 25 August 2016 19:39:18 John T. Haggerty wrote:
> If it's only Gmail, why van I telnet to their port and get their mail
> server?
>
> Seems counterintuitive.
Were you expecting Gmail to be either intuitive or logical?? :-o
Lisi
John T. Haggerty:
>
> I have the following issue (seems to be common although my details seem to
> differ):
>
> 1. I recently registered a new domain as WWW.whatever.org or whatever.
Please use example.com when you do not want to disclose your real domain
name. The domain whatever.org does not be
ggerty wrote:
>
>> I have the following issue (seems to be common although my details seem
>> to differ):
>>
>> 1. I recently registered a new domain as WWW.whatever.org or whatever.
>>
>> 2. Postfix gets installed.
>>
>> 3. "Internet site &
On Thu, 25 Aug 2016 at 18:16, John T. Haggerty wrote:
> I have the following issue (seems to be common although my details seem to
> differ):
>
> 1. I recently registered a new domain as WWW.whatever.org or whatever.
>
> 2. Postfix gets installed.
>
> 3. "Internet
I have the following issue (seems to be common although my details seem to
differ):
1. I recently registered a new domain as WWW.whatever.org or whatever.
2. Postfix gets installed.
3. "Internet site " is enabled fqdn added.
4. Email cannot be sent out to my Gmail address since it
On Tue 17 May 2016 at 12:32:33 -0500, David Wright wrote:
> On Thu 12 May 2016 at 20:38:41 (+0100), Brian wrote:
>
> > For Exim and minimaldns the question is
> >
> > Does the hostname resolve to a fqdn (something with a dot in it)?
> >
> > 12
onfigure exim4-config either stop saying
> > > > "hostname --fqdn did not return a fully qualified name, dc_minimaldns
> > > > will not
> > > > work. Please fix your /etc/hosts setup." or suggest a reasonable fix?
> > > > Or IOW, why has bu
On Thu 12 May 2016 at 10:08:49 -0500, David Wright wrote:
> On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> > On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > >
> > > BTW when will dpkg-reconfigure exim4-config either stop saying
> > &g
a warning about the terminating newline while their
script is broken. (crontab suffers from the same problem. A correct
way to write such a script is demonstrated by /etc/init.d/kmod's
reading of /etc/modules. I always add a blank comment line to my
configuration files anyway.)
> > BTW
he HELO.
>
> I doubt this has anything to do with BT. MTA's will generally provide
> the FQDN as the HELO name (as described in the corresponding RFC), and
> if the FQDN has been chosen to end with .local then you'll get that in
> the HELO.
My point was that the default is
ange Server refuse mail from a BT server
for this connection, the "BT server" is actually the client.
> because the latter identified itself with .local as tld in the HELO.
> BT knows nothing about email.
I doubt this has anything to do with BT. MTA's will generally provide
t had no dots it appended
$mydomain forming names such as foo.localdomain when the configured
hostname was a short name (the general Debian recommendation) rather
than a FQDN. That would match the names used in /etc/hosts and
everything would work. For a system defaulting to localhost:
root
a DNS server, or
provides some service across the Internet, that 'domain' and 'FQDN'
become meaningful. Even in the latter case, 'domain' applies only to
the external interface and to any network machines carrying public IP
addresses, and means nothing to machines behi
Quoting David Wright (deb...@lionunicorn.co.uk):
>
> I'm one of the many who use .home
> https://tools.ietf.org/html/draft-cheshire-homenet-dot-home-00
> and this paper points out that there's an awful lot of leakage onto
> the Internet.
>
> I think I/we ought to be using .local
> http://tools.ie
already the fine Debian Reference
> > maintained by Osamu Aoki. All it takes is time and that seems in less
> > supply every day.
I agree. I think I may have stumbled on the same or a similar
discussion regarding 127.0.1.1 foo and I tried making changes
accordingly. The result of one
On Fri 03 Apr 2015 at 14:29:49 -0600, Bob Proulx wrote:
> Brian wrote:
> > Bob Proulx wrote:
> > > The debian-installer will set things up right with an entry such as
> > > this one.
> > >
> > > 127.0.1.1 foo.example.com foo
> >
> > If 'Domain name' is blank you get '127.0.1.1 foo'.
>
> Ah, y
Brian wrote:
> Bob Proulx wrote:
> > The debian-installer will set things up right with an entry such as
> > this one.
> >
> > 127.0.1.1 foo.example.com foo
>
> If 'Domain name' is blank you get '127.0.1.1 foo'.
Ah, yes, I had left that out. We had discussed that point in a
previous email. H
irst, goes
> > > to /etc/hosts second, and if it encounters FQDN hostname - it all ends
> > > here.
> > > If /etc/hosts contain only bare hostname - it'd return a bare hostname.
>
> But /etc/hosts shouldn't have a bare hostname, right? It should
>
Alex Mestiashvili wrote:
> >> and as far as I see it simply asks the DNS about the hostname using
> >> getaddrinfo.
> >
> > But, with stock nsswitch.conf, it issues uname(2) syscall first, goes
> > to /etc/hosts second, and if it encounters FQDN hostname - it
>> and as far as I see it simply asks the DNS about the hostname using
>> getaddrinfo.
>
> But, with stock nsswitch.conf, it issues uname(2) syscall first, goes
> to /etc/hosts second, and if it encounters FQDN hostname - it all ends
> here.
> If /etc/hosts contai
ch.conf, it issues uname(2) syscall first, goes
to /etc/hosts second, and if it encounters FQDN hostname - it all ends
here.
If /etc/hosts contain only bare hostname - it'd return a bare hostname.
Only if /etc/hosts does not contain a hostname - a DNS search will be
performed (or other resolvin
On 04/02/2015 02:10 PM, Mihamina Rakotomandimby wrote:
Hi al,
WHen issuing 'hostname --fqdn', I'm supposed to get the FQDN.
Anyway when trying some different combinations, involving
/etc/hostname, /etc/domainname, /etc/hosts, /etc/resolv.conf, I cannot
figure out where the FQ
Hi al,
WHen issuing 'hostname --fqdn', I'm supposed to get the FQDN.
Anyway when trying some different combinations, involving /etc/hostname,
/etc/domainname, /etc/hosts, /etc/resolv.conf, I cannot figure out where
the FQDN is looked up AND with what precedence.
Would you kno
Thanks All,
I fully accept that exim is as it is, and being an
(instrumentation-)developer
myself it's easy to see how we got here. As stated in my very first post,
I did make it all work by using "proper" ;-) entries in /etc/hosts,
hostname and mailname. This being my first email server instal
On 5/19/2013 3:45 AM, Klaus Doering wrote:
> Stan,
>
> Thank you for taking the time to explain your perspective. Maybe it is
> the tone of your teachings that tickle me, maybe it's just that I'm no
> big fan of sweeping statements a la "Don't do it, ever". As I described
Many folks with long ex
y the DHCP server. In "dnsmasq" this
> would be the "domain=" option. And it is this option that is not
> acknowledged by exim.
>
Whether a server sits on the WAN or an internal LAN (with no
visibility on the WAN), the principles of configuration are the
same. Instead
On Du, 19 mai 13, 13:51:01, Klaus Doering wrote:
>
> This email server is not directly connected to the 'net, it sits behind
> a router. Thus, there is one external IP for which I've registered an "A"
> record and an "MX" record on a public DNS server, and then there is an
> internal IP server on
On 19/05/13 12:48, Arun Khan wrote:
On Sun, May 19, 2013 at 2:15 PM, Klaus Doering
wrote:
I agree that in a different setting, where there are many users,
hundreds of emails per minute and other mission-critical stuff is going
on, one needs to design the infrastructure a lot more carefully.
On Sun, May 19, 2013 at 2:15 PM, Klaus Doering
wrote:
>
> I agree that in a different setting, where there are many users,
> hundreds of emails per minute and other mission-critical stuff is going
> on, one needs to design the infrastructure a lot more carefully.
>
As a thumb rule, any system pro
Stan,
Thank you for taking the time to explain your perspective. Maybe it is
the tone of your teachings that tickle me, maybe it's just that I'm no
big fan of sweeping statements a la "Don't do it, ever". As I described
in my initial post, this thread concerns a small domestic setting. There
is
On 5/16/2013 2:17 PM, Klaus Doering wrote:
> Stan, Thank you for the teaching. Indeed, there are many books I should
> have read already, alas, there are a great many subjects about which
> important books are written. So, I go along and learn when things don't
> work as expected. Like now.
>
> Th
Joe,
Yes, I've set the "A" and the "MX" record to the same FQDN, and that is
also the HELO string. (at least now that I adjusted the entry in the
hosts file.)
Thanks,
Klaus
On 16/05/13 19:06, Joe wrote:
Apart from any other issue, please note that the HELO string pro
Stan, Thank you for the teaching. Indeed, there are many books I should
have read already, alas, there are a great many subjects about which
important books are written. So, I go along and learn when things don't
work as expected. Like now.
The story about using DHCP to assign fixed addresses doe
On Thu, 16 May 2013 09:02:57 +0100
Klaus Doering wrote:
>
> The RaspPi (running Raspbian, a version of Wheezy for the ARMHF
> architecture) also acts as a mail server, talking
> SMTP to the wider world using exim4. After I got an error message
> from some strict server telling me
>
> 504 5.
On 5/16/2013 3:02 AM, Klaus Doering wrote:
...
> Sorry long post. Can anybody shine light on this, and maybe even know
> how to make use of the DHCP provided
> domain name in exim?
First, using a DHCP server, in a consumer broadband router or otherwise,
to assign -sticky static- addresses and hos
cient to set the domain in /etc/mailname, instead
/etc/hosts must contain the FQDN.
Sorry long post. Can anybody shine light on this, and maybe even know
how to make use of the DHCP provided
domain name in exim?
Thanks
Klaus
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On Sun, 29 Jul 2012 15:50:53 -0400, Tom H wrote:
> On Fri, Jul 27, 2012 at 12:35 PM, Camaleón wrote:
(...)
>> Yes, I can ping *but* I have the above machine listed in my
>> "/etc/hosts" file.
>>
>> sm01@stt008:~$ cat /etc/hosts
>> 127.0.0.1 localhost
>> 192.168.0.8 stt008.linux.site
On Fri, Jul 27, 2012 at 2:33 PM, Kent West wrote:
>
> westk@westek:~$ cat /etc/nsswitch.conf
> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
>
> Changing the order of the hosts: line to:
> hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4
> as you suggested above, s
nf|grep hosts
> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
>
> And let's see if I can ping a local machine using its FQDN:
>
> sm01@stt008:~$ ping -c 3 stt008.linux.site
> PING stt008.linux.site (192.168.0.8) 56(84) bytes of data.
> 64 bytes from stt008.li
On Sun, Jul 29, 2012 at 3:18 PM, Tom H wrote:
>
> Although you're using "acu.local" as a domain, I suspect that it has
> the same problem as ".local" and clashes with avahi. Do you have any
> "mdns" entries on the "hosts" line of "/etc/resolv.conf"?
"/etc/nsswitch.conf" not "/etc/resolv.conf", so
em (so I put the /etc/default/avahi-daemon file back to the way it
> was).
>
> I have a MacBook running an up-to-date OS/X, and it can ping both the
> hostname and the FQDN (and it's resolv.conf file looks pretty much the same
> as the above), so it seems to be a problem in
On Fri, 27 Jul 2012 13:33:07 -0500, Kent West wrote:
> On 07/27/2012 11:35 AM, Camaleón wrote:
(...)
>> I remember something related to the "/etc/nsswitch.conf" file, the
>> order of the queried facilities and also the avahi issue with ".local"
>> domains...
(...)
>> Just for testing purposes yo
On Vi, 27 iul 12, 13:45:36, Kent West wrote:
>
> As mentioned in another post, changing the line in /etc/nsswitch.conf from:
>
> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
>
> to:
>
> hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4
>
> seems to have solved
On Fri, 27 Jul 2012 13:45:36 -0500
Kent West wrote:
>
> The domain is a Windows Active Directory domain (if that's a sensible
> description), and it used to be named ACU, but then we moved to a new
> Active Directory setup, starting from scratch because the ACU AD
> Domain had too many problem
On 07/27/2012 12:11 PM, Andrei POPESCU wrote:
On Vi, 27 iul 12, 09:45:02, Kent West wrote:
Why can I ping the hostname, but not the fully-qualified domain name
of a box?
westk@westek:~$ ping k1000
PING k1000.acu.local (150.252.149.1) 56(84) bytes of data.
64 bytes from 150.252.149.1: icmp_req=
On 27.07.2012 21:33, Kent West wrote:
> Changing the order of the hosts: line to:
>
> hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4
>
> as you suggested above, seems to have solved the problem:
>
> ...
>
> Will this cause me any problems?
I put it into this:
hosts:
;/etc/nsswitch.conf" file, the
order of the queried facilities and also the avahi issue with ".local"
domains...
sm01@stt008:~$ cat /etc/nsswitch.conf|grep hosts
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
And let's see if I can ping a local machine using its FQDN:
On Vi, 27 iul 12, 09:45:02, Kent West wrote:
> Why can I ping the hostname, but not the fully-qualified domain name
> of a box?
>
>
> westk@westek:~$ ping k1000
> PING k1000.acu.local (150.252.149.1) 56(84) bytes of data.
> 64 bytes from 150.252.149.1: icmp_req=1 ttl=62 time=0.128 ms
> ^C64 bytes
he "/etc/nsswitch.conf" file, the
order of the queried facilities and also the avahi issue with ".local"
domains...
sm01@stt008:~$ cat /etc/nsswitch.conf|grep hosts
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
And let's see if I can ping a local machine u
>>> westk@westek:~$ nslookup k1000.acu.local
>>> Server: 150.252.134.8
>>> Address:150.252.134.8#53
>>>
>>> Name: k1000.acu.local
>>> Address: 150.252.149.1
>>>
>>>
>>> I googled for this problem a
-date OS/X, and it can ping both the
hostname and the FQDN (and it's resolv.conf file looks pretty much
the same
as the above), so it seems to be a problem in this Debian box (westek).
Odd. What does your routing table look like ("ip route" or "route")?
I don't see
/etc/default/avahi-daemon file (after which I did a "sudo
/etc/init.d/avahi-daemon restart" command), but that didn't solve the
problem (so I put the /etc/default/avahi-daemon file back to the way it
was).
I have a MacBook running an up-to-date OS/X, and it can ping both the
hostna
gt;
>>
>> I googled for this problem and found instructions to change 1 to 0 in the
>> /etc/default/avahi-daemon file (after which I did a "sudo
>> /etc/init.d/avahi-daemon restart" command), but that didn't solve the
>> problem (so I put the /etc/default
t solve the
> problem (so I put the /etc/default/avahi-daemon file back to the way it
> was).
>
> I have a MacBook running an up-to-date OS/X, and it can ping both the
> hostname and the FQDN (and it's resolv.conf file looks pretty much the same
> as the above), so it seems to
start" command), but that didn't solve the
problem (so I put the /etc/default/avahi-daemon file back to the way it
was).
I have a MacBook running an up-to-date OS/X, and it can ping both the
hostname and the FQDN (and it's resolv.conf file looks pretty much the
same as the above),
So both addresses are unambiguous. For what reason now would I need a
FQDN? Why wouldn't a domain name suffice?
Typically, I see it that a domain refers to an entity, whereas a FQDN refers to
a host or service within that entity. For your purposes the following sdhould
be suffi
Chris Davies a écrit :
> Stefan Schmidt wrote:
>> in my understanding the /etc/hosts file should contain an entry with the
>> FQDN of the host.
>
>> 123.123.123.123 hostname.domain.tld hostname
>
> Yes, that's right.
>
>
>> I would for simplicit
On Sun, Jan 4, 2009 at 9:11 PM, Stefan Schmidt wrote:
> Hello,
>
> in my understanding the /etc/hosts file should contain an entry with the
> FQDN of the host.
>
> 123.123.123.123 hostname.domain.tld hostname
>
> I would for simplicity prefer to use a domai
Stefan Schmidt wrote:
> in my understanding the /etc/hosts file should contain an entry with the
> FQDN of the host.
> 123.123.123.123 hostname.domain.tld hostname
Yes, that's right.
> I would for simplicity prefer to use a domain name instead of a FQDN.
> 123.123.123.123
Thanks for your feedback!
So both addresses are unambiguous. For what reason now would I need a
FQDN? Why wouldn't a domain name suffice?
What happens when you want/need to add another machine ?
I use the domain solely for private purposes and I will probably never
need more than t
On Sun, 4 Jan 2009, Stefan Schmidt wrote:
Hello,
Howdy
in my understanding the /etc/hosts file should contain an entry with the FQDN
of the host.
123.123.123.123 hostname.domain.tld hostname
Yes, that is the proper format and order
I would for simplicity prefer to use a domain name
Hello,
in my understanding the /etc/hosts file should contain an entry with the
FQDN of the host.
123.123.123.123 hostname.domain.tld hostname
I would for simplicity prefer to use a domain name instead of a FQDN.
123.123.123.123 domain.tld hostname
In my DNS-configuration I can define an
Hello,
in my understanding the /etc/hosts file should contain an entry with the
FQDN of the host.
123.123.123.123 hostname.domain.tld hostname
I would for simplicity prefer to use a domain name instead of a FQDN.
123.123.123.123 domain.tld hostname
In my DNS-configuration I can define an IP
Umarzuki Mochlis <[EMAIL PROTECTED]>:
>
> Why that must be, I mean when changing the hostname with hostname
> command, we also sometimes need to do the same with /etc/hosts else
> something weird would happen. Does the command hostname writes
> somewhere else other than /etc/hosts?
man hostna
) A running instance of Debian only has one of these at a
time. The kernel's hostname string is a very local identifier.
The FQDN is a more complicated beast, dependent on your NSS settings and the
resources they point to, and a single running Debian instance might have many
of them. Th
On Thu,20.Nov.08, 20:29:22, Umarzuki Mochlis wrote:
> Why that must be, I mean when changing the hostname with hostname command,
> we also sometimes need to do the same with /etc/hosts else something weird
> would happen. Does the command hostname writes somewhere else other than
> /etc/hosts?
Acc
Why that must be, I mean when changing the hostname with hostname command,
we also sometimes need to do the same with /etc/hosts else something weird
would happen. Does the command hostname writes somewhere else other than
/etc/hosts?
--
Regards,
Umarzuki Mochlis
http://gameornot.net
# /etc/mailname
lvps123-123-123-123.dedicated.hosteurope.de
First of all I think the /etc/hostname shouldn't contain the FQDN, but instead
the hostname, in this case lvps123-123-123-123. I would like to replace all
these values with my own domain name (mydomain.com), but I'm not sure i
On Fri, Nov 02, 2007 at 10:50:21AM -0600, John Schmidt wrote:
> Is there a way to set up my chroot environment (or perhaps it is an
> apache issue) that allows me the freedom to move the machine from one
I'm not even sure I really understand the question. Apache doesn't care
all that much about y
Hi,
I am testing out the installation of some software that involves specifying
hostname information for the install. I have set up a minimal chroot
environment and downloaded all of the debian packages and the other software
that is needed to build it.
I am using this on my laptop that is
would then possibly have more than one FQDN.
>
> "The host name is usually set once at system startup in
> /etc/rc.d/rc.inet1 or /etc/init.d/boot (normally by reading the
> contents of a file which contains the host name, e.g. /etc/hostname)"
>
> Those first 2 files
On Fri, 31 Aug 2007, Jonathan Wilson wrote:
Can anyone who /knows/ tell me what the proper officially correct ways of
setting the hostname and the FQDN are, please?
Thanks,
JW
--
in /etc/hostname :
myhostname
in /etc/hosts:
10.0.0.120 myhostname.mydomain.com myhostname
set
I have been trying to find out the exact and proper way to set the host and
domain name on Debian and it's clear as mud. Searching the internet gives all
sorts of conflicting answers.
First, I thought the way to do it was to put the FQDN in /etc/hostname. Then I
ended up
On Thursday 22 March 2007 17:14, I wrote:
> Hello list,
>
> I have a server running bind that is master for 'domain.local'.
> When I try to use a FQDN from within an application on my debian
> etch 'desktop machine' (e.g. in a browser: http://host.domain.loca
ECTED]> wrote:
Hello list,
I have a server running bind that is master for 'domain.local'.
When I try to use a FQDN from within an application on my debian
etch 'desktop machine' (e.g. in a browser: http://host.domain.local/) it
does not resolve / ask the DNS server for the
On Thu, 22 Mar 2007, Richard Harb (debian) wrote:
Hello list,
I have a server running bind that is master for 'domain.local'.
When I try to use a FQDN from within an application on my debian
etch 'desktop machine' (e.g. in a browser: http://host.domain.local/) it
does n
Hello list,
I have a server running bind that is master for 'domain.local'.
When I try to use a FQDN from within an application on my debian
etch 'desktop machine' (e.g. in a browser: http://host.domain.local/) it
does not resolve / ask the DNS server for the address.
wi
Andrew Critchlow wrote:
> Hi, I have not yet adjusted /etc/hosts ? Do I need to do this? What is
> its purpose and why cant it bypass this to use resolv.conf?
You need to edit the /etc/hosts file to set the name and domain
for 127.0.0.1. You can not get these from a DNS server and this
is the inf
Andrew Critchlow wrote:
Hi, I have not yet adjusted /etc/hosts ? Do I need to do this? What is
its purpose and why cant it bypass this to use resolv.conf?
I have tried restarting etc
many thanks
Andrew,
I've not followed the discussion up to this point. I apologize if this
does
Hi, I have not yet adjusted /etc/hosts ? Do I need to do this? What is its purpose and why cant it bypass this to use resolv.conf?
I have tried restarting etc
many thanks
Andrew Critchlow wrote:
> I am trying to set the FQDN domain of my debian box, I have read that
> to set the dns name in resolv.conf use:
...
> It still shows up as: localdomain
Have you also adjusted /etc/hostname and/or /etc/hosts?
Have you tried restarting networking and/or rebooti
Can anyone help, I am in desperate need of help!
I am trying to set the FQDN domain of my debian box, I have read that to set the dns name in resolv.conf use:
domain domain.com
I have tried this but when I issue
#hostname --fqdn
It shows up as: localhost.localdomain
or
#dnsdomainname
It still
To get hostname to work for myhost.example.com do this:
* Make sure /etc/hostname has myhost.
* Put this line in /etc/hosts:
1.2.3.4 myhost.example.com myhost
David
On Tuesday 24 January 2006 02:01 pm, José Pablo Ezequiel Fernández wrote:
> Hello.
> How do I change the fqdn of a co
Gene Heskett wrote:
> On Tuesday 24 January 2006 18:47, Ken Bloom wrote:
>
>>Steve Witt wrote:
>>
>>>On Tue, 24 Jan 2006, [utf-8] José Pablo Ezequiel Fernández wrote:
>>>
>>>>Hello.
>>>>How do I change the fqdn of a c
On Tuesday 24 January 2006 18:47, Ken Bloom wrote:
>Steve Witt wrote:
>> On Tue, 24 Jan 2006, [utf-8] José Pablo Ezequiel Fernández wrote:
>>> Hello.
>>> How do I change the fqdn of a computer ?
>>> No matter what I do, hostname -f keeps telling
>>>
Steve Witt wrote:
> On Tue, 24 Jan 2006, [utf-8] José Pablo Ezequiel Fernández wrote:
>
>> Hello.
>> How do I change the fqdn of a computer ?
>> No matter what I do, hostname -f keeps telling
>> "localhost.localdomain", other
>> computers with
On Tue, 24 Jan 2006, [utf-8] José Pablo Ezequiel Fernández wrote:
Hello.
How do I change the fqdn of a computer ?
No matter what I do, hostname -f keeps telling "localhost.localdomain", other
computers with the same configuration give the right hostname.
Thank you.
--
The hostn
Hello.
How do I change the fqdn of a computer ?
No matter what I do, hostname -f keeps telling "localhost.localdomain", other
computers with the same configuration give the right hostname.
Thank you.
--
José Pablo Ezequiel Fernández
pgpib1CDLZJ6J.pgp
Description: PGP signature
[EMAIL PROTECTED] wrote:
Hi all,
After I finished configuring apache2, I run /etc/init.d/apache2 restart and I
got the following:
"Forcing reload of webserver: Apache2 apache2: could not determine the
server's fully qualified domain name, using 127.0.0.1 for ServerName"
I have my webserver's ip
Hi all,
After I finished configuring apache2, I run /etc/init.d/apache2 restart and I
got the following:
"Forcing reload of webserver: Apache2 apache2: could not determine the
server's fully qualified domain name, using 127.0.0.1 for ServerName"
I have my webserver's ip address and domain name in
What configuration files need to be changed when performing a change
of hostname and fqdn in a basically setup debian box?
Problem: I am planning to get a debian dedicated hosting service, they
make a basic woody installation, but probably they will call it debian
following the default name.
For
I have configured postfix with smarthost. When I send an email, it goes to
nowhere. Using the mail command I checked that postfix gives a warning
that the domain name is not set. If I set it, I get the following warning:
postdrop: warning: unable to look up public/pickup: No such file or
directory
For the moment, /etc/mailname is set to "ay" on my machine. But the
message-id generated by the "bug" utility doesn't have a FQDN. I tried
to set it to "ay.vinc17.org", but address rewriting doesn't work any
longer (vinc17.org is a domain I own, but ay.vinc
1 - 100 of 152 matches
Mail list logo
