> dnsserver: Couldn't resolve IP address for host localhost.
You should have an /etc/hosts and have resolv.conf configured properly.
> On the console, I can ping localhost, but how can I configure
> localhost MX records?
You don't. It said that Java wasn't able to resolve the IP address, not an
Hi,
We had a bug both in 2.3rc2 and 2.2 that cause the outgoing spool to
stuck if you have more than 1000 messages and to consume too much CPU if
you only have "waiting" messages in the spool.
Outgoing spooling stuck over old mails when more than 1000 old mails are
present in outgoing:
http://iss
I wanted to let the list know what I have found out since my last post:
I upgraded to version 2.3rc2 and no more error messages and email works
(the outgoing email problem went away)
I tried to use the spool file from 2.2 in my 2.3rc2 installation, but
the error messages came back (I think wh
I see these message in the dns log for james-2.2.0
08/09/06 11:11:09 ERROR dnsserver: Couldn't resolve IP address for host
localhost.
08/09/06 11:11:28 INFO dnsserver: Couldn't resolve MX records for domain
localhost.
(it goes on, you get the idea)
On the console, I can ping localhost, but how
To conclude this thread... it looks like my router is retarded.
"If you want the 510 v4 to do a nameserver for your LAN and your needs
are beyond the simple name - address resolving, stay away from it.
It cannot handle nor forward anything but A and PTR queries, making
it impossible to run a mails
If you're looking for a low cost windows option for home LAN dns I
couldn't reccomend simple dns plus highly enough. (If English is not
your native tongue that means I *like* it a lot! ;-)
Although it seems to have doubled in price since I paid for it four years ago...
You can host your own domain
> Yes this is all true. It can find other domains as long as I have
> visited them
> once already (eg with browser) so that they are cached.
>
It shouldnt matter how you trigger the lookup - james and a web browser use
the same method.
>
> It is a simple all in one ADSL router. It seems that it
Daniel Perry netcase.co.uk> writes:
> 1. a remote dns server can find the domain
> 2. your local dns server can't find the domain
> 3. your local dns server can find other domains
Yes this is all true. It can find other domains as long as I have visited them
once already (eg
So,
1. a remote dns server can find the domain
2. your local dns server can't find the domain
3. your local dns server can find other domains
If your machine is using just this DNS server and 3 is true, then it must be
doing recursive lookups. What sort of network setup is this?
How rec
Danny Angus slc.co.uk> writes:
> 1/ because it doesn't delegate lookups
> 2/ because it might also be stymied by your firewall
> 3/ because your paranoid network admins won't let you.
>
> Look at the operating system NS settings on the server.
The firewall is also the DNS and DHCP server and th
> Hi, I have James set up at home behind a firewalled ADSL router and I was
> wondering why I cannot send remote mail. I am using the default
configuration
> which has suto detected my internal DNS server at 10.0.0.138. Why would
this
> DNS server not allow James to resolve external addresses?
1
Hi, I have James set up at home behind a firewalled ADSL router and I was
wondering why I cannot send remote mail. I am using the default configuration
which has suto detected my internal DNS server at 10.0.0.138. Why would this
DNS server not allow James to resolve external addresses?
Messages
12 matches
Mail list logo
