DNS problem on installation

[Sami]

Please could I ask for some help on this issue please as it continues to give me problems? I have configured my Ubuntu system exactly as described in the installation guide but during the installation of ./install.sh, I still get the following problem:

Setting defaults...No results returned for A lookup of dell-desktop.mydomain.com
Checked nameservers:
192.168.0.100

DNS ERROR resolving dell-desktop.mydomain.com
It is suggested that the hostname be resolveable by DNS
Change hostname [Yes]


The IP address of 192.168.0.100 is my router. I use it for DNS. Queries on domain name, such as dig google.com work ok... Also below is the result of dig mydomain.com (where mydomain is substituted for my own domain name).

dig dell-desktop.mydomain.com

; <<>> DiG 9.4.2 <<>> dell-desktop.mydomain.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26721
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;dell-desktop.mydomain.com. IN A

;; AUTHOR.ITY SECTION:
mydomain.com. 10800 IN SOA ns9.hostingcare.net. hostmaster.hostingcare.net. 1219528502 10800 3600 604800 10800

;; Query time: 828 msec
;; SERVER: 192.168.0.100#53(192.168.0.100)
;; WHEN: Mon Jan 5 04:46:58 2009
;; MSG SIZE rcvd: 107


My system is purely for testing Zimbra. It is just a basic system. However I do not want my MX record at 'mydomain.com' to point at my public IP address, as my system is just for testing. Thanks.

[uxbod]

Please post the following

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname` <- note backticks and not single quotes

as you are behind a firewall/router on a private IP you will need to setup a Wiki :: Split DNS architecture which will allow you to then add a internal MX record for testing.

[Sami]

Originally Posted by uxbod

Please post the following

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname` <- note backticks and not single quotes

Thanks very much, Uxbod. Here are my results. However, the host with back-ticks didn't get executed properly - see below. I tried using another shell, with /bin/bash and /bin/dash but it didn't make any difference.

# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost

192.168.0.131 dell-desktop.zimbdomain.com dell-desktop

========================
# 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

========================
# cat /etc/resolv.conf

### BEGIN INFO

#

# Modified_by: NetworkManager

# Process: /usr/bin/NetworkManager

# Process_id: 5460

#

### END INFO



nameserver 192.168.0.100





domain zimbdomain.com


========================
# dig zimbdomain.com mx



; <<>> DiG 9.4.2 <<>> zimbdomain.com mx

;; global options: printcmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37348

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3



;; QUESTION SECTION:

;zimbdomain.com. IN MX



;; ANSWER SECTION:

zimbdomain.com. 65162 IN MX 10 mail.zimbdomain.com.



;; AUTHORITY SECTION:

zimbdomain.com. 57154 IN NS ns9.hostingcare.net.

zimbdomain.com. 57154 IN NS ns10.hostingcare.net.



;; ADDITIONAL SECTION:

mail.zimbdomain.com. 65162 IN A 70.86.109.99

ns9.hostingcare.net. 25305 IN A 70.86.109.99

ns10.hostingcare.net. 25305 IN A 70.86.109.59



;; Query time: 197 msec

;; SERVER: 192.168.0.100#53(192.168.0.100)

;; WHEN: Mon Jan 5 11:56:04 2009

;; MSG SIZE rcvd: 149


========================
# dig zimbdomain.com any



; <<>> DiG 9.4.2 <<>> zimbdomain.com any

;; global options: printcmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6618

;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 2, ADDITIONAL: 0



;; QUESTION SECTION:

;zimbdomain.com. IN ANY



;; ANSWER SECTION:

zimbdomain.com. 57329 IN A 70.86.109.99

zimbdomain.com. 57329 IN NS ns9.hostingcare.net.

zimbdomain.com. 57329 IN NS ns10.hostingcare.net.



;; AUTHORITY SECTION:

zimbdomain.com. 57329 IN NS ns10.hostingcare.net.

zimbdomain.com. 57329 IN NS ns9.hostingcare.net.



;; Query time: 177 msec

;; SERVER: 192.168.0.100#53(192.168.0.100)

;; WHEN: Mon Jan 5 11:56:43 2009

;; MSG SIZE rcvd: 124


========================
# host `zimbdomain.com`

bash: zimbdomain.com: command not found

Usage: host [-aCdlriTwv] [-c class] [-N ndots] [-t type] [-W time]

[-R number] [-m flag] hostname [server]


========================

# host 'zimbdomain.com'

zimbdomain.com has address 70.86.109.99

zimbdomain.com mail is handled by 10 mail.zimbdomain.com.

[uxbod]

You just need to type

host `hostname`

hostname will automagically be expanded to what your O/S believe is the actual hostname of the server. Even with that in mind you will need to setup a Split DNS (per my first posting) as the MX is being resolved to the external one.

[Sami]

Originally Posted by uxbod

You just need to type

host `hostname`

hostname will automagically be expanded to what your O/S believe is the actual hostname of the server. Even with that in mind you will need to setup a Split DNS (per my first posting) as the MX is being resolved to the external one.

$ host `hostname`
Host dell-desktop not found: 3(NXDOMAIN)

Apologies for that, I assumed hostname was my actual domain. See results above, now I've entered it correctly!!

[uxbod]

Yep, so you need to setup a split DNS architecture.

[Sami]

Originally Posted by uxbod

Yep, so you need to setup a split DNS architecture.

This sounds very complex Uxbod. Bearing in mind this is only for my testing and familiarisation process, wouldn't it be easier to just register a new domain and point the MX record at my IP address?

[uxbod]

It really is not complicated ... As you are on a private IP you either need to install a DNS server on your ZCS installation or if you already have a DNS server within your internal network create a MX record for your test domain there. You will then need to update /etc/resolv.conf on your ZCS server to point too it.