Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

About a week ago, I updated my DNS, adding:

* CNAME 3600 CNAME 3600

HOST, TYPE, VALUE, MX, TTL MX 10 3600 MX 20 3600 MX 20 3600 MX 30 3600 MX 30 3600 MX 30 3600 MX 30 3600

From before, I had:

HOST, TYPE, VALUE, TTL A 3600 NS 3600 NS 3600 CNAME 3600

Additional details:
The domain is purchased from is used for DNS management.

Now, from home, everything works perfectly, but from the university, neither nor any of the OpenID-related subdomains are working. Instead, an error-message from my webhost (000webhost), is displayed -

I've used OpenDNS's CacheCheck ( to check their cache as I thought this might help me identify the problem. After requesting a refresh (yesterday, and today), all of their caches point correctly to and most of them to the OpenID-related subdomains (which caches are not updated seems to differ for different usernames).

I have a theory that the problems might be related to some caches ignoring the * rule and instead querying the 000webhost Name Servers.

So, my questions are:
1) Have I made any sort of misconfiguration?
2) Since I have an A record pointing to the IP of 000webhost, and I'm not using their subdomain option, can I remove the NS records ( and without causing other kinds of trouble?

Thanks in advance,


PS: I'm quite new to DNS. If I'm using the wrong words to describe something in this text, I'm more than happy for any feedback related to that as well.

share|improve this question
Today, everything seems to work. Are you sure it was not simply the effect of the cache? The old NS records (going to 000webhost) were cached and still used for the duration of the TTL. – bortzmeyer Feb 1 '10 at 15:14

caches ignoring the * rule

That would be a very big brokeness. It is quite unlikely, wildcards exist in the DNS from the beginning.

share|improve this answer

My theory seems to be correct. From the mentioned CacheCheck, after having refreshed the cache, I followed a link named "Check a third-party tool", and here is what I got:

DNS Traversal for

Note how the 000webhost Name Servers respond "[Broken DNS server: Reports that it refuses to respond!]". Yet the main website ( still work.

This means that since I only host the main site at 000webhost, and I have a working A rule, I won't need the two mentioned rules.

PS: I will soon change the OpenID from username.<domain> to<domain> (as I think username.<domain> should be used for other purposes than just OpenID), so if anyone attempts to check it for themselves at a (much) later point, the output that they get from the tool will be different. And, of course, if I am correct in my theory, the problem will soon be resolved, so you won't see the same anyhow.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.