Dnspref - Revision history

Onnowpurbo: /* Running the tests */

2015-08-15T22:16:06Z

Running the tests

← Older revision		Revision as of 22:16, 15 August 2015
Line 59:		Line 59:
	==Running the tests==		==Running the tests==

	~~When running~~ dnsperf, a data ~~file~~ (~~the~~ -d ~~option~~) ~~and~~ server (~~the~~ -s ~~option~~) ~~will normally be specified~~. ~~The output of~~ dnsperf ~~is mostly self-explanatory~~. ~~Pay attention to the number of dropped packets reported~~ - ~~when running the test over a local~~ Ethernet ~~connection~~, ~~it should be zero~~. ~~If one or more packets has been dropped~~, ~~there may be a problem with the network connection~~. ~~In that case~~, ~~the results should be considered suspect and the test repeated~~.		Saat menjalankan dnsperf, file data (pilihan -d) dan server (option -s) biasanya akan ditentukan. Output dari dnsperf sebagian besar cukup jelas. Perhatikan jumlah paket yang di drop - ketika menjalankan tes melalui koneksi Ethernet lokal, itu harus nol. Jika satu atau lebih paket telah drop, mungkin ada masalah dengan koneksi jaringan. Dalam hal ini, hasil harus dicurigai dan lakukan tes ulang.

	~~Options~~

			Options

	-a local_addr		-a local_addr
	Specifies the local address from which to send requests. The default is the wildcard address.		Specifies the local address from which to send requests. The default is the wildcard address.

Onnowpurbo at 22:12, 15 August 2015

2015-08-15T22:12:42Z

