pcp
[Top] [All Lists]

Re: [pcp] dns configuration error with pcp.io

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] dns configuration error with pcp.io
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 1 Jun 2016 17:15:37 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <574E9182.9010903@xxxxxxxxxxxxxxxx>
References: <20160531002857.GA15708@xxxxxxxxxx> <574E9182.9010903@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: AFbO5FZauHuJiOdMDzX2+w+DjAH4Uw==
Thread-topic: dns configuration error with pcp.io
Hi Ken,

----- Original Message -----
> On 31/05/16 10:28, Frank Ch. Eigler wrote:
> > Hi -
> > 
> > Formally reporting here, for having done so on IRC appears not enough:
> > 
> > The pcp.io domain is misconfigured.  It both has NS records (with the
> > onlydomains.com registrar (?)), and a CNAME record (pointing to
> > oss.sgi.com).  This is a violation of RFC2181 section 10.1, and makes
> > the domain unresolvable to some name servers.
> > 
> > This could be fixed by changing the CNAME to an A record, or other ways.
> 
> Is anyone attending to this?
> 

Its on the (looong) to-do list.

> I have a new bozo with Ubuntu 16.04 and I'm now seeing on a regular basis ...
> 
> kenj@vm11:~/src/pcp$ git pull
> fatal: Unable to look up pcp.io (port 9418) (Temporary failure in name
> resolution)
> 
> and I presume this is related to Frank's observations.

FWLIW, nothing has changed in pcp.io DNS configuration in well, years.  I'm
guessing something has changed at the ISP end.

> ps bozo has had a bit of a steroids injection ...

This is cos of the way the deb packages auto-enable daemons, it ends up in
this unexpected duplication ... will fix up, thanks.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>