Can't resolve DNS since 2.1.17

[Werner Koch]

On Mon, 13 Feb 2017 19:09, gabrielfrancosouza at gmail.com said:

>> The correct approach is likely to fix the network configuration causing
>> FORMERR to begin with?
>
> I don't think my ISP will care much (see above). Besides, the old
> behavior worked with this configuration just fine.

The DNS resolver you are using predates SRV records:

19:22:50.674427 IP 192.168.15.20.10218 > 192.168.15.1.domain: 53039+ SRV? _pgpkey-https._tcp.hkps.pool.sks-keyservers.net. (65)
19:22:50.693552 IP 192.168.15.1.domain > 192.168.15.20.10218: 53039 FormErr 0/0/0 (65)

The RFC for SRV records is 17 years old and even not so decent DNS
software supports this.  If it does not it is very likely that the box
has huge numbers of exploitble bugs (think UDP) and an sysadmin should
be able to get access to that forgotten DNS server even without a
password and fix it.  If you have no sysadmin at hand I suggest to take
a sledgehammer and tear down the wall behind you assume 192.168.15.1.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: </pipermail/attachments/20170213/a1dbf07f/attachment.sig>