> >Yup, you have big DNS problems. There are *no* authoritative name servers
> >for inmrk.com or 231.141.204.in-addr.arpa. With a DNS set that screwed
> >up, I'm not particularly surprised at your observations.
>
> Do you think the lack of reverse DNS explains the slowness in receiving
> pages? I thought it might, but wasn't able to prove it.
It's not necessarily the cause of all your problems, but it's probably
a contributing factor. Every name lookup (forward or reverse) for your
domains is a potential problem. For the reverse lookups, in addition to
none of these name servers being authoritative (these are the delegations
in the root name servers):
231.141.204.in-addr.arpa. 86400 NS ns1.new-york.net.
231.141.204.in-addr.arpa. 86400 NS ns2.new-york.net.
231.141.204.in-addr.arpa. 86400 NS ns3.new-york.net.
there are also a couple of other name servers which show up if you ask
the servers above:
231.141.204.in-addr.arpa. 86400 NS wlv.iipo.gtegsc.com.
231.141.204.in-addr.arpa. 86400 NS tink.com.
Of these, wlv.iipo.gtegsc.com is again not authoritative, and tink.com
evidently doesn't run a name server at all.
If you clean up your DNS configuration (the sooner the better) you have
at least removed *one* problem.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:13 EDT