<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML DIR=ltr><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"></HEAD><BODY>
<DIV><FONT face='Arial' color=#000000 >Thank you
Bert,</FONT></DIV>
<DIV><FONT face=Arial> I had never checked into it, My Microsoft DNS server
had been doing this for about 4 years and never complained, it seemed to have
worked well, Unusuall for Microsoft not to follow a standard.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>What recommendations do you have for my situation. I
virtual host most of the websites, and therefore cannot have more than 1 A
record for that IP address, that is why I was using the CNAME. I was trying to
make it so when the user went to xxxxxx.com, without the www, it would resolve
the correct web server.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Barry</FONT></DIV>
<DIV><FONT face=Arial color=#000000></FONT> </DIV>
<DIV><FONT face=Arial color=#000000>On Thu, Jul 08, 2004 at 12:58:47AM -0500,
Barry Bourdage wrote:<BR><BR>><I>
650 361 ovington.com CNAME tp-web1.techpro.com 120<BR></I><BR>Don't do this. You
can never have a CNAME at the same level as the SOA:<BR><BR>><I>
653 361 ovington.com SOA ns1.techpro.com<BR></I>><I> <A
href="http://mailman.powerdns.com/mailman/listinfo/pdns-users">dnsadmin at
techpro.com</A> 20040623 1800 3600 86400 1800 86400 <BR></I><BR>This is not a
PowerDNS thing, but a DNS thing.<BR><BR></DIV></FONT></BODY></HTML>