← Older revision		Revision as of 22:12, 15 August 2015
Line 63:		Line 63:
	Options		Options

	-a local_addr		-a local_addr

	Specifies the local address from which to send requests. The default is the wildcard address.		Specifies the local address from which to send requests. The default is the wildcard address.
	-b bufsize		-b bufsize
	Sets the size of the socket's send and receive buffers, in kilobytes. If not specified, the operating system's default is used.		Sets the size of the socket's send and receive buffers, in kilobytes.
	-c clients		If not specified, the operating system's default is used.
			-c clients
	Act as multiple clients. Requests are sent from multiple sockets. The default is to act as 1 client.		Act as multiple clients. Requests are sent from multiple sockets. The default is to act as 1 client.
	-d datafile		-d datafile
	Specifies the input data file. If not specified, dnsperf will read from standard input.		Specifies the input data file. If not specified, dnsperf will read from standard input.
	-D		-D
	Sets the DO (DNSSEC OK) bit [RFC3225] in all packets sent. This also enables EDNS0, which is required for DNSSEC.		Sets the DO (DNSSEC OK) bit [RFC3225] in all packets sent. This also enables EDNS0, which is required for DNSSEC.
	-e		-e
	Enables EDNS0 [RFC2671], by adding an OPT record to all packets sent.		Enables EDNS0 [RFC2671], by adding an OPT record to all packets sent.
	-f family		-f family
	Specifies the address family used for sending DNS packets. The possible values are "inet", "inet6", or "any". If "any" (the default value) is specified, dnsperf will use whichever address family is appropriate for the server it is sending packets to.		Specifies the address family used for sending DNS packets. The possible values are "inet", "inet6", or "any".
	-h		If "any" (the default value) is specified, dnsperf will use whichever address family is
			appropriate for the server it is sending packets to.
			-h
	Print a usage statement and exit.		Print a usage statement and exit.
	-l limit		-l limit
	Specifies a time limit for the run, in seconds. This may cause the input to be read multiple times, or only some of the input to be read. The default behavior is to read the input once, and have no specific time limit.		Specifies a time limit for the run, in seconds. This may cause the input to be read multiple times,
	-n runs_through_file		or only some of the input to be read. The default behavior is to read the input once, and have no specific time limit.
	Run through the input file at most this many times. If no time limit is set, the file will be read exactly this number of times; if a time limit is set, the file may be read fewer times.		-n runs_through_file
	-p port		Run through the input file at most this many times. If no time limit is set, the file will be read
			exactly this number of times; if a time limit is set, the file may be read fewer times.
			-p port
	Sets the port on which the DNS packets are sent. If not specified, the standard DNS port (53) is used.		Sets the port on which the DNS packets are sent. If not specified, the standard DNS port (53) is used.
	-q num_queries		-q num_queries
	Sets the maximum number of outstanding requests. When this value is reached, dnsperf will not send any more requests until either responses are received or requests time out. The default value is 100.		Sets the maximum number of outstanding requests. When this value is reached, dnsperf will not send any
	-Q max_qps		more requests until either responses are received or requests time out. The default value is 100.
			-Q max_qps
	Limits the number of requests per second. There is no default limit.		Limits the number of requests per second. There is no default limit.
	-s server_addr		-s server_addr
	Specifies the name or address of the server to which requests will be sent. The default is the loopback address, 127.0.0.1.		Specifies the name or address of the server to which requests will be sent. The default is the loopback address, 127.0.0.1.
	-S stats_interval		-S stats_interval
	If this parameter is specified, a count of the number of queries per second during the interval will be printed out every stats_interval seconds.		If this parameter is specified, a count of the number of queries per second during the interval will be printed out every stats_interval seconds.
	-t timeout		-t timeout
	Specifies the request timeout value, in seconds. dnsperf will no longer wait for a response to a particular request after this many seconds have elapsed. The default is 5 seconds.		Specifies the request timeout value, in seconds. dnsperf will no longer wait for a response to a particular
	-u		request after this many seconds have elapsed. The default is 5 seconds.
	Instructs dnsperf to send DNS dynamic update messages, rather than queries. The format of the input file is different in this case; see the "Constructing a dynamic update input file" section for more details.		-u
	-v		Instructs dnsperf to send DNS dynamic update messages, rather than queries.
	Enables verbose mode. The DNS RCODE of each response will be reported to standard output when the response is received, as will the latency. If a query times out, it will be reported with the special string "T" instead of a normal DNS RCODE. If a query is interrupted, it will be reported with the special string "I".		The format of the input file is different in this case; see the "Constructing a dynamic update input file" section for more details.
	-x local_port		-v
			Enables verbose mode. The DNS RCODE of each response will be reported to standard output
			when the response is received, as will the latency. If a query times out, it will be reported
			with the special string "T" instead of a normal DNS RCODE. If a query is interrupted, it will be reported with the special string "I".
			-x local_port
	Specifies the local port from which to send requests. The default is the wildcard port (0).		Specifies the local port from which to send requests. The default is the wildcard port (0).

	If acting as multiple clients and the wildcard port is used, each client will use a different random port. If a port is specified, the clients will use a range of ports starting with the specified one.		If acting as multiple clients and the wildcard port is used, each client will use a different random port.
	-y [alg:]name:secret		If a port is specified, the clients will use a range of ports starting with the specified one.
	Add a TSIG record [RFC2845] to all packets sent, using the specified TSIG key algorithm, name and secret, where the algorithm defaults to hmac-md5 and the secret is expressed as a base-64 encoded string.		-y [alg:]name:secret
			Add a TSIG record [RFC2845] to all packets sent, using the specified TSIG key algorithm,
			name and secret, where the algorithm defaults to hmac-md5 and the secret is expressed as a base-64 encoded string.

	==Lebih Lanjut==		==Lebih Lanjut==

Onnowpurbo: /* Membangun Input File yang Update Secara Dinamik */

2015-07-22T07:12:58Z

Membangun Input File yang Update Secara Dinamik

← Older revision		Revision as of 07:12, 22 July 2015
Line 45:		Line 45:
	prohibit x A		prohibit x A

	~~Subsequent lines contain records to be added~~, ~~records to be deleted~~, ~~rrsets to be deleted~~, ~~or names to be deleted~~. ~~The keywords~~ "add" or "delete" ~~are followed by the appropriate information~~. ~~All relative names are considered to be relative to the~~ zone name. ~~The following lines show the~~ 4 ~~types of updates~~.
			Kalimat selanjutnya berisi record yang perlu di tambahkan, record yang perlu di delete, rrset yang perlu di delete, atau nama yang perlu di delete. Keyword "add" atau "delete" di ikuti dengan informasi yang benar. Semua nama relatif terhadap zone name. Kalimat berikut memperlihatkan 4 type dari update.

	add x 3600 A 10.1.2.3		add x 3600 A 10.1.2.3
