Quote:
Originally Posted by bhwong  > My mistake, that should have read: the resolv.conf should only have the IP of your LAN DNS server, this is from your resolv.conf.
My LAN do not have a DNS server. So it should be my ISP DNS server right? |
According to your earlier output your LAN does have a DNS server, this is from your resolv.conf:
Code:
nameserver 192.168.190.1
and the output you provided earlier shows that the output from the dig query was provided by a LAN DNS server:
Code:
; Query time: 8 msec
;; SERVER: 192.168.190.250#53(192.168.190.250)
;; WHEN: Tue Nov 3 18:26:12 2009
;; MSG SIZE rcvd: 115
Your hosts file also shows you to be on a private LAN IP address for your Zimbra server:
Code:
192.168.190.250 zimbra.mydomain.com zimbra
If that's the case you should have a DNS server on your LAN that provides the LAN IP of your Zimbra server when queried from the Zimbra server using the commands I gave you earlier.
Quote:
Originally Posted by bhwong > Those results still show no A or MX records for the domain, can you not see that?
What will it show if there are A or MX records? I'm not familiar with dig output but Pingability.com: Web Site Monitoring and Alert Service output does show that my A and MX records are working fine. Something to do with the nameserver above? |
You haven't shown anything that has your A & MX records in it, there's no output other than the pingability web site in your link. If you wish to see what the records would look like check the output for the dig commands using google.com as an domain name.