aliased site not resolving but main/real name resolves

pls at post.here pls at post.here
Wed Jun 2 03:02:07 UTC 1999


Hello,

We are having an odd problem with accessing a website.  Regretably it
is uncle Bill's site which recently changed it's main/canonical domain
name from www.microsoft.com to microsoft.com (following on the heels
of freshmeat and slashdot I guess :).  The www.microsoft.com is now an
alias.  The problem is that for some of our nameservers the
www.microsoft.com gives an error and I can't figure out why.  Other
sites (like slashdot and freshmeat) which also have the www.xxx.xx
aliased to their main name resolve fine.  I was told by the user
trying to get to this site that it looks like they changed their DNS
resolution around last friday.  But what about their change is so
unique or non-standard that it would break my nslookups?  I now this
is M$ so the question might be what isn't non-standard but this is
really stumping me so I was hoping someone would see something in
microsoft's DNS that would clue me into what is wrong.

As an aside, short of fixing the resolving problem I was going to
create an alias in my DNS pointing to the CNAME of microsoft.com - is
this an ok/acceptable short term solution for our internal DNS?

thanks for any ideas/tips

Adam

post here so everyone can benefit, but to write me:
r e g n i s a t w o r l d n e t d o t a t t d o t n e t



More information about the bind-users mailing list