Zimbra

Dijital · #1 (**permalink**) 06-12-2007, 07:49 PM

So my first install I'm pretty sure is horked (I still have it on a VM just in case)
So I decided to reinstall since I believe I messed up the DNS during install. But here is the error I am getting now:

Quote:

DNS ERROR resolving mail.dijital.us
It is suggested that the hostname be resolveable via DNS
Re-Enter hostname [Yes]
Please enter the logical hostname for this host [mail.dijital.us]
No results returned for A lookup of mail.dijital.us
Checked nameservers:
172.16.1.240
24.220.0.10
24.220.0.11

DNS ERROR resolving mail.dijital.us
It is suggested that the hostname be resolveable via DNS
Re-Enter hostname [Yes]

Here is my /etc/hosts file:

Quote:

127.0.0.1 localhost.localdomain localhost
172.16.1.240 mail.dijital.us mail

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Here is my /etc/bind/zones/mail.dijital.us.db:

Quote:

; mail.dijital.us
$TTL 604800
@ IN SOA ns.mail.dijital.us. root.mail.dijital.us. (
2007061201
28800
3600
604800
38400
);
@ IN NS ns
IN MX 10 mail
IN A 172.16.1.240
email IN A 172.16.1.240
mail IN A 172.16.1.240
ns IN A 172.16.1.240
root IN A 172.16.1.240

/etc/resolv.conf:

Quote:

search mail.dijital.us
nameserver 172.16.1.240
nameserver 24.220.0.10
nameserver 24.220.0.11

/etc/bind/named.conf.local:

Quote:

zone "mail.dijital.us" {
type master;
file "/etc/bind/zones/mail.dijital.us.db";
};

/etc/bind/named.conf.options:

Quote:

options {
directory "/var/cache/bind";

// If there is a firewall between you and nameservers you want
// to talk to, you might need to uncomment the query-source
// directive below. Previous versions of BIND always asked
// questions using port 53, but BIND 8.1 and later use an unprivileged
// port by default.

// query-source address * port 53;

// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.

forwarders {
24.220.0.10;
24.220.0.11;
// };

auth-nxdomain no; # conform to RFC1035

// By default, name servers should only perform recursive domain
// lookups for their direct clients. If recursion is left open
// to the entire Internet, your name server could be used to
// perform distributed denial of service attacks against other
// innocent computers. For more information on DDoS recursion:
// CVE-2006-0987 (under review)

allow-recursion { localnets; };

// If you have DNS clients on other subnets outside of your
// server's "localnets", you can explicitly add their networks
// without opening up your server to the Internet at large:
// allow-recursion { localnets; 192.168.0.0/24; };

// If your name server is only listening on 127.0.0.1, consider:
// allow-recursion { 127.0.0.1; };

};

Dig:

Quote:

; <<>> DiG 9.3.2 <<>> dijital.us
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33092
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;dijital.us. IN A

;; ANSWER SECTION:
dijital.us. 38400 IN A 208.107.59.182

;; Query time: 536 msec
;; SERVER: 24.220.0.10#53(24.220.0.10)
;; WHEN: Tue Jun 12 21:19:23 2007
;; MSG SIZE rcvd: 44

If there any other logs/files you need to see please let me know, would be glad to post them. Thanks for any who can help. Also should know that this machine is in vmware as well, once I have it fully functioning in vmware will switch to physical server. Another thought do we need a CNAME record in there?