Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've got a VPS, and a domain. The domain was associated with a host/hosting service by a company (provided LAMP) before, when i had enough from them, so i changed the DNS records to my VPS ip adress on the domain admin page of the company.

All works fine now, except if i use the adress with the www subdomain. I added 3 records:

<domainname>.<country> VPS-ip
*.<domainname>.<country> VPS-ip
www.<domainname>.<country> VPS-ip

The first two gets resolved with the right adress, but last one not. Does the www resolved somehow else? Or does it take some time to cascade it top the top?

share|improve this question
3  
Wouldn't *.domainname.country take care of the www entry already? –  Aaron Feb 22 '12 at 0:47
    
@Aaron I don't think that statement should take the form of a question :-) –  Mathias R. Jessen Feb 22 '12 at 0:51
    
If you told us your actual domain name, we could simply make a couple DNS requests and probably tell you what your problem is. Is the anonymization really necessary? –  Zoredache Feb 22 '12 at 0:58
    
It was the TTL/DNS cacheing what i was missing. I gave answer for Mathias because he wrote it first. –  burninggramma Feb 22 '12 at 1:09
add comment

2 Answers 2

up vote 0 down vote accepted

To answer your last question: "Or does it take some time to cascade it top the top?"

Yes (if I've understood your question correctly), if the www subdomain previously existed, you'd have to wait for the record to propagate between the nameservers as well for TTL to expire. Since no other DNS servers could possibly cache ALL records matching *.domain.tld, that one is easier to verify.

For example I doubt mathias-is-an-even-more-beautiful-man.domain.tld has ever been queried, and thus never cached (= no wait for TTL to expire). The www subdomain is more likely to have been queried and cached recently :-)

share|improve this answer
add comment

Your wildcard-entry (*) will match every single request made.

Try looking up pauska-is-a-beautiful-man.domain.tld, you'll be surprised :)

share|improve this answer
    
I was under the impression that a wildcard would only be used if there was not an explicit record for a requested name. –  Zoredache Feb 22 '12 at 0:56
    
Ah, true. Well, the host should resolve either way. –  pauska Feb 22 '12 at 0:57
    
Ye i do know that. Still with the www prefix its resolved for the "old" ip. Is there maybe an upper level witch stores it cached, and need some time to get the new adress? –  burninggramma Feb 22 '12 at 0:58
    
@Zoredache That is true, but in the sense that the explicit www record is needless when it has the same value as any other 1.-level subdomain, pauska is right –  Mathias R. Jessen Feb 22 '12 at 1:00
    
Yes, DNS records are cached according to the TTL setting on either the zone or per record. Have you tried using nslookup directly against the nameserver where your domain is hosted? –  pauska Feb 22 '12 at 1:00
add comment

Your Answer

 
discard

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.