Problem to access the console admin

[karukera]

From some acces providers POP, i have weird problems to access the console admin.
I have to wait several minutes before having access to the login screen then several minutes to access the console.

I have to reload the page many times before connecting.

The problem is that i have this problem only with one provider.
All is working fine with the others.

I tried to reach their customer service, they are just able to ask my name and to reply that "they don't guarantee that all applications can run on their network". That's TRUE.

I cannot believe that there are filters on thei network.

I suspected a network configuration problem and asked my supplier to verify the configuration. He told me that the configuration is correct.

As I am definitely not a specialist in that matter, i gave up

But, but! I just read a post refering to the dig command so i applied it to my MX and the following is the result.

I'm a bit confused by the fact that there are no answer and answer question.

I won't be able to understand your technical replies but if you suspect that there may be a configuration problem, don't hesitate to let me know and guide me.

OUTPUT OF DIG MX webmail.domain.com

; <<>> DiG 9.3.2 <<>> MX webmail.domain.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 577
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;webmail.domain.com. IN MX

;; AUTHORITY SECTION:
domain.com. 600 IN SOA ns.provider.net. master.domain.com. 2009111001 10800 900 604800 86400

;; Query time: 187 msec
;; SERVER: xxx.xxx.172.1#53(xxx.xxx.172.1)
;; WHEN: Sat Sep 11 10:55:06 2010
;; MSG SIZE rcvd: 97

[phoenix]

OUTPUT OF DIG MX webmail.domain.com

; <<>> DiG 9.3.2 <<>> MX webmail.domain.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 577
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;webmail.domain.com. IN MX

;; AUTHORITY SECTION:
domain.com. 600 IN SOA ns.provider.net. master.domain.com. 2009111001 10800 900 604800 86400

;; Query time: 187 msec
;; SERVER: xxx.xxx.172.1#53(xxx.xxx.172.1)
;; WHEN: Sat Sep 11 10:55:06 2010
;; MSG SIZE rcvd: 97

According to that output you have no MX record for your server, you do need a valid A & MX record for your Zimbra server. In addition, if you are behind a firewall (and/or a NAT router) you will need a Split DNS set-up.

[karukera]

OK. So how do you explain that everything works fine when the server is accessed from another provider ?

[phoenix]

OK. So how do you explain that everything works fine when the server is accessed from another provider ?

I don't know why you think I'd need to explain it. All I'm telling you is that the information you've provided shows no MX records, I don't know who is responsible for those DNS records nor why it's happening from that location - that's up to you to ask your provider (your ISP or whoever is responsible for the DNS) why that command doesn't give the correct response. Merely saying that your provider has said 'it's all OK' doesn't actually prove anything.

[karukera]

Remember that i'm a Mister Jourdain in networking technologies so what is obvious for you is not necessarily obvious for me but I might have been more precise.

I agrre with you. I have no doubt that the configuration is incorrect and i'm certain that the one who managed the server is wrong.

What I wanted to say is that, despite the fact that the configuration is incorrect, when I use the server with this configuration, through "A" ISP, everything works fine and when I use it through "B" ISP, i can't access the server.

The server is not hosted nor managed by any of the ISP mentionned.

I don't thought you need to explain it but i just wanted to mark my astonishement that the server can run without MX record.

Am i wrong to be surprised or is it legitimate ?

May this specificic case indicate that ZCS can work without a MX record ?

May we think that there is a mysterious configuration that allows ZCS to work. (the server is installed on a virtual machine via Xen hypervisor on a physical machine hosted by OVH.)

May I inferred that my acces problem to the administration console through a specific provider is not necessarily linked to this configuration or the way zimbra operates ?

If you want to verify by yourself, I can send you a mail from the server so you'll be able to dig the domain name yourself.