Line 52:		Line 53:
	delete w		delete w

	~~Each~~ update message ~~is terminated by a line containing the command~~:		Setiap update message di akhiri dengan sebuah kalimat berisi perintah:

	send		send

Onnowpurbo: /* Membangun Input File yang Update Secara Dinamik */

2015-07-22T07:04:42Z

Membangun Input File yang Update Secara Dinamik

← Older revision		Revision as of 07:04, 22 July 2015
Line 33:		Line 33:
	==Membangun Input File yang Update Secara Dinamik==		==Membangun Input File yang Update Secara Dinamik==

	To test dynamic update performance, dnsperf ~~is run with the~~ -u ~~option~~, ~~and the~~ input ~~file is constructed of blocks of lines describing~~ dynamic update ~~messages~~. ~~The first line in a block contains the~~ zone ~~name~~:		Untuk men-test dynamic update performance, dnsperf dijalankan dengan opsi -u, dan file input di bangun dari blok kalimat yang menjelaskan dynamic update message. Kalimat pertama di blok berisi nama zone, misalnya:

	example.com		example.com

	~~Subsequent lines contain prerequisites~~, ~~if there are any~~. ~~Prerequisites can specify that a name may or may not exist~~, an rrset ~~may or may not exist~~, ~~or an~~ rrset ~~exists and its~~ rdata ~~matches all specified~~ rdata ~~for that~~ name ~~and~~ type. ~~The keywords~~ "require" ~~and~~ "prohibit" ~~are followed by the appropriate information~~. ~~All relative names are considered to be relative to the~~ zone name. ~~The following lines show the~~ 5 ~~types of prerequisites.~~		Kalimat selanjutnya berisi persyaratan, jika ada. Persyaratan dapat diberikan pada sebuah nama yang mungkin ada atau tidak ada, sebuah rrset mungkin ada atau tidak ada, atau jika ada rrset dan rdata-nya match ke semua rdata yang di spesifikasikan untuk name dan type. Keyword "require" dan "prohibit" di ikuti oleh informasi yang sesuai. Semua name relatif terhadap zone name. Kalimat berikut memperlihatkan 5 type persyaratan

	require a		require a

Onnowpurbo: /* Constructing a dynamic update input file */

2015-07-21T23:27:34Z

Constructing a dynamic update input file

← Older revision		Revision as of 23:27, 21 July 2015
Line 31:		Line 31:
	di mana "www" awalan memastikan bahwa server akan merespon dengan rujukan. Idealnya, proporsi realistis query untuk domain tidak ada harus dicampur dengan yang sudah ada, dan baris dari file input harus acak.		di mana "www" awalan memastikan bahwa server akan merespon dengan rujukan. Idealnya, proporsi realistis query untuk domain tidak ada harus dicampur dengan yang sudah ada, dan baris dari file input harus acak.

	==~~Constructing a dynamic update input file~~==		==Membangun Input File yang Update Secara Dinamik==

	To test dynamic update performance, dnsperf is run with the -u option, and the input file is constructed of blocks of lines describing dynamic update messages. The first line in a block contains the zone name:		To test dynamic update performance, dnsperf is run with the -u option, and the input file is constructed of blocks of lines describing dynamic update messages. The first line in a block contains the zone name:

Onnowpurbo: /* Membuat input file query */

2015-07-21T23:26:24Z

Membuat input file query

