Tha an t-ùghdar air suathadh a-rithist uair is uair mu thràth air diofar thaobhan de ghnìomhachd DNS ann an grunn de fhoillseachadh mar phàirt den bhlog. Aig an aon àm, bha am prìomh chuideam a-riamh air a bhith a’ leasachadh tèarainteachd na prìomh sheirbheis eadar-lìn seo.
Gu ruige o chionn ghoirid, a dh’ aindeoin so-leòntachd follaiseach trafaic DNS, a tha fhathast, sa mhòr-chuid, air a ghluasad gu soilleir, gu gnìomhan droch-rùnach bho sholaraichean a tha ag iarraidh an teachd-a-steach àrdachadh le bhith a’ fighe a-steach sanasachd ann an susbaint, buidhnean tèarainteachd riaghaltais agus caisgireachd, a bharrachd air dìreach eucoirich, am pròiseas , a dh'aindeoin làthaireachd diofar theicneòlasan leithid DNSSEC / DANE, DNScrypt, DNS-over-TLS agus DNS-over-HTTPS, stad. Agus ma tha fuasglaidhean frithealaiche, agus cuid dhiubh air a bhith ann airson ùine mhòr, aithnichte agus rim faighinn gu farsaing, tha an taic bho bhathar-bog teachdaiche a’ fàgail mòran ri bhith air a mhiannachadh.
Gu fortanach, tha an suidheachadh ag atharrachadh. Gu sònraichte, luchd-leasachaidh a’ bhrobhsair Firefox mòr-chòrdte mu phlanaichean gus modh taic a chomasachadh gu bunaiteach (DoH) gu luath. Bu chòir dha seo cuideachadh le bhith a’ dìon trafaic DNS neach-cleachdaidh WWW bho na cunnartan gu h-àrd, ach dh’ fhaodadh e feadhainn ùra a thoirt a-steach.
1. DNS-thar-HTTPS duilgheadasan
Aig a’ chiad sealladh, chan eil toirt a-steach mòr DNS-over-HTTPS a-steach do bhathar-bog eadar-lìn ag adhbhrachadh ach freagairt adhartach. Ach, tha an diabhal, mar a chanas iad, anns na mion-fhiosrachadh.
Is e a’ chiad dhuilgheadas a tha a’ cuingealachadh farsaingeachd cleachdadh farsaing DoH am fòcas a-mhàin air trafaic lìn. Gu dearbh, tha am protocol HTTP agus an dreach làithreach HTTP/2 aige, air a bheil DoH stèidhichte, mar bhunait don WWW. Ach chan e dìreach an lìon a th’ anns an eadar-lìn. Tha mòran de sheirbheisean mòr-chòrdte ann, leithid post-d, grunn theachdairean sa bhad, siostaman gluasad faidhle, sruthadh ioma-mheadhain, msaa, nach eil a’ cleachdadh HTTP. Mar sin, a dh’ aindeoin a’ bheachd a tha aig mòran de DoH mar panacea, tha e a’ tionndadh a-mach nach eil e iomchaidh gun oidhirp a bharrachd (agus neo-riatanach) airson rud sam bith ach teicneòlasan brobhsair. Co-dhiù, tha coltas gu bheil DNS-over-TLS na thagraiche fada nas airidh air an dreuchd seo, a bhios a’ toirt a-steach cuairteachadh trafaic àbhaisteach DNS anns a’ phròtacal TLS àbhaisteach tèarainte.
Is e an dàrna duilgheadas, a dh’ fhaodadh a bhith tòrr nas cudromaiche na a’ chiad fhear, an fhìor thrèigsinn de dhì-mheadhanachadh gnèitheach DNS le dealbhadh airson a bhith a’ cleachdadh aon fhrithealaiche DoH a tha air a shònrachadh ann an roghainnean a’ bhrobhsair. Gu sònraichte, tha Mozilla a’ moladh seirbheis a chleachdadh bho Cloudflare. Chaidh seirbheis den aon seòrsa a chuir air bhog le daoine ainmeil eile air an eadar-lìn, gu sònraichte Google. Tha e a 'tionndadh a-mach gu bheil buileachadh DNS-thar-HTTPS anns an riochd anns a bheil e air a mholadh an-dràsta a-mhàin a' meudachadh eisimeileachd luchd-cleachdaidh deireannach air na seirbheisean as motha. Chan eil e na dhìomhaireachd gum faod am fiosrachadh a bheir mion-sgrùdadh air ceistean DNS seachad eadhon barrachd dàta a chruinneachadh mu dheidhinn, a bharrachd air a bhith cinnteach agus iomchaidh.
A thaobh seo, bha agus tha an t-ùghdar fhathast na neach-taic do bhuileachadh mòr chan ann de DNS-over-HTTPS, ach de DNS-over-TLS còmhla ri DNSSEC / DANE mar dhòigh uile-choitcheann, tèarainte agus gun a bhith cuideachail airson tuilleadh meadhanachadh air an eadar-lìn. gus dèanamh cinnteach à tèarainteachd trafaic DNS. Gu mì-fhortanach, airson adhbharan follaiseach, chan urrainn dhuinn a bhith an dùil gun tèid mòr-thaic a thoirt a-steach do roghainnean DoH gu bathar-bog teachdaiche, agus tha e fhathast na raon de luchd-dealasach teicneòlas tèarainteachd.
Ach leis gu bheil DoH againn a-nis, carson nach cleachd thu e às deidh dhut faighinn seachad air sgrùdadh a dh’ fhaodadh a bhith aig corporaidean tro na frithealaichean aca chun t-seirbheisiche DNS-over-HTTPS againn fhèin?
2. DNS-thar-HTTPS pròtacal
Ma choimheadas tu air an ìre àbhaisteach a’ toirt cunntas air a’ phròtacal DNS-over-HTTPS, chì thu gur e, gu dearbh, API lìn a leigeas leat pasgan DNS àbhaisteach a chuartachadh anns a’ phròtacal HTTP/2. Tha seo air a chuir an gnìomh tro chinn-cinn HTTP sònraichte, a bharrachd air tionndadh de chruth dà-chànanach de dhàta DNS tar-chuir (faic. agus sgrìobhainnean às deidh sin) ann an cruth a leigeas leat an sgaoileadh agus fhaighinn, a bharrachd air a bhith ag obair leis na meata-dàta riatanach.
A rèir na h-ìre, chan eil ach HTTP/2 agus ceangal TLS tèarainte a’ faighinn taic.
Faodar iarrtas DNS a chuir a-steach a’ cleachdadh na modhan àbhaisteach GET agus POST. Anns a 'chiad chùis, tha an t-iarrtas air a thionndadh gu sreang le còd base64URL, agus anns an dàrna fear, tro chorp an iarrtais POST ann an cruth binary. Anns a 'chùis seo, thèid seòrsa sònraichte de dhàta MIME a chleachdadh rè iarrtas DNS agus freagairt tagradh/dns-teachdaireachd.
root@eprove:~ # curl -H 'accept: application/dns-message' 'https://my.domaint/dns-query?dns=q80BAAABAAAAAAAAB2V4YW1wbGUDY29tAAABAAE' -v
* Trying 2001:100:200:300::400:443...
* TCP_NODELAY set
* Connected to eprove.net (2001:100:200:300::400) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /usr/local/share/certs/ca-root-nss.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=my.domain
* start date: Jul 22 00:07:13 2019 GMT
* expire date: Oct 20 00:07:13 2019 GMT
* subjectAltName: host "my.domain" matched cert's "my.domain"
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x801441000)
> GET /dns-query?dns=q80BAAABAAAAAAAAB2V4YW1wbGUDY29tAAABAAE HTTP/2
> Host: eprove.net
> User-Agent: curl/7.65.3
> accept: application/dns-message
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 200
< server: h2o/2.3.0-beta2
< content-type: application/dns-message
< cache-control: max-age=86274
< date: Thu, 12 Sep 2019 13:07:25 GMT
< strict-transport-security: max-age=15768000; includeSubDomains; preload
< content-length: 45
<
Warning: Binary output can mess up your terminal. Use "--output -" to tell
Warning: curl to output it to your terminal anyway, or consider "--output
Warning: <FILE>" to save to a file.
* Failed writing body (0 != 45)
* stopped the pause stream!
* Connection #0 to host eprove.net left intactCuideachd aire a thoirt don tiotal smachd tasgadan: anns an fhreagairt bhon fhrithealaiche lìn. Anns a 'pharamadair aois as motha anns a bheil an luach TTL airson a’ chlàr DNS air a thilleadh (no an luach as ìsle ma tha seata dhiubh ga thilleadh).
Stèidhichte air na tha gu h-àrd, tha grunn ìrean ann an obrachadh frithealaiche DoH.
- Faigh iarrtas HTTP. Mas e GET a tha seo, dì-chòdaich a’ phacaid bho chòdachadh base64URL.
- Cuir am pasgan seo chun an fhrithealaiche DNS.
- Faigh freagairt bhon fhrithealaiche DNS
- Lorg an luach TTL as ìsle anns na clàran a fhuaireadh.
- Till freagairt don neach-dèiligidh tro HTTP.
3. Am frithealaiche DNS-thar-HTTPS agad fhèin
Is e an dòigh as sìmplidh, as luaithe agus as èifeachdaiche air an t-seirbheisiche DNS-over-HTTPS agad fhèin a ruith a bhith a’ cleachdadh frithealaiche lìn HTTP/2 , air a bheil an t-ùghdar air sgrìobhadh goirid mu thràth (faic “").
Tha an roghainn seo a’ faighinn taic bhon fhìrinn gum faodar còd an t-seirbheisiche DoH agad fhèin a chuir an gnìomh gu h-iomlan a’ cleachdadh an eadar-theangair amalaichte ann an H2O fhèin . A bharrachd air na leabharlannan àbhaisteach, gus dàta iomlaid leis an t-seirbheisiche DNS, feumaidh tu an leabharlann Socket (mrbgem), a tha, gu fortanach, mar-thà air a ghabhail a-steach san dreach leasachaidh gnàthach de H2O 2.3.0-beta2 ann am puirt FreeBSD. Ach, chan eil e duilich a chuir ri dreach sam bith roimhe le bhith a’ clonadh an stòr dhan chatalog /deps mus deach a chruinneachadh.
root@beta:~ # uname -v
FreeBSD 12.0-RELEASE-p10 GENERIC
root@beta:~ # cd /usr/ports/www/h2o
root@beta:/usr/ports/www/h2o # make extract
===> License MIT BSD2CLAUSE accepted by the user
===> h2o-2.2.6 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by h2o-2.2.6 for building
===> Extracting for h2o-2.2.6.
=> SHA256 Checksum OK for h2o-h2o-v2.2.6_GH0.tar.gz.
===> h2o-2.2.6 depends on file: /usr/local/bin/ruby26 - found
root@beta:/usr/ports/www/h2o # cd work/h2o-2.2.6/deps/
root@beta:/usr/ports/www/h2o/work/h2o-2.2.6/deps # git clone https://github.com/iij/mruby-socket.git
Клонирование в «mruby-socket»…
remote: Enumerating objects: 385, done.
remote: Total 385 (delta 0), reused 0 (delta 0), pack-reused 385
Получение объектов: 100% (385/385), 98.02 KiB | 647.00 KiB/s, готово.
Определение изменений: 100% (208/208), готово.
root@beta:/usr/ports/www/h2o/work/h2o-2.2.6/deps # ll
total 181
drwxr-xr-x 9 root wheel 18 12 авг. 16:09 brotli/
drwxr-xr-x 2 root wheel 4 12 авг. 16:09 cloexec/
drwxr-xr-x 2 root wheel 5 12 авг. 16:09 golombset/
drwxr-xr-x 4 root wheel 35 12 авг. 16:09 klib/
drwxr-xr-x 2 root wheel 5 12 авг. 16:09 libgkc/
drwxr-xr-x 4 root wheel 26 12 авг. 16:09 libyrmcds/
drwxr-xr-x 13 root wheel 32 12 авг. 16:09 mruby/
drwxr-xr-x 5 root wheel 11 12 авг. 16:09 mruby-digest/
drwxr-xr-x 5 root wheel 10 12 авг. 16:09 mruby-dir/
drwxr-xr-x 5 root wheel 10 12 авг. 16:09 mruby-env/
drwxr-xr-x 4 root wheel 9 12 авг. 16:09 mruby-errno/
drwxr-xr-x 5 root wheel 14 12 авг. 16:09 mruby-file-stat/
drwxr-xr-x 5 root wheel 10 12 авг. 16:09 mruby-iijson/
drwxr-xr-x 5 root wheel 11 12 авг. 16:09 mruby-input-stream/
drwxr-xr-x 6 root wheel 11 12 авг. 16:09 mruby-io/
drwxr-xr-x 5 root wheel 10 12 авг. 16:09 mruby-onig-regexp/
drwxr-xr-x 4 root wheel 10 12 авг. 16:09 mruby-pack/
drwxr-xr-x 5 root wheel 10 12 авг. 16:09 mruby-require/
drwxr-xr-x 6 root wheel 10 12 сент. 16:10 mruby-socket/
drwxr-xr-x 2 root wheel 9 12 авг. 16:09 neverbleed/
drwxr-xr-x 2 root wheel 13 12 авг. 16:09 picohttpparser/
drwxr-xr-x 2 root wheel 4 12 авг. 16:09 picotest/
drwxr-xr-x 9 root wheel 16 12 авг. 16:09 picotls/
drwxr-xr-x 4 root wheel 8 12 авг. 16:09 ssl-conservatory/
drwxr-xr-x 8 root wheel 18 12 авг. 16:09 yaml/
drwxr-xr-x 2 root wheel 8 12 авг. 16:09 yoml/
root@beta:/usr/ports/www/h2o/work/h2o-2.2.6/deps # cd ../../..
root@beta:/usr/ports/www/h2o # make install clean
...Tha rèiteachadh an fhrithealaiche lìn àbhaisteach san fharsaingeachd.
root@beta:/usr/ports/www/h2o # cd /usr/local/etc/h2o/
root@beta:/usr/local/etc/h2o # cat h2o.conf
# this sample config gives you a feel for how h2o can be used
# and a high-security configuration for TLS and HTTP headers
# see https://h2o.examp1e.net/ for detailed documentation
# and h2o --help for command-line options and settings
# v.20180207 (c)2018 by Max Kostikov http://kostikov.co e-mail: [email protected]
user: www
pid-file: /var/run/h2o.pid
access-log:
path: /var/log/h2o/h2o-access.log
format: "%h %v %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i""
error-log: /var/log/h2o/h2o-error.log
expires: off
compress: on
file.dirlisting: off
file.send-compressed: on
file.index: [ 'index.html', 'index.php' ]
listen:
port: 80
listen:
port: 443
ssl:
cipher-suite: ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS
cipher-preference: server
dh-file: /etc/ssl/dhparams.pem
certificate-file: /usr/local/etc/letsencrypt/live/eprove.net/fullchain.pem
key-file: /usr/local/etc/letsencrypt/live/my.domain/privkey.pem
hosts:
"*.my.domain":
paths: &go_tls
"/":
redirect:
status: 301
url: https://my.domain/
"my.domain:80":
paths: *go_tls
"my.domain:443":
header.add: "Strict-Transport-Security: max-age=15768000; includeSubDomains; preload"
paths:
"/dns-query":
mruby.handler-file: /usr/local/etc/h2o/h2odoh.rbIs e an aon eisgeachd an làimhseachadh URL /dns-ceist airson a bheil ar frithealaiche DNS-over-HTTPS, sgrìobhte ann am mruby agus air a ghairm tron roghainn làimhseachaidh, gu dearbh an urra mruby.handler-faidhle.
root@beta:/usr/local/etc/h2o # cat h2odoh.rb
# H2O HTTP/2 web server as DNS-over-HTTP service
# v.20190908 (c)2018-2019 Max Kostikov https://kostikov.co e-mail: [email protected]
proc {|env|
if env['HTTP_ACCEPT'] == "application/dns-message"
case env['REQUEST_METHOD']
when "GET"
req = env['QUERY_STRING'].gsub(/^dns=/,'')
# base64URL decode
req = req.tr("-_", "+/")
if !req.end_with?("=") && req.length % 4 != 0
req = req.ljust((req.length + 3) & ~3, "=")
end
req = req.unpack1("m")
when "POST"
req = env['rack.input'].read
else
req = ""
end
if req.empty?
[400, { 'content-type' => 'text/plain' }, [ "Bad Request" ]]
else
# --- ask DNS server
sock = UDPSocket.new
sock.connect("localhost", 53)
sock.send(req, 0)
str = sock.recv(4096)
sock.close
# --- find lowest TTL in response
nans = str[6, 2].unpack1('n') # number of answers
if nans > 0 # no DNS failure
shift = 12
ttl = 0
while nans > 0
# process domain name compression
if str[shift].unpack1("C") < 192
shift = str.index("x00", shift) + 5
if ttl == 0 # skip question section
next
end
end
shift += 6
curttl = str[shift, 4].unpack1('N')
shift += str[shift + 4, 2].unpack1('n') + 6 # responce data size
if ttl == 0 or ttl > curttl
ttl = curttl
end
nans -= 1
end
cc = 'max-age=' + ttl.to_s
else
cc = 'no-cache'
end
[200, { 'content-type' => 'application/dns-message', 'content-length' => str.size, 'cache-control' => cc }, [ str ] ]
end
else
[415, { 'content-type' => 'text/plain' }, [ "Unsupported Media Type" ]]
end
}Thoir an aire gu bheil an t-seirbheisiche tasgadan ionadail an urra ri bhith a’ làimhseachadh phasgan DNS, sa chùis seo bhon sgaoileadh àbhaisteach FreeBSD. Bho thaobh tèarainteachd, is e seo am fuasgladh as fheàrr. Ach, chan eil dad a 'cur bacadh ort bho bhith a' cur an àite localhost gu seòladh DNS eile a tha thu an dùil a chleachdadh.
root@beta:/usr/local/etc/h2o # local-unbound verison
usage: local-unbound [options]
start unbound daemon DNS resolver.
-h this help
-c file config file to read instead of /var/unbound/unbound.conf
file format is described in unbound.conf(5).
-d do not fork into the background.
-p do not create a pidfile.
-v verbose (more times to increase verbosity)
Version 1.8.1
linked libs: mini-event internal (it uses select), OpenSSL 1.1.1a-freebsd 20 Nov 2018
linked modules: dns64 respip validator iterator
BSD licensed, see LICENSE in source package for details.
Report bugs to [email protected]
root@eprove:/usr/local/etc/h2o # sockstat -46 | grep unbound
unbound local-unbo 69749 3 udp6 ::1:53 *:*
unbound local-unbo 69749 4 tcp6 ::1:53 *:*
unbound local-unbo 69749 5 udp4 127.0.0.1:53 *:*
unbound local-unbo 69749 6 tcp4 127.0.0.1:53 *:*Chan eil air fhàgail ach H2O ath-thòiseachadh agus faicinn dè a thig às.
root@beta:/usr/local/etc/h2o # service h2o restart
Stopping h2o.
Waiting for PIDS: 69871.
Starting h2o.
start_server (pid:70532) starting now...4. Deuchainn
Mar sin, leig dhuinn sùil a thoirt air na toraidhean le bhith a’ cur iarrtas deuchainn a-rithist agus a’ coimhead air trafaic lìonraidh a’ cleachdadh a’ ghoireas tcpdump.
root@beta/usr/local/etc/h2o # curl -H 'accept: application/dns-message' 'https://my.domain/dns-query?dns=q80BAAABAAAAAAAAB2V4YW1wbGUDY29tAAABAAE'
Warning: Binary output can mess up your terminal. Use "--output -" to tell
Warning: curl to output it to your terminal anyway, or consider "--output
Warning: <FILE>" to save to a file.
...
root@beta:~ # tcpdump -n -i lo0 udp port 53 -xx -XX -vv
tcpdump: listening on lo0, link-type NULL (BSD loopback), capture size 262144 bytes
16:32:40.420831 IP (tos 0x0, ttl 64, id 37575, offset 0, flags [none], proto UDP (17), length 57, bad cksum 0 (->e9ea)!)
127.0.0.1.21070 > 127.0.0.1.53: [bad udp cksum 0xfe38 -> 0x33e3!] 43981+ A? example.com. (29)
0x0000: 0200 0000 4500 0039 92c7 0000 4011 0000 ....E..9....@...
0x0010: 7f00 0001 7f00 0001 524e 0035 0025 fe38 ........RN.5.%.8
0x0020: abcd 0100 0001 0000 0000 0000 0765 7861 .............exa
0x0030: 6d70 6c65 0363 6f6d 0000 0100 01 mple.com.....
16:32:40.796507 IP (tos 0x0, ttl 64, id 37590, offset 0, flags [none], proto UDP (17), length 73, bad cksum 0 (->e9cb)!)
127.0.0.1.53 > 127.0.0.1.21070: [bad udp cksum 0xfe48 -> 0x43fa!] 43981 q: A? example.com. 1/0/0 example.com. A 93.184.216.34 (45)
0x0000: 0200 0000 4500 0049 92d6 0000 4011 0000 ....E..I....@...
0x0010: 7f00 0001 7f00 0001 0035 524e 0035 fe48 .........5RN.5.H
0x0020: abcd 8180 0001 0001 0000 0000 0765 7861 .............exa
0x0030: 6d70 6c65 0363 6f6d 0000 0100 01c0 0c00 mple.com........
0x0040: 0100 0100 0151 8000 045d b8d8 22 .....Q...].."
^C
2 packets captured
23 packets received by filter
0 packets dropped by kernelTha an toradh a 'sealltainn mar a tha an t-iarrtas airson an seòladh fhuasgladh example.com air fhaighinn agus air a phròiseasadh gu soirbheachail leis an t-seirbheisiche DNS.
A-nis chan eil air fhàgail ach ar frithealaiche a chuir an gnìomh ann am brabhsair Firefox. Gus seo a dhèanamh, feumaidh tu grunn shuidheachaidhean atharrachadh air na duilleagan rèiteachaidh mu dheidhinn: cumadh.
An toiseach, is e seo seòladh an API againn far am bi am brabhsair ag iarraidh fiosrachadh DNS a-steach lìonra.trr.uri. Thathas cuideachd a’ moladh an àrainn IP bhon URL seo a shònrachadh airson rùn IP tèarainte a’ cleachdadh a’ bhrobhsair fhèin gun a bhith a’ faighinn cothrom air DNS a-steach network.trr.bootstrapAddress. Agus mu dheireadh, am paramadair fhèin lìonra.trr.modh gabhail a-steach cleachdadh DoH. Le bhith a’ suidheachadh an luach gu “3” bheir sin air a’ bhrobhsair DNS-over-HTTPS a-mhàin a chleachdadh airson fuasgladh ainm, agus bheir an “2” nas earbsaiche agus nas tèarainte prìomhachas do DoH, a’ fàgail an lorg DNS àbhaisteach mar roghainn air ais.
5. PROFIT!
An robh an artaigil cuideachail? An uairsin feuch nach bi thu diùid agus cuir taic ri airgead tron fhoirm tabhartais (gu h-ìosal).
Source: www.habr.com