Okay here is the problem.

Seems that some people can get to my page some of the time and other times they can't.

AOL'ers seem to have a problem most of the time.

The site is http://www.health4m.com

I am NOT a network/gateway guru so I am calling on you guys to see if anyone can problem solve this issue. I have contacted support at my web hosting company and I keep getting the reply, " We can get to it NO problem"... (they cut and paste me part of my page and that's it)... I don't know if they don't want to deal with this or just don't understand me. Don't want to cut down my webhosting provider gnxonline.com BECAUSE until this happened they have been terrific... but.....but... I am going crazy with this issue..

If you do a whois on health4m.com you will see the following:
Domain servers in listed order:

NS5.J-SAINSBURY.NET 195.224.187.102
NS6.J-SAINSBURY.NET 195.224.187.103

BUT on the web administration page they have this information... health4m. com. -> ns. health4m. com.
ns. health4m. com. -> 195. 224. 187. 101

Is that the problem? The ns.health4m.com is .101 and NOT .102, 0r .103?
The actual IP is 195.224.187.105 ... but I am sure you guys will figure that one out. *smile*...

Someone had mentioned "cluster dns" issues? I had NO idea what they were talking about... any ideas?

*sigh*.. again any help here, and again it seems to be intermitant.. works sometimes and NOT others..

Help and any suggestions if you can.. Or what I might say to them to GET them to take a closer look..

Thanks...

A couple of things:

1. Whois information:


Domain Name: HEALTH4M.COM

Administrative Contact:
Domain Accounts sales@Gnxonline.com
GNXONLINE
Gnxonline House 424A Lewisham High Street
Lewisham, London SE13 6LJ
UK
Phone- 44 0208 240 9991
Fax- 44 0208 692 4291
Technical Contact:
Domain Accounts sales@Gnxonline.com
GNXONLINE
Gnxonline House 424A Lewisham High Street
Lewisham, London SE13 6LJ
UK
Phone- 44 0208 240 9991
Fax- 44 0208 692 4291

Record updated on 2002-02-23 07:42:49.
Record created on 2002-02-23.
Record expires on 2004-02-23.
Database last updated on 2002-03-13 06:39:48 EST.

Domain servers in listed order:

NS5.J-SAINSBURY.NET 195.224.187.102
NS6.J-SAINSBURY.NET 195.224.187.103


bah...tell your host to remember the two network rule.

take a look at the zone files for the two name servers:


[root@ns1 root]# dig @NS5.J-SAINSBURY.NET health4m.com axfr

; <<>> DiG 9.1.3 <<>> @NS5.J-SAINSBURY.NET health4m.com axfr
;; global options: printcmd
health4m.com. 86400 IN SOA ns.health4m.com. support.gnxonli
ne.com. 1014426038 10800 3600 604800 86400
health4m.com. 86400 IN MX 10 mail.health4m.com.
health4m.com. 86400 IN A 195.224.187.105
health4m.com. 86400 IN NS ns.health4m.com.
ftp.health4m.com. 86400 IN CNAME health4m.com.
mail.health4m.com. 86400 IN CNAME health4m.com.
ns.health4m.com. 86400 IN A 195.224.187.101
webmail.health4m.com. 86400 IN A 195.224.187.101
www.health4m.com. 86400 IN CNAME health4m.com.
health4m.com. 86400 IN SOA ns.health4m.com. support.gnxonli
ne.com. 1014426038 10800 3600 604800 86400
;; Query time: 87 msec
;; SERVER: 195.224.187.102#53(NS5.J-SAINSBURY.NET)
;; WHEN: Wed Mar 13 18:33:43 2002
;; XFR size: 11 records


Ugh...why would you reference a different server in your SOA? Anyway, that's not the interesting part:


[root@ns1 root]# dig @NS6.J-SAINSBURY.NET health4m.com axfr
dig: Couldn't find server 'NS6.J-SAINSBURY.NET': Name or service not known


That delegation is sooo lame :D.

On the plus side, there is good information on the SOA host, even if it doesn't make sense to put it there:


[root@ns1 root]# dig @ns.health4m.com health4m.com axfr

; <<>> DiG 9.1.3 <<>> @ns.health4m.com health4m.com axfr
;; global options: printcmd
health4m.com. 86400 IN SOA ns.health4m.com. support.gnxonli
ne.com. 1014426038 10800 3600 604800 86400
health4m.com. 86400 IN MX 10 mail.health4m.com.
health4m.com. 86400 IN A 195.224.187.105
health4m.com. 86400 IN NS ns.health4m.com.
ftp.health4m.com. 86400 IN CNAME health4m.com.
mail.health4m.com. 86400 IN CNAME health4m.com.
ns.health4m.com. 86400 IN A 195.224.187.101
webmail.health4m.com. 86400 IN A 195.224.187.101
www.health4m.com. 86400 IN CNAME health4m.com.
health4m.com. 86400 IN SOA ns.health4m.com. support.gnxonli
ne.com. 1014426038 10800 3600 604800 86400
;; Query time: 89 msec
;; SERVER: 195.224.187.101#53(ns.health4m.com)
;; WHEN: Wed Mar 13 18:35:58 2002
;; XFR size: 11 records



My guess is that some ISPs are hitting that bad record, and so have no information about your domain -- though they shouldn't. Tell them to fix that, and you should be okay.

uuallan,

Well I just KNEW one of you guys would know... thanks so much.. GREAT site here by the way.. thanks muchly.. ON my way to tell them and hopefully I will not get ignored this time. THEY have been wonderful... thus far short of this... It is like they don't want to deal with it, or think I am nuts..

AOL'ers are having a REAL tough time.. any ideas there? Or may this fix it?

AGAIN THANKS so very much uuallan for taking the time... I was about to go nuts on this.. HOPE we have a fix here! :) *BIG SMILE*