Hi everyone,
I am suspicious that it's some recent filter due to last vulnerability of
> bind. It could not be?
I currently have exactly same issue after bind99 update on my DNS platform.
And I don't know why only *.freebsd.org domains seems to be impacted.
Name :
bind99
[26/893]
Vers
On 16/12/2014 02:25, Kevin Oberman wrote:
On Mon, Dec 15, 2014 at 10:02 AM, Marcelo Gondim
mailto:gon...@bsdinfo.com.br>> wrote:
Hi Kevin,
On 13/12/2014 23:44, Kevin Oberman wrote:
On Sat, Dec 13, 2014 at 4:26 AM, Marcelo Gondim
mailto:gon...@bsdinfo.com.br>>
w
On Mon, Dec 15, 2014 at 10:02 AM, Marcelo Gondim
wrote:
> Hi Kevin,
>
> On 13/12/2014 23:44, Kevin Oberman wrote:
>
>> On Sat, Dec 13, 2014 at 4:26 AM, Marcelo Gondim
>> wrote:
>>
>> Dear,
>>>
>>> I'm having trouble resolving domain name freebsd.org. The portsnap
>>> server
>>> works correctly
Hi Kevin,
On 13/12/2014 23:44, Kevin Oberman wrote:
On Sat, Dec 13, 2014 at 4:26 AM, Marcelo Gondim
wrote:
Dear,
I'm having trouble resolving domain name freebsd.org. The portsnap server
works correctly but the pkg audit -F does not work and can not even access
the site according to the foll
On Sat, Dec 13, 2014 at 4:26 AM, Marcelo Gondim
wrote:
> Dear,
>
> I'm having trouble resolving domain name freebsd.org. The portsnap server
> works correctly but the pkg audit -F does not work and can not even access
> the site according to the following tests:
>
> # host ec2-sa-east-1.portsnap.
Dear,
I'm having trouble resolving domain name freebsd.org. The portsnap
server works correctly but the pkg audit -F does not work and can not
even access the site according to the following tests:
# host ec2-sa-east-1.portsnap.freebsd.org
ec2-sa-east-1.portsnap.freebsd.org has address 177.71
: RE: dual dns resolution problem
I tried here bymyself and there are no troubles to connect to my own
server., neither connecting from home - name resolves nicely. And that is
the culprit: 'failure in name resolution'.. means that your name server
cannot resolve name-to-ipaddr.
Resume:
I tried here bymyself and there are no troubles to connect to my own server., neither
connecting from home - name resolves nicely. And that is the culprit: 'failure in name
resolution'.. means that your name server cannot resolve name-to-ipaddr.
Resume: you *must* go back to your named files,
The Problem:
Applications seem unable to resolve dns information.
ssh and sendmail are examples.
Example:
%ssh novell.com
ssh: novell.com: Non-recoverable failure in name resolution
%nslookup novell.com
Server: localhost.inside-polk.skyrunner.net
Address: 127.0.0.1
Name:novell.com
Addre