← Older revision		Revision as of 23:26, 21 July 2015
Line 24:		Line 24:
	Sebuah file input dnsperf harus berisi satu set query yang besar dan realistik, dalam jumlah sepuluh ribu sampai jutaan. File input berisi satu baris per query, yang terdiri dari nama domain dan nama tipe RR dipisahkan oleh spasi. Kelas query secara implisit IN.		Sebuah file input dnsperf harus berisi satu set query yang besar dan realistik, dalam jumlah sepuluh ribu sampai jutaan. File input berisi satu baris per query, yang terdiri dari nama domain dan nama tipe RR dipisahkan oleh spasi. Kelas query secara implisit IN.

	~~When measuring the performance serving~~ non-terminal ~~zones such as the~~ root ~~zone or TLDs~~, ~~note that such servers spend most of their time providing referral responses~~, ~~not authoritative answers~~. ~~Therefore~~, ~~a realistic input~~ file ~~might consist mostly of queries for type~~ A ~~for names~~ ~~below~~, ~~not at~~, ~~the delegations present in the zone~~. ~~For example~~, ~~when testing the performance of a~~ server ~~configured to be authoritative for the~~ top-level domain "fi.", ~~which contains delegations for domains like~~ "helsinki.fi" ~~and~~ "turku.fi", ~~the input~~ file ~~could contain lines like~~		Ketika mengukur kinerja melayani zona non-terminal seperti zona root atau TLD, diketahui bahwa server tersebut menghabiskan sebagian besar waktu mereka memberikan tanggapan rujukan, jawaban non authoritive. Oleh karena itu, file masukan yang realistis mungkin kebanyakan terdiri dari permintaan untuk tipe A untuk nama tertentu, tidak pada, kehadiran delegasi dalam zona. Misalnya, ketika menguji kinerja server dikonfigurasi untuk menjadi otoritatif untuk top-level domain "fi.", Yang berisi delegasi untuk domain seperti "helsinki.fi" dan "turku.fi", masukan file yang bisa berisi baris seperti

	www.turku.fi A		www.turku.fi A
	www.helsinki.fi A		www.helsinki.fi A

	~~where the~~ "www" ~~prefix ensures that the~~ server ~~will respond with a referral~~. ~~Ideally~~, ~~a realistic proportion of queries for nonexistent domains should be mixed in with those for existing ones~~, ~~and the lines of the~~ input ~~file should be in a random order~~.		di mana "www" awalan memastikan bahwa server akan merespon dengan rujukan. Idealnya, proporsi realistis query untuk domain tidak ada harus dicampur dengan yang sudah ada, dan baris dari file input harus acak.

	==Constructing a dynamic update input file==		==Constructing a dynamic update input file==

Onnowpurbo: /* Membuat input file query */

2015-07-21T23:21:31Z

Membuat input file query

← Older revision		Revision as of 23:21, 21 July 2015
Line 22:		Line 22:
	==Membuat input file query==		==Membuat input file query==

	A dnsperf ~~input file should contain a large and realistic~~ set ~~of queries~~, ~~on the order of ten thousand to a million~~. ~~The~~ input ~~file contains one line~~ per query, ~~consisting of a~~ domain ~~name and an~~ RR ~~type name separated by a space~~. ~~The class of the~~ query ~~is implicitly~~ IN.		Sebuah file input dnsperf harus berisi satu set query yang besar dan realistik, dalam jumlah sepuluh ribu sampai jutaan. File input berisi satu baris per query, yang terdiri dari nama domain dan nama tipe RR dipisahkan oleh spasi. Kelas query secara implisit IN.

	When measuring the performance serving non-terminal zones such as the root zone or TLDs, note that such servers spend most of their time providing referral responses, not authoritative answers. Therefore, a realistic input file might consist mostly of queries for type A for names below, not at, the delegations present in the zone. For example, when testing the performance of a server configured to be authoritative for the top-level domain "fi.", which contains delegations for domains like "helsinki.fi" and "turku.fi", the input file could contain lines like		When measuring the performance serving non-terminal zones such as the root zone or TLDs, note that such servers spend most of their time providing referral responses, not authoritative answers. Therefore, a realistic input file might consist mostly of queries for type A for names below, not at, the delegations present in the zone. For example, when testing the performance of a server configured to be authoritative for the top-level domain "fi.", which contains delegations for domains like "helsinki.fi" and "turku.fi", the input file could contain lines like
Line 31:		Line 31:
	where the "www" prefix ensures that the server will respond with a referral. Ideally, a realistic proportion of queries for nonexistent domains should be mixed in with those for existing ones, and the lines of the input file should be in a random order.		where the "www" prefix ensures that the server will respond with a referral. Ideally, a realistic proportion of queries for nonexistent domains should be mixed in with those for existing ones, and the lines of the input file should be in a random order.

	Constructing a dynamic update input file		==Constructing a dynamic update input file==

	To test dynamic update performance, dnsperf is run with the -u option, and the input file is constructed of blocks of lines describing dynamic update messages. The first line in a block contains the zone name:		To test dynamic update performance, dnsperf is run with the -u option, and the input file is constructed of blocks of lines describing dynamic update messages. The first line in a block contains the zone name:
Line 56:		Line 56:
	send		send

	Running the tests		==Running the tests==

	When running dnsperf, a data file (the -d option) and server (the -s option) will normally be specified. The output of dnsperf is mostly self-explanatory. Pay attention to the number of dropped packets reported - when running the test over a local Ethernet connection, it should be zero. If one or more packets has been dropped, there may be a problem with the network connection. In that case, the results should be considered suspect and the test repeated.		When running dnsperf, a data file (the -d option) and server (the -s option) will normally be specified. The output of dnsperf is mostly self-explanatory. Pay attention to the number of dropped packets reported - when running the test over a local Ethernet connection, it should be zero. If one or more packets has been dropped, there may be a problem with the network connection. In that case, the results should be considered suspect and the test repeated.
Line 104:		Line 104:
	If acting as multiple clients and the wildcard port is used, each client will use a different random port. If a port is specified, the clients will use a range of ports starting with the specified one.		If acting as multiple clients and the wildcard port is used, each client will use a different random port. If a port is specified, the clients will use a range of ports starting with the specified one.
	-y [alg:]name:secret		-y [alg:]name:secret
	Add a TSIG record [RFC2845] to all packets sent, using the specified TSIG key algorithm, name and secret, where the algorithm defaults to hmac-md5 and the secret is expressed as a base-64 encoded string.		Add a TSIG record [RFC2845] to all packets sent, using the specified TSIG key algorithm, name and secret, where the algorithm defaults to hmac-md5 and the secret is expressed as a base-64 encoded string.

	~~Author~~

	~~Nominum, Inc~~.

	==Lebih Lanjut==		==Lebih Lanjut==

Onnowpurbo: /* Mengkonfigurasi DNS Server untuk testing */

2015-06-05T09:48:00Z

Mengkonfigurasi DNS Server untuk testing

← Older revision		Revision as of 09:48, 5 June 2015
Line 16:		Line 16:
	==Mengkonfigurasi DNS Server untuk testing==		==Mengkonfigurasi DNS Server untuk testing==

	~~If using~~ dnsperf ~~to test an authoritative~~ server, ~~the~~ name server ~~under test should be set up to serve one or more zones similar in size and number to what the~~ server ~~is expected to serve in production~~.		Jika menggunakan dnsperf untuk menguji server authoritif, name server yang diuji harus dibentuk untuk melayani satu atau lebih zona serupa dalam ukuran dan jumlah pada apa server diharapkan untuk melayani dalam produksi.

	~~Also~~, ~~be sure to turn off recursion in the~~ server~~'s configuration~~ (in BIND 8/9, ~~specify~~ "recursion no;" ~~in the~~ options block). In BIND 8, ~~you should also specify~~ "fetch-glue no;"; ~~otherwise the~~ server ~~may attempt to retrieve~~ glue ~~information from the Internet during the test~~, ~~slowing it down by an unpredictable factor~~.		Juga, pastikan untuk mematikan rekursi dalam konfigurasi server (di BIND 8/9, dengan "recursion no;" dalam options block). Dalam BIND 8, anda juga harus menentukan "fetch-glue no;"; jika server mungkin mencoba untuk mengambil informasi glue dari internet selama pengujian, ini memperlambat oleh faktor tak terduga.

	==Membuat input file query==		==Membuat input file query==

Onnowpurbo: /* Keterangan */

2015-06-05T09:42:23Z

Keterangan

← Older revision		Revision as of 09:42, 5 June 2015
Line 10:		Line 10:
	==Keterangan==		==Keterangan==

	dnsperf ~~is a~~ DNS server ~~performance testing tool. It is primarily intended for measuring the performance of authoritative~~ DNS ~~servers~~, ~~but it can also be used for measuring~~ caching server ~~performance in a closed laboratory environment. For testing~~ caching ~~servers resolving against the live~~ Internet, ~~the resperf program is preferred~~.		dnsperf adalah alat pengujian kinerja server DNS. Hal ini terutama ditujukan untuk mengukur kinerja server DNS authoritif, tetapi juga dapat digunakan untuk mengukur kinerja server caching di lingkungan laboratorium tertutup. Untuk menguji server caching yang tersambung ke Internet, lebih baik menggunakan respref.

	~~It is recommended that~~ dnsperf ~~and the name~~ server ~~under test be run on separate machines~~, ~~so that the~~ CPU ~~usage of~~ dnsperf ~~itself does not slow down the name~~ server. ~~The two machines should be connected with a fast network~~, ~~preferably a dedicated~~ Gigabit Ethernet ~~segment~~. ~~Testing through a~~ router or firewall ~~is not advisable~~.		Disarankan dnsperf dan DNS server yang diuji dijalankan pada mesin yang terpisah, sehingga penggunaan CPU dari dnsperf sendiri tidak memperlambat server nama. Dua mesin harus terhubung dengan jaringan yang cepat, sebaiknya segmen khusus Gigabit Ethernet. Pengujian melalui router atau firewall tidak dianjurkan.

	==Mengkonfigurasi DNS Server untuk testing==		==Mengkonfigurasi DNS Server untuk testing==

Onnowpurbo: /* Keterangan */

2015-06-05T09:39:53Z

Keterangan

← Older revision		Revision as of 09:39, 5 June 2015
Line 14:		Line 14:
	It is recommended that dnsperf and the name server under test be run on separate machines, so that the CPU usage of dnsperf itself does not slow down the name server. The two machines should be connected with a fast network, preferably a dedicated Gigabit Ethernet segment. Testing through a router or firewall is not advisable.		It is recommended that dnsperf and the name server under test be run on separate machines, so that the CPU usage of dnsperf itself does not slow down the name server. The two machines should be connected with a fast network, preferably a dedicated Gigabit Ethernet segment. Testing through a router or firewall is not advisable.

	~~Configuring the name server~~		==Mengkonfigurasi DNS Server untuk testing==

	If using dnsperf to test an authoritative server, the name server under test should be set up to serve one or more zones similar in size and number to what the server is expected to serve in production.		If using dnsperf to test an authoritative server, the name server under test should be set up to serve one or more zones similar in size and number to what the server is expected to serve in production.
Line 20:		Line 20:
	Also, be sure to turn off recursion in the server's configuration (in BIND 8/9, specify "recursion no;" in the options block). In BIND 8, you should also specify "fetch-glue no;"; otherwise the server may attempt to retrieve glue information from the Internet during the test, slowing it down by an unpredictable factor.		Also, be sure to turn off recursion in the server's configuration (in BIND 8/9, specify "recursion no;" in the options block). In BIND 8, you should also specify "fetch-glue no;"; otherwise the server may attempt to retrieve glue information from the Internet during the test, slowing it down by an unpredictable factor.

	~~Constructing a query~~ input file		==Membuat input file query==

	A dnsperf input file should contain a large and realistic set of queries, on the order of ten thousand to a million. The input file contains one line per query, consisting of a domain name and an RR type name separated by a space. The class of the query is implicitly IN.		A dnsperf input file should contain a large and realistic set of queries, on the order of ten thousand to a million. The input file contains one line per query, consisting of a domain name and an RR type name separated by a space. The class of the query is implicitly IN.