I'm trying to set up a backup e-mail server which only recives e-mails but the messages keep boucing back saying
immolo@immolo.net
unrouteable mail domain "immolo.net"

Now I'm sure this is a problem in bind but I can't see what and I have follow a few howtos but here is a copy if it helps:

$TTL 3D
@ IN SOA immolo.net. immolo.immolo.net. (
2005041403
8H ; Refresh
2H ; Retry
4W ; Expire
1D ) ; Minimum TTL
IN NS localhost.
IN NS ns1.immolo.net.
IN NS ns2.immolo.net.
IN MX 10 localhost.
IN MX 20 mail.immolo.net.
;
localhost A 127.0.0.1
server A 81.96.17.126
ns1 A 81.96.17.126
ns2 A 81.96.17.126
www CNAME server
ftp CNAME server
mail CNAME server


If anyone can help me with this problem I would be very greatful.

Can you resolve the domain itelf via ping or anything from commandline at the server? if not then its a problem with /etc/hosts

I can resolve the domain with any of the above lines but if I type "ping immolo.net" is comes back with domain unknown.

If this is what you meant could you possible show me how to fix this in /etc/hosts?

Ian

pico /etc/hosts then put your datacenters nameservers in there.

ie. nameserver 123.123.123123 in that file

should include the word nameserver and 123.123.123.123 (which would be the ip your DC provides, you can use this for testing purposes.

nameserver 67.97.234.4

This still isn't working as far as I can see my domain works just not without a subdomain on it. my /etc/hosts is now looking like this:


127.0.0.1 localhost
192.168.0.1 server.immolo.net server
192.168.0.2 laptop.immolo.net laptop
192.168.0.3 rachel.immolo.net rachel
192.168.0.4 dev.immolo.net dev
nameserver 81.96.17.126

The other computers being in the intranet of course.

er sorry it should be /etc/resolv.conf heh

Example.

root@thunder [~]# cat /etc/resolv.conf
nameserver 67.97.234.4
nameserver 127.0.0.1
nameserver 207.218.245.135
nameserver 207.218.247.135

I did wonder :P
anyway with the change it is still bringing up nothing

nameserver 81.96.17.126
nameserver 127.0.0.1
nameserver 194.168.4.100
nameserver 194.168.8.100

That's the output of my /etc/resolv.conf

I can't see where the problem is.

i'm guessing you can ping ip's and so forth on that server? Try pinging google.com and just to make sure dns is actually being resolved on that server

PING google.com (216.239.39.99) 56(84) bytes of data.
64 bytes from 216.239.39.99: icmp_seq=1 ttl=241 time=345 ms
64 bytes from 216.239.39.99: icmp_seq=2 ttl=241 time=344 ms
64 bytes from 216.239.39.99: icmp_seq=3 ttl=241 time=1233 ms

Plus I'm using the laptop to write this which is in the intranet so the only thing it can be is the name servers, the whois for the domain name gives:

Domain Name: IMMOLO.NET
Registrar: ABACUS AMERICA, INC. DBA NAMES4EVER
Whois Server: whois.names4ever.com
Referral URL: http://www.names4ever.com
Name Server: NS1.IMMOLO.NET
Name Server: NS2.IMMOLO.NET
Status: ACTIVE
Updated Date: 23-jan-2005
Creation Date: 04-jan-2005
Expiration Date: 04-jan-2006

I don't know if that helps or not.

ok then if you can ping google.com its something to do with your dns on your domain your trying to get things to work with.

You shouldn't have:

IN MX 10 localhost.

MX entries should point to an A record (which resolves to a routable IP address.)

Also, you shouldn't have:

mail CNAME server

CNAME aliases shouldn't be used for a MX record. Use A records instead.

Finally:

IN NS localhost.

You only need NS records for ns1.immolo.net and ns2.immolo.net. A NS record pointing to localhost will most likely cause problems.

If you add an additional A record:

A 81.96.17.126

Then you will be able to ping both IMMOLO.NET and WWW.IMMOLO.NET