Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: paul_NZ on January 08, 2011, 11:34:19 PM
-
1. SME Server in Server/Gateway Mode running SME running 7.5.1 with all updates installed
2. Previously able to access <domain>.co.nz, www.<domain>.co.nz, cpanel.<domain>.co.nz, etc hosted externally
3. This morning not able to access domains as described in 2 above
4. Rebooted server and then able to access www.<domain>.co.nz ONLY
5. command
; <<>> DiG 9.2.4 <<>> localhost www.<domain>.co.nz
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7467
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.<domain>.co.nz. IN A
;; ANSWER SECTION:
www.<domain>.co.nz 12027 IN A xx.xxx.xxx {- correct external IP address}
;; Query time: 0 msec
;; SERVER: 192.168.1.20#53(192.168.1.20)
;; WHEN: Sun Jan 9 11:18:34 2011
;; MSG SIZE rcvd: 62
6. command
dig localhost <domain>.co.nz
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12812
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;localhost. IN A
;; ANSWER SECTION:
localhost. 655360 IN A 127.0.0.1
;; Query time: 0 msec
;; SERVER: 192.168.1.20#53(192.168.1.20)
;; WHEN: Sun Jan 9 11:21:56 2011
;; MSG SIZE rcvd: 43
; <<>> DiG 9.2.4 <<>> localhost <domain>.co.nz
;; global options: printcmd
;; connection timed out; no servers could be reached
7. command dig cpanel.<domain>.co.nz gives a similar result to 6 above
8. Accessing ANY of these addresses from 'outside' of the SME server works perfectly so my question is what needs to be fixed within the SME server to allow access to these addresses?
Thanks in advance.
-
Is <domain>, or any of the subdomains of <domain> configured as a domain on your SME server? If so, is "Domain DNS servers" set to "resolve locally" or to "Internet DNS servers"?
Are there any other settings on the SME server related to <domain> (ProxyPass, for example)?
Is your SME server configured to use "corporate DNS" (that is, do you have a specific DNS server configured), or is it using SME default settings (DNS direct from root DNS servers)?
Have there been any changes made to the DNS settings for <domain> in the 3 days before problems began?
Have you verified the observed behavior from multiple LAN workstations?