On Thu, Jul 18, 2019 at 11:04:52PM -0400, Winston Sorfleet wrote:
> On 2019-07-18 10:49 p.m., Nathan Stratton Treadway wrote:
> > On Thu, Jul 18, 2019 at 21:51:56 -0400, Winston Sorfleet wrote:
> >> |backup@flamen:/etc/amanda/vtl$ amcheck -c vtl --client-verbose pomerium||
> >> ||Amanda Backup
On 2019-07-18 10:49 p.m., Nathan Stratton Treadway wrote:
> On Thu, Jul 18, 2019 at 21:51:56 -0400, Winston Sorfleet wrote:
>> |backup@flamen:/etc/amanda/vtl$ amcheck -c vtl --client-verbose pomerium||
>> ||Amanda Backup Client Hosts Check||
>> ||||
>> ||ERROR:
On Thu, Jul 18, 2019 at 21:51:56 -0400, Winston Sorfleet wrote:
> |backup@flamen:/etc/amanda/vtl$ amcheck -c vtl --client-verbose pomerium||
> ||Amanda Backup Client Hosts Check||
> ||||
> ||ERROR: pomerium.romanus.ca: selfcheck request failed: tcpm_recv_token:
>
Greetings all
|backup@flamen:/etc/amanda/vtl$ amcheck -c vtl --client-verbose pomerium||
||Amanda Backup Client Hosts Check||
||||
||ERROR: pomerium.romanus.ca: selfcheck request failed: tcpm_recv_token:
invalid size||
||Client check: 1 host checked in 5.814
On Mon, Mar 27, 2017 at 09:53:21 -0400, Jean-Louis Martineau wrote:
> Nothing can be done.
>
> The backup are done with the 'localhost' hostname
> You must use it when restoring.
In particular, the dumps written to tape include the hostname as part of
the header block in the dump-fil
Nothing can be done.
The backup are done with the 'localhost' hostname
You must use it when restoring.
Jean-Louis
On 23/03/17 09:50 AM, hy...@lactose.homelinux.net wrote:
> Greetings.
>
> For the past couple of years, I've been using amanda to back up the
> server amanda was runni
Home /home comp-user-tar
>vost.jgcomp.com Home /home comp-user-tar
>
> My server and all the clients are in the same domain
> and ip-addr -> hostname queries to my local DNS returns
> the short form rather than the FQDN.
>
> Are there any known
are in the same domain
and ip-addr -> hostname queries to my local DNS returns
the short form rather than the FQDN.
Are there any known places/situations where using the
short hostnames will definitely cause problems?
The concern arose as I'm still trying to get amdump_client
working. At one poin
A record for a single hostname, that provides
(or used to) a round-robin lookup.
CNAME and PTR are on opposite sides of the fence.
On Mon, Jan 06, 2014 at 03:22:29PM -0700, Charles Curley wrote:
On Mon, 6 Jan 2014 21:52:53 +0100
Heiko Schlittermann h...@schlittermann.de wrote
Hello,
the backup server refuses the connection:
Mon Jan 6 21:39:50 2014: thd-0x14aec00: \
amandad: pu.schlittermann.de doesn't resolve to itself, it resolves to
ssl.schlittermann.de
The names are not obfuscated, you may try to dig(8) around as well.
The connection comes from
On Mon, 6 Jan 2014 21:52:53 +0100
Heiko Schlittermann h...@schlittermann.de wrote:
ssl.schlittermann.de.3600IN A 212.80.235.130
pu.schlittermann.de. 3600IN A 212.80.235.130
I think, nothing is wrong with having two PTR records. Even I know
that ancient
hostname]
...
It's not really an issue with resolving the hostname. DNS is setup correctly
and I can ssh from the client to the server and from the server to the backup.
While running amrecover I see no queries being sent to the servers listed in
resolv.conf. Even inserting the host into /etc
On Sat, Mar 29, 2008 at 4:18 PM, Oscar Ricardo Silva
[EMAIL PROTECTED] wrote:
Son of a (kicking self) ... I think I figured out the problem. It was a
combination of two things. I ran tcpdump on the client to see what it was
doing
and saw a bunch of queries. Considering we're
... that's when I
ran into this problem. When I run amrecover I get this error:
/usr/local/amanda25/sbin/amrecover -C dailytoo
AMRECOVER Version 2.5.2p1. Contacting server on amanda.tn.utexas.edu ...
[request failed: amanda.tn.utexas.edu: ssh could not resolve hostname]
and here's the content
On Fri, Mar 28, 2008 at 5:57 PM, Oscar Ricardo Silva
[EMAIL PROTECTED] wrote:
/usr/local/amanda25/sbin/amrecover -C dailytoo
AMRECOVER Version 2.5.2p1. Contacting server on amanda.tn.utexas.edu ...
[request failed: amanda.tn.utexas.edu: ssh could not resolve hostname]
...
It's not really
Not sure why this didn't make the list last week?
A gaff on my part?
-pf
-- Forwarded message --
From: Peter Farrell [EMAIL PROTECTED]
Date: 23-Mar-2006 12:20
Subject: amrcover and nslookups that resolve hostname to more than one
IP_ADDR (multi-homed servers)
To: amanda-users
to both of it's IP_ADDR to it's true hostname. But since
the traffic isn't going through the interface that has precedence via
my DNS the recover fails.
I read in the documents that:
=
If the tape server has multiple network connections, an amanda.conf
interface
! Amcheck
says,
ERROR: stupid.server.edu [addr 555.555.555.555: hostname lookup failed]
Obviously I replace the true name IP with fake names.
The IP is NOT CORRECT! Even in the /etc/hosts file, it has the correct
IP for this stupid.server.
Any ideas on why amanda would think
the clients report OK, except one! Stupid old AIX! Amcheck
says,
ERROR: stupid.server.edu [addr 555.555.555.555: hostname lookup failed]
Obviously I replace the true name IP with fake names.
The IP is NOT CORRECT! Even in the /etc/hosts file, it has the correct
IP for this stupid.server.
Any ideas
one! Stupid old AIX! Amcheck
says,
ERROR: stupid.server.edu [addr 555.555.555.555: hostname lookup failed]
Obviously I replace the true name IP with fake names.
The IP is NOT CORRECT! Even in the /etc/hosts file, it has the correct
IP for this stupid.server.
Any ideas on why amanda would think
Hi,
I have a RHE4 machine with the standard AMANDA config, and then I copied
over my amanda.conf file, disklist, and chg-conf file from the old
AMANDA server.
Now, all the clients report OK, except one! Stupid old AIX! Amcheck
says,
ERROR: stupid.server.edu [addr 555.555.555.555: hostname
PM
To: Matt Hyclak
Cc: amanda-users@amanda.org
Subject: Re: New AMANDA server cannot one reach old client. (hostname
lookup failed with the wrong IP)
On Mon, 13 Mar 2006 at 4:03pm, Matt Hyclak wrote
On Mon, Mar 13, 2006 at 03:46:13PM -0500, Byarlay, Wayne A.
enlightened us:
I have a RHE4
On Mon, Mar 13, 2006 at 04:44:51PM -0500, Byarlay, Wayne A. enlightened us:
Thanks all for your help, Did I mention that I'm somewhat newbie-ish
with *nix? Blush. Thanks, here are my responses...
1. I did not know about this host command. It yields the INCORRECT
information!
server cannot one reach old client. (hostname
lookup failed with the wrong IP)
On Mon, 13 Mar 2006 at 4:03pm, Matt Hyclak wrote
On Mon, Mar 13, 2006 at 03:46:13PM -0500, Byarlay, Wayne A.
enlightened us:
I have a RHE4 machine with the standard AMANDA config, and then I
copied over my amanda.conf
A.
Sent: Monday, March 13, 2006 4:45 PM
Cc: amanda-users@amanda.org
Subject: RE: New AMANDA server cannot one reach old client. (hostname
lookup failed with the wrong IP)
Thanks all for your help, Did I mention that I'm somewhat newbie-ish
with *nix? Blush. Thanks, here are my responses...
1. I did
reach old client. (hostname
lookup failed with the wrong IP)
oh, and the incorrect IP is actually the host address; so it's thinking
that its own IP is that of the stupid.aix.client.
So I guess actually the stupid server is the amanda host... :(
-Original Message-
From: [EMAIL PROTECTED
KEVIN ZEMBOWER wrote:
Thank you, Olivier, Scott and Matt, for all your suggestions. Your
helpfulness is part of what makes Amanda a truly great solution.
AMANDA-users take care of each other ;-)
The problem, as you all suggested, seems to be the lack of a reverse
DNS look-up capability
I'm betting this might be a fairly common problem that some of you
all have solved before. What's your preferred solution? I can think
of a couple of alternatives, such as:
I have not seen any answer but I'd try to use IP address in disklist
file...
Olivier
static reverse DSN look-ups? This
would be an easy solution, but I don't know of anything that does it.
Thanks you all, again, for all your suggestions and advice.
-Kevin
Olivier Nicole [EMAIL PROTECTED] 10/19/05 09:36PM
Hi,
ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup
$ amcheck -c DBackup
Amanda Backup Client Hosts Check
ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed]
Client check: 2 hosts checked in 0.702 seconds, 1 problem found
(brought to you by Amanda 2.4.4p3)
[EMAIL PROTECTED]:/tmp/amanda-dbg$ dig
: www.netcontech.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of KEVIN ZEMBOWER
Sent: Wednesday, October 19, 2005 11:57 AM
To: amanda-users@amanda.org
Subject: Need help diagnosing hostname problems
I had an amanda setup that worked fine until two weeks ago, when I
to
respond, and the output is puzzling:
[EMAIL PROTECTED]:/tmp/amanda-dbg$ amcheck -c DBackup
Amanda Backup Client Hosts Check
ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed]
Client check: 2 hosts checked in 0.702 seconds, 1 problem found
Hi,
ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed]
Client check: 2 hosts checked in 0.702 seconds, 1 problem found
That seems like network issue to me, rather than amanda issue.
Did you make sure that your amanda server can ping to www.jhuccp.org?
After renumbering did
Someone have deleted the PTR record of this server. Now i have added it, and
amanda works perfectly.
I thought that was a dns problem, but i was convinced that amanda uses only
forward lookup zone.
Thanks to all for help.
Giovanni
p.s. Sorry again for bad english.
label ok
WARNING: tapecycle (20) = runspercycle (20).
Server check took 0.275 seconds
Amanda Backup Client Hosts Check
ERROR: auriga: [addr 172.30.2.195: hostname lookup failed]
Client check: 1 host checked in 0.007 seconds, 1 problem found
(brought to you
On Mon, 2005-07-04 at 17:24 +0200, Montagni, Giovanni wrote:
ERROR: auriga: [addr 172.30.2.195: hostname lookup failed]
Ok...
[EMAIL PROTECTED] local]# ping auriga
PING auriga.manord.com (172.30.2.195) 56(84) bytes of data.
Your ping test is equivalent to doing host auriga. What Amanda
bkimmob01 label ok
WARNING: tapecycle (20) = runspercycle (20).
Server check took 0.275 seconds
Amanda Backup Client Hosts Check
ERROR: auriga: [addr 172.30.2.195: hostname lookup failed]
Client check: 1 host checked in 0.007 seconds, 1 problem found
Verify
://www.mobileware.be
Dominique Arpin
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
04/07/2005 18:18
To
Montagni, Giovanni
[EMAIL PROTECTED]
cc
amanda-users@amanda.org
Subject
Re: Hostname lookup failed
Hi to all,
I have a problem with amanda.
In december i've set-up amanda
: note0002: [addr 192.168.0.59: hostname lookup failed]
Client check: 1 host checked in 10.025 seconds, 1 problem found
(brought to you by Amanda 2.4.4p3)
In note0002 /tmp/amanda directory in amandad.*.debug files I see:
amandad: time 0.000: strange, this is not a request packet
amandad: time 0.000
Amanda Backup Client Hosts Check
ERROR: note0002: [addr 192.168.0.59: hostname lookup failed]
Client check: 1 host checked in 10.025 seconds, 1 problem found
ERROR [addr 192.168.0.59: hostname lookup failed]
192.168.0.59 is my amanda server IP
: note0002: [addr 192.168.0.59: hostname lookup failed]
Client check: 1 host checked in 10.025 seconds, 1 problem found
(brought to you by Amanda 2.4.4p3)
Thanks for help
Leonid
:
ERROR: hostname: [host hostname:Port not secure]
Weird thing is, the (Port number?) keeps incrementing by 1 every
time I run amcheck!
Do I need to install the newest (same) version of the client?
I have attempted to install the client to the actual RH9 server which is
running amanda
Hi!
I got another Problem with Amanda.
amcheck DailySet1 makes the following
error:
ERROR: dev2 ß
CLIENT: [addr 192.168.10.1 ß
GATEWAY: hostname lookup failed]
The Gateway is pingable also the Client. The Gateway
and the Client are pingable with theyre hostnames (DNS). I also
Sebastian Ksters wrote:
amcheck DailySet1 makes the following error:
ERROR: dev2 CLIENT: [addr 192.168.10.1 GATEWAY: hostname lookup failed]
Is that funny eszet symbol part of the error message?
(wingdings symbol 0xDF in the html source of the mail)
Or did you make that up together
Hello. I am new to amanda, so please forgive any newbie questions. I
have done my best to RTFM for all of the docs I can find googling
amanda. My question relates to the hostname lookup performed by amanda -
I have put the correct machine name/IP in /etc/hosts. There is no DNS
resolution
Hi Santiago,
On Wed, Jan 22, 2003 at 08:03:43AM -0700, Santiago wrote:
Hello. I am new to amanda, so please forgive any newbie questions. I
have done my best to RTFM for all of the docs I can find googling
amanda. My question relates to the hostname lookup performed by amanda
- I have put
On Wed, Jan 22, 2003 at 08:03:43AM -0700, Santiago wrote:
Hello. I am new to amanda, so please forgive any newbie questions. I
have done my best to RTFM for all of the docs I can find googling
amanda. My question relates to the hostname lookup performed by amanda -
I have put the correct
Santiago wrote:
Hello. I am new to amanda, so please forgive any newbie questions. I
have done my best to RTFM for all of the docs I can find googling
amanda. My question relates to the hostname lookup performed by amanda -
I have put the correct machine name/IP in /etc/hosts. There is no DNS
ERROR: listserve.mydomain.net: [host
ais-back01.mydomain.net.84.25.196.in-addr.arpa: hostname lookup failed]
Client check: 1 host checked in 0.053 seconds, 1 problem found
(brought to you by Amanda 2.4.3)
ais-back01.mydomain.net is my tape host and listserve.mydomain.net is
the client I am trying
ERROR: listserve.mydomain.net: [host
ais-back01.mydomain.net.84.25.196.in-addr.arpa: hostname lookup failed]
you get exactly this name? yes?
then you have been told the solution a few weeks ago:
Fix your DNS
Your dns-reverse-zone entry of ais-back01
Martinez, Michael - CSREES/ISTM wrote:
When I first installed amanda I had this problem too, and fixed it by making
sure .amanahosts had correct permissions and correct contents.
Here's the specs, in the case when an Amanda server is also an Amanda
Client.
Server .amandahosts (perms 400)
network stuff is right
Michael Martinez
System Administrator
-Original Message-
From: Mozzi [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 20, 2002 2:35 AM
To: Martinez, Michael - CSREES/ISTM
Cc: 'Gene Heskett'; amanda
Subject: Re: Hostname lookups[continued]
Martinez
On Friday 20 September 2002 02:35, Mozzi wrote:
Martinez, Michael - CSREES/ISTM wrote:
When I first installed amanda I had this problem too, and fixed
it by making sure .amanahosts had correct permissions and
correct contents.
Here's the specs, in the case when an Amanda server is also an
ERROR: my host: [addr 192.168.2.215: hostname lookup failed]
Client check: 1 host checked in 0.028 seconds, 1 problem found
--
The ip addy it gives back is wrong.[192.168.2.215
Title: RE: Hostname lookups
Hey Mozzi,
There seems to be an issue with Amanda and reverse DNS lookups - I had many when I wanted to setup backup clients across multiple subnets.
But in the end if you have your backup client having the ip/hostname of the backup server in it's /etc/hosts
Server check took 5.020 seconds
Amanda Backup Client Hosts Check
ERROR: my host: [addr 192.168.2.215: hostname lookup failed]
Client check: 1 host checked in 0.028 seconds, 1 problem found
Gene Heskett wrote:
k 5.020 seconds
Amanda Backup Client Hosts Check
ERROR: my host: [addr 192.168.2.215: hostname lookup failed]
Client check: 1 host checked in 0.028 seconds, 1 problem found
On Thursday 19 September 2002 08:57, Mozzi wrote:
Gene Heskett wrote:
k 5.020 seconds
Amanda Backup Client Hosts Check
ERROR: my host: [addr 192.168.2.215: hostname lookup failed]
Client check: 1 host checked in 0.028 seconds, 1 problem found
11:01 AM
To: Mozzi
Cc: amanda
Subject: Re: Hostname lookups[continued]
On Thursday 19 September 2002 08:57, Mozzi wrote:
Gene Heskett wrote:
k 5.020 seconds
Amanda Backup Client Hosts Check
ERROR: my host: [addr 192.168.2.215: hostname lookup failed
On Thursday 19 September 2002 11:31, Martinez, Michael - CSREES/ISTM
wrote:
When I first installed amanda I had this problem too, and fixed it
by making sure .amanahosts had correct permissions and correct
contents.
Here's the specs, in the case when an Amanda server is also an
Amanda
On Tue, 20 Nov 2001 at 12:41pm, Rafe Thayer wrote
I've been trying to configure an amanda client on a Sun box. When I do an
amcheck the server checks out fine, but I get this warning from the
client:
WARNING: al-bundy.cs.ucla.edu: selfcheck request timed out. Host down?
I've attached the
Hi Folks,
I've been trying to configure an amanda client on a Sun box. When I do an
amcheck the server checks out fine, but I get this warning from the
client:
WARNING: al-bundy.cs.ucla.edu: selfcheck request timed out. Host down?
I've attached the contents of the amandad.xxx.debug file from
that the client is in our KDC.
I still get the error:
Amanda Backup Client Hosts Check
ERROR: host.comp.bogus: couldn't resolve hostname
Client check: 5 hosts checked in 0.266 seconds, 1 problem found.
What might be the problem:
* I need to recompile amanda for a client
ERROR: host.comp.bogus: couldn't resolve hostname
What version of Amanda are you running? I cannot find this error message
text in 2.4.2 or beyond.
However, I suspect this message comes from the server, not the client,
i.e. the server is saying it has a problem making the request to client
Hi Rafe!
On 21 Nov 01 at 11:10 you wrote:
I've been trying to configure an amanda client on a Sun box. When I do an
amcheck the server checks out fine, but I get this warning from the
client:
WARNING: al-bundy.cs.ucla.edu: selfcheck request timed out. Host down?
The server is
I've been trying to configure an amanda client on a Sun box. When I do an
amcheck the server checks out fine, but I get this warning from the
client:
WARNING: al-bundy.cs.ucla.edu: selfcheck request timed out. Host down?
I've attached the contents of the amandad.xxx.debug file from
Hi Folks,
I've been trying to configure an amanda client on a Sun box. When I do an
amcheck the server checks out fine, but I get this warning from the
client:
WARNING: al-bundy.cs.ucla.edu: selfcheck request timed out. Host down?
I've attached the contents of the amandad.xxx.debug file from
On Tue, 20 Nov 2001 at 12:41pm, Rafe Thayer wrote
I've been trying to configure an amanda client on a Sun box. When I do an
amcheck the server checks out fine, but I get this warning from the
client:
WARNING: al-bundy.cs.ucla.edu: selfcheck request timed out. Host down?
I've attached the
On Wed, 16 May 2001, John R. Jackson wrote:
I recently decided to add another Amanda client to my existing Amanda
setup (server running v2.4.1p1) where I back up three clients using Krb4.
Does the new client also use Krb4?
Yes, the clients are using Amanda 2.4.2 with the Krb4 patches.
If
with
this:
-=-
Amanda Backup Client Hosts Check
ERROR: shell1.nominum.com: couldn't resolve hostname
Client check: 4 hosts checked in 0.320 seconds, 1 problem found.
-=-
Granted, it has been a couple of years since I have had to add a new
Amanda client, so I might be missing
I recently decided to add another Amanda client to my existing Amanda
setup (server running v2.4.1p1) where I back up three clients using Krb4.
Does the new client also use Krb4?
ERROR: shell1.nominum.com: couldn't resolve hostname
Here's the relevant code:
#ifdef KRB4_SECURITY
ERROR: samba2: [addr 10.0.1.2: hostname lookup failed]
I think this is saying that on host samba2 it could not take IP address
10.0.1.2 and convert that back to a host name. That IP address should
be the IP address of the machine that connected to samba2, i.e. your
tape server (where you ran
On Fri, Apr 27, 2001 at 02:15:47PM -0500, John R. Jackson wrote:
I think this is saying that on host samba2 it could not take IP address
10.0.1.2 and convert that back to a host name. That IP address should
be the IP address of the machine that connected to samba2, i.e. your
tape server (where
:
Amanda Backup Client Hosts Check
ERROR: stallman: [host stallman.: hostname lookup failed]
Client check: 1 host checked in 0.334 seconds, 1 problem found.
Running version 2.4.1p1
DNS is right, reverse lookups are right (the hostname is defined in
/etc
I am having difficulty getting amcheck to do a proper hostcheck...
Ummm, it's not amcheck (or Amanda's) fault. They are just using what
the system provides ...
ERROR: stallman: [host stallman.: hostname lookup failed]
What this says is that amandad on the client (yes, I know you said it's
Hi all,
I encounter following error from my CNCBACK in 192.168.0.83
[root@CNCBACK DailySet1]# su backup -c "amcheck DailySet1 -c"
Amanda Backup Client Hosts Check
ERROR: office: [addr 192.168.0.83: hostname lookup failed]
Client check: 1 host checke
Charlie!
Amanda Backup Client Hosts Check
ERROR: office: [addr 192.168.0.83: hostname lookup failed]
Client check: 1 host checked in 0.109 seconds, 1 problem found
(brought to you by Amanda 2.4.2)
But 'office' is really pingable in fact,
What does
"David" == David Lloyd [EMAIL PROTECTED] writes:
David If that doesn't work, try dig 83.0.168.192.in-addr.arpa
dig -x 192.168.0.83 is less of a mouthful. :-)
Ben
But how can I disable it, I meaning not using reverse DNS lookup?
--Charlie
- Original Message -
From: "David Lloyd" [EMAIL PROTECTED]
To: "Charlie Zhu" [EMAIL PROTECTED]
Cc: "Amanda Users" [EMAIL PROTECTED]
Sent: Tuesday, March 13, 2001 1:56 PM
Subje
Hmmm..
To disable it completely, I think you'd need to hack the source.
DSL
Oops!
To disable it completely, I think you'd need to hack the source.
Obvously you don't need to but I wouldn't if I were you :-)
DSL
--
CWA - Chin Waggers Association
"Let's sit around and complain about something.
Our topic for today is: ADSL...h...that `L'
stands for Linux
Hello everybody:
i configured amanda to run as a server in a machine whith an oldhostname
Now i changed the hostname to newhostname
when i do amrecover it looks for oldhostname.
How can i tell amanda that i have changed the name of the server where it is
running?
...
when i do amrecover it looks for oldhostname.
How can i tell amanda that i have changed the name of the server where it is
running?
Do a "man amrecover" and look for the -s and -t flags.
If you don't want to use those flags and want it to pick the new name
by default, you'll have to
I just got a note from amcheck about a problem with one of my client
workstations:
Amanda Backup Client Hosts Check
ERROR: metro: [addr 203.24.38.228: hostname lookup failed]
Client check: 5 hosts checked in 1.692 seconds, 1 problem found
This is nonsense -- I
ERROR: metro: [addr 203.24.38.228: hostname lookup failed]
FYI, this is reported from the client side, so you need to do your
testing there, not on the server.
This is nonsense -- I can ping the host, so my resolver is not broken.
What else can cause this?
It says that when Amanda tried to do
Is it possible that the error message could be improved?
Sure. Do you have a suggestion?
For starters, it should state that the error is coming from the client, not
from amcheck on the tape server. Something like:
"Client-side error: unable to perform reverse lookup on IP".
My /etc/resolv.conf:
domain ns31.newsbook.net
search ns31.newsbook.net
Here you are saying that your domain is ns31.newsbook.net.
Is that what you want?
- Peter
--
Peter N. M. Hansteen [EMAIL PROTECTED] http://www.datadok.no
Datadokumentasjon A/S, Bredsgaarden 2, N-5003 Bergen, Norway
richard wrote:
Dear all,
Thanks for your hint. But I have checked the following and the problem
still exists.
After the ./amdump, I still get the error:
FAILURE AND STRANGE DUMP SUMMARY:
202.85.165 /home lev 0 FAILED [202.85.165.88: [addr 202.85.164.38:
hostname
lookup failed
*** Default servers are not available
The machines which amanda thinks are the default name servers for
your domain are for some reason not responding, it seems. Check
your resolv.conf.
--
Peter N. M. Hansteen [EMAIL PROTECTED] http://www.datadok.no
Datadokumentasjon A/S, Bredsgaarden
richard wrote:
*** Default servers are not available
Do you have a DNS server? It seems that you don't. If you really don't
have one, then you should update your /etc/hosts file (or, more
precisely, whichever alternative to DNS is listed in your
/etc/nsswitch.conf file in the entry
From: Thorsten Flick [EMAIL PROTECTED]
Date: Thu, 16 Nov 2000 16:37:49 +0100
DNS is running well. and i administer it for myself.
Good -- reducing the effects of "middlemen" helps get work done. :-}
[stuff about gethostbyname() gethostbyaddr()...]
Ok, i will test this. But, did nslookup
91 matches
Mail list logo
