Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

Alright, hopefully this is a simple one..

We have a new server on our domain CMOT2.ourcompany.local I want to host a few IIS sites on it and refer to them as WIKI.CMOT2.ourcompany.local etc.

I set up the IIS bindings, and also set up DNS CNAME aliases, but it doesn't resolve even after adding aliases I can resolve WIKI.CMOT2 in any way. Just for completeness:

CNAME lives in cmot2 'folder' under ourcompany.local Alias name is 'wiki' FQDN for target host is cmot2.ourcompany.local

-- just noticed that if I nslookup cmot2 or cmot2.lacea.local, I get "non-existent domain". Yet there is an A record for sitting in DNS.... and i am able to nslookup the other A-records..

Oh gods of expert administration, please advise!

share|improve this question
So, you're using nslookup to lookup wiki.cmot2 and it's not resolving? – joeqwerty Jul 12 '11 at 0:19

Within the cmot2 folder you'll want an A record that points the IP address and has no name.

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.