The below is mostly fixed but the register refuses to update the
nameservers since they are the same IP as fnwe.net


On Fri, Jan 17, 2014 at 11:50 AM, Dave Duchscher <da...@tamu.edu> wrote:

> On Jan 17, 2014, at 9:31 AM, Aryeh Friedman <aryeh.fried...@gmail.com>
> wrote:
>
> >> Thanks this confirms an issue someone else reported... will have it
> fixed
> >> in the next few hours.
> >>
> >
> > I think I got it... turns out the records are right but since I used
> lower
> > serial numbers then on older ones it took the older ones only... I have
> > updated the serial to be yyyymmddxx form and this should work now.
> > --
> > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>
> FYI, your registrar name server list is out of sync with your domain.
>
> Whois lists:
>
>   NS1.FNWE.NET
>   NS2.FNWE.NET
>
> You domain now lists:
>
>   cloud.PetiteCloud.org
>
> Also, mixing CNAMES with NS records is not a good idea.
>
>   ns2.fnwe.net.           1787    IN      CNAME   cloud.fnwe.net.
>   cloud.fnwe.net.         1787    IN      A       162.217.113.50
>
>   ns1.fnwe.net.           1454    IN      CNAME   cloud.FNWE.NET.
>   cloud.FNWE.NET.         1774    IN      A       162.217.113.50
>
> --
> DaveD
>
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to