#weavenetwork

good evening. I am having some routing issues, which I am about to take 20 or 30 minutes to describe and document on a gist page. Hoping folks might take a look when it is ready and advise me how it is I get my dns requests from my container, to name servers which know about the outside world.

gist to the rescue, yet again! three times out of four, describing my issue on gist tends to resolve my issue.

I had been testing my outbound routing with a `ping gp.org`, which works on the docker host, but not inside the container. But I started testing with other targets for the ping, and it seems that I am able to resolve names into IP addresses for a couple of other domains, including my first test of one for which I manage the DNS.

I added my own DNS servers, to the data center's DNS servers which were already in my /et/resolv.conf file on the docker host. Had failed to test my own domain before doing that.

gp.org still comes back empty though, very strange.

but it looks like this is going to be a problem which I will have to resolve sooner or later: github.com

I am unable to resolve github.com

Some of my deployments depend on github.com for their code.

wish I understood better why I am able to resolve some domains but not others.

never mind on that: the docker host whose network is built on the latest version of my reset_network script is able to resolve github.com, but another docker host which was not is unable to resolve that domain. So never mind on that.

seems like something I can resolve.