Domain is giving me strange problems with resolving

[noimad1]

I have a domain that I've been using for years, and it's always worked fine until I moved it to a new server a couple months ago. It just stops resolving most of the time, and then occassionally will resolve.

I have a lot of customers around the U.S. complaining they can't resolve to it.

Currently I can't resolve to it myself. Now here is the kicker...when I run a DNS report on the domain it comes back fine.

The domain is secure3.ixsweb.com

Anyone have any ideas on this one? I don't know what else to check...

[noimad1]

Anyone have any ideas on this one?

[Peoplespaces]

There are no nameservers for the subdomain and your main domains nameservers report all sorts of errors.

[logicsupport]

Please check the nameserver entries for the account

[noimad1]

The nameserver records look ok on my end. When I run the report it looks ok:

Free DNS tools, reports and hosting tests, WHOIS, ping, tracerout, spam database lookup. Advanced network and domain name tools.

?

[PlatinumServerM]

Go to intoDNS: ixsweb.com - check DNS server and mail server health
there are several errors there that need to be fixed

[mtindor]

Originally Posted by noimad1

I have a domain that I've been using for years, and it's always worked fine until I moved it to a new server a couple months ago. It just stops resolving most of the time, and then occassionally will resolve.

I have a lot of customers around the U.S. complaining they can't resolve to it.

Currently I can't resolve to it myself. Now here is the kicker...when I run a DNS report on the domain it comes back fine.

The domain is secure3.ixsweb.com

Anyone have any ideas on this one? I don't know what else to check...

WHOIS reports that ixsweb.com nameservers are:

ns1.ixsweb.com
ns3.ixsweb.com
ns5.ixsweb.com

1. ns3.ixsweb.com is currently not responding to queries

2. your zone files only have NS records for:

;; ANSWER SECTION:
ixsweb.com. 86400 IN NS ns3.ixsweb.com.
ixsweb.com. 86400 IN NS ns1.ixsweb.com.

;; ADDITIONAL SECTION:
ns1.ixsweb.com. 14400 IN A 74.55.169.106
ns3.ixsweb.com. 14400 IN A 70.85.253.226


So, you've got a couple of problems just to start.

A. Decide whether or not the third nameserver listed in WHOIS (ns5.isxweb.com) is supposed to be authoritative for the domain.

If it is, then make sure and add an NS record in your zone file for NS5, i.e.:

ixsweb.com. 86400 IN NS ns3.ixsweb.com.
ixsweb.com. 86400 IN NS ns1.ixsweb.com.
ixsweb.com. 86400 IN NS ns5.ixsweb.com.

If you DO NOT want ns5.isxweb.com to be an authoritative nameserver, then remove it as a nameserver at InterxStream (the Enom reseller).

B. Get ns3.ixsweb.com to respond again. Right now, any queries sent to ns3.ixsweb.com are not responded to.


ns5.ixsweb.com is answering authoritatively for ixsweb.com. If that is your intent, then add do what I said in item A.


ns3.ixsweb.com is NOT answering queries. Either do what I listed in item B, or get rid of ns3.isxweb.com in your zone file and remove it as an authoritative nameserver at Enom/InterXStream.

There are other things to do in order to improve the results given at intoDNS. But for now, you need to at least remedy those things above.

Additionally, as somebody else mentioned, if secure3.ixsweb.com is actually set up as a subdomain in Cpanel, you probably should have NS records for it in your main zone. An example would be this:

In the ixsweb.com zone file, you should have:

secure3.ixsweb.com. IN NS xxx.xxx.xxx.xxx
secure3.ixsweb.com. IN NS yyy.yyy.yyy.yyy

- where xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy are the nameservers that your Cpanel server uses. Of course, this would mean that on xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy you should already have a separate zone file in place for secure3.ixsweb.com

Mike