();
builder.Services.AddHttpContextAccessor();
builder.Services.AddDnsmasqApiHttpClients();
diff --git a/src/DnsmasqWebUI/appsettings.json b/src/DnsmasqWebUI/appsettings.json
index a11a2cd..a882f9c 100644
--- a/src/DnsmasqWebUI/appsettings.json
+++ b/src/DnsmasqWebUI/appsettings.json
@@ -2,6 +2,9 @@
"Application": {
"ApplicationTitle": "Local DNS"
},
+ "UpdateCheck": {
+ "IntervalMinutes": 1440
+ },
"Logging": {
"LogLevel": {
"Default": "Information",
diff --git a/src/DnsmasqWebUI/wwwroot/js/ec-option-help.js b/src/DnsmasqWebUI/wwwroot/js/ec-option-help.js
new file mode 100644
index 0000000..2f0dcb2
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/js/ec-option-help.js
@@ -0,0 +1,26 @@
+/**
+ * Positioning and scroll-close for config option help popover.
+ * Called from ConfigOptionHelpModal.razor via IJSRuntime.InvokeAsync.
+ */
+window.getConfigOptionHelpAnchorRect = function (anchorId) {
+ var el = document.getElementById(anchorId);
+ if (!el) return null;
+ var r = el.getBoundingClientRect();
+ return { top: r.top, left: r.left, bottom: r.bottom, width: r.width, height: r.height };
+};
+
+var _configOptionHelpScrollHandler = null;
+
+window.addConfigOptionHelpScrollCloseListener = function (dotNetRef) {
+ if (_configOptionHelpScrollHandler) return;
+ _configOptionHelpScrollHandler = function () {
+ dotNetRef.invokeMethodAsync('OnScrollClose').catch(function () {});
+ };
+ window.addEventListener('scroll', _configOptionHelpScrollHandler, true);
+};
+
+window.removeConfigOptionHelpScrollCloseListener = function () {
+ if (!_configOptionHelpScrollHandler) return;
+ window.removeEventListener('scroll', _configOptionHelpScrollHandler, true);
+ _configOptionHelpScrollHandler = null;
+};
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/addn-hosts.html b/src/DnsmasqWebUI/wwwroot/option-help/addn-hosts.html
new file mode 100644
index 0000000..bac7ec8
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/addn-hosts.html
@@ -0,0 +1,5 @@
+-H, --addn-hosts=<file>
+Additional hosts file. Read the specified file as well as /etc/hosts. If --no-hosts is given, read
+only the specified file. This option may be repeated for more than one
+additional hosts file. If a directory is given, then read all the files contained in that directory
+in alphabetical order.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/address.html b/src/DnsmasqWebUI/wwwroot/option-help/address.html
new file mode 100644
index 0000000..f9754ec
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/address.html
@@ -0,0 +1,27 @@
+-A, --address=/<domain>[/<domain>...]/[<ipaddr>]
+Specify an IP address to return for any host in the given domains.
+A (or AAAA) queries in the domains are never forwarded and always replied to
+with the specified IP address which may be IPv4 or IPv6. To give
+multiple addresses or both IPv4 and IPv6 addresses for a domain, use repeated --address flags.
+Note that /etc/hosts and DHCP leases override this for individual
+names. A common use of this is to redirect the entire doubleclick.net
+domain to some friendly local web server to avoid banner ads. The
+domain specification works in the same way as for --server, with
+the additional facility that /#/ matches any domain. Thus
+--address=/#/1.2.3.4 will always return 1.2.3.4 for any
+query not answered from /etc/hosts or DHCP and not sent to an
+upstream nameserver by a more specific --server directive. As for
+--server, one or more domains with no address returns a
+no-such-domain answer, so --address=/example.com/ is equivalent to
+--server=/example.com/ and returns NXDOMAIN for example.com and
+all its subdomains. An address specified as '#' translates to the NULL
+address of 0.0.0.0 and its IPv6 equivalent of :: so
+--address=/example.com/# will return NULL addresses for example.com and
+its subdomains. This is partly syntactic sugar for --address=/example.com/0.0.0.0
+and --address=/example.com/:: but is also more efficient than including both
+as separate configuration lines. Note that NULL addresses normally work in the same way as localhost, so beware that clients looking up these names are likely to end up talking to themselves.
+
+Note that the behaviour for queries which don't match the specified address literal changed in version 2.86.
+Previous versions, configured with (eg) --address=/example.com/1.2.3.4 and then queried for a RR type other than
+A would return a NoData answer. From 2.86, the query is sent upstream. To restore the pre-2.86 behaviour,
+use the configuration --address=/example.com/1.2.3.4 --local=/example.com/
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/alias.html b/src/DnsmasqWebUI/wwwroot/option-help/alias.html
new file mode 100644
index 0000000..ff0e233
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/alias.html
@@ -0,0 +1,13 @@
+-V, --alias=[<old-ip>]|[<start-ip>-<end-ip>],<new-ip>[,<mask>]
+Modify IPv4 addresses returned from upstream nameservers; old-ip is
+replaced by new-ip. If the optional mask is given then any address
+which matches the masked old-ip will be re-written. So, for instance
+--alias=1.2.3.0,6.7.8.0,255.255.255.0
+
+will map 1.2.3.56 to 6.7.8.56 and 1.2.3.67 to 6.7.8.67. This is what
+Cisco PIX routers call "DNS doctoring". If the old IP is given as
+range, then only addresses in the range, rather than a whole subnet,
+are re-written. So
+--alias=192.168.0.10-192.168.0.40,10.0.0.0,255.255.255.0
+
+maps 192.168.0.10->192.168.0.40 to 10.0.0.10->10.0.0.40
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/all-servers.html b/src/DnsmasqWebUI/wwwroot/option-help/all-servers.html
new file mode 100644
index 0000000..dca4c64
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/all-servers.html
@@ -0,0 +1,5 @@
+--all-servers
+By default, when dnsmasq has more than one upstream server available,
+it will send queries to just one server. Setting this flag forces
+dnsmasq to send all queries to all available servers. The reply from
+the server which answers first will be returned to the original requester.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/auth-server.html b/src/DnsmasqWebUI/wwwroot/option-help/auth-server.html
new file mode 100644
index 0000000..7577439
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/auth-server.html
@@ -0,0 +1,17 @@
+--auth-server=<domain>,[<interface>|<ip-address>...]
+Enable DNS authoritative mode for queries arriving at an interface or address. Note that the interface or address
+need not be mentioned in
+--interface
+
+or
+--listen-address
+
+configuration, indeed
+--auth-server
+
+will override these and provide a different DNS service on the
+specified interface. The <domain> is the "glue record". It should
+resolve in the global DNS to an A and/or AAAA record which points to
+the address dnsmasq is listening on. When an interface is specified,
+it may be qualified with "/4" or "/6" to specify only the IPv4 or IPv6
+addresses associated with the interface. Since any defined authoritative zones are also available as part of the normal recusive DNS service supplied by dnsmasq, it can make sense to have an --auth-server declaration with no interfaces or address, but simply specifying the primary external nameserver.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/auth-ttl.html b/src/DnsmasqWebUI/wwwroot/option-help/auth-ttl.html
new file mode 100644
index 0000000..c9b7a1e
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/auth-ttl.html
@@ -0,0 +1,2 @@
+--auth-ttl=<time>
+Set the TTL value returned in answers from the authoritative server.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/bind-dynamic.html b/src/DnsmasqWebUI/wwwroot/option-help/bind-dynamic.html
new file mode 100644
index 0000000..205ac93
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/bind-dynamic.html
@@ -0,0 +1,11 @@
+--bind-dynamic
+Enable a network mode which is a hybrid between
+--bind-interfaces
+
+and the default. Dnsmasq binds the address of individual interfaces,
+allowing multiple dnsmasq instances, but if new interfaces or
+addresses appear, it automatically listens on those (subject to any
+access-control configuration). This makes dynamically created
+interfaces work in the same way as the default. Implementing this
+option requires non-standard networking APIs and it is only available
+under Linux. On other platforms it falls-back to --bind-interfaces mode.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/bind-interfaces.html b/src/DnsmasqWebUI/wwwroot/option-help/bind-interfaces.html
new file mode 100644
index 0000000..22f3595
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/bind-interfaces.html
@@ -0,0 +1,10 @@
+-z, --bind-interfaces
+On systems which support it, dnsmasq binds the wildcard address,
+even when it is listening on only some interfaces. It then discards
+requests that it shouldn't reply to. This has the advantage of
+working even when interfaces come and go and change address. This
+option forces dnsmasq to really bind only the interfaces it is
+listening on. About the only time when this is useful is when
+running another nameserver (or another instance of dnsmasq) on the
+same machine. Setting this option also enables multiple instances of
+dnsmasq which provide DHCP service to run in the same machine.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/bogus-nxdomain.html b/src/DnsmasqWebUI/wwwroot/option-help/bogus-nxdomain.html
new file mode 100644
index 0000000..e956fc0
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/bogus-nxdomain.html
@@ -0,0 +1,8 @@
+-B, --bogus-nxdomain=<ipaddr>[/prefix]
+Transform replies which contain the specified address or subnet into "No such
+domain" replies. IPv4 and IPv6 are supported. This is intended to counteract a devious move made by
+Verisign in September 2003 when they started returning the address of
+an advertising web page in response to queries for unregistered names,
+instead of the correct NXDOMAIN response. This option tells dnsmasq to
+fake the correct response when it sees this behaviour. As at Sept 2003
+the IP address being returned by Verisign is 64.94.110.11
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/bogus-priv.html b/src/DnsmasqWebUI/wwwroot/option-help/bogus-priv.html
new file mode 100644
index 0000000..16db0cd
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/bogus-priv.html
@@ -0,0 +1,9 @@
+-b, --bogus-priv
+Bogus private reverse lookups. All reverse lookups for private IP ranges (ie 192.168.x.x, etc)
+which are not found in /etc/hosts or the DHCP leases file are answered
+with "no such domain" rather than being forwarded upstream. The
+set of prefixes affected is the list given in RFC6303, for IPv4 and IPv6.
+Enabling this also subtly alters DNSSEC validation for reverse lookups in the
+private ranges such that a non-secure DS record is accepted as proof that
+the range is not signed. This works around behaviour by the public DNS services
+which seem not to return validated proof-of-non-existence for DS records in these domains.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/cache-rr.html b/src/DnsmasqWebUI/wwwroot/option-help/cache-rr.html
new file mode 100644
index 0000000..1eb4242
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/cache-rr.html
@@ -0,0 +1,6 @@
+--cache-rr=<rrtype>[,<rrtype>...]
+By default, dnsmasq caches A, AAAA, CNAME and SRV DNS record types.
+This option adds other record types to the cache. The RR-type can be given
+as a name such as TXT or MX or a decimal number. A single --cache-rr option
+can take a comma-separated list of RR-types and more than one --cache-rr option
+is allowed. Use --cache-rr=ANY to enable caching for all RR-types.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/cache-size.html b/src/DnsmasqWebUI/wwwroot/option-help/cache-size.html
new file mode 100644
index 0000000..78fffd0
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/cache-size.html
@@ -0,0 +1,2 @@
+-c, --cache-size=<cachesize>
+Set the size of dnsmasq's cache. The default is 150 names. Setting the cache size to zero disables caching. Note: huge cache size impacts performance.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/clear-on-reload.html b/src/DnsmasqWebUI/wwwroot/option-help/clear-on-reload.html
new file mode 100644
index 0000000..e9ead74
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/clear-on-reload.html
@@ -0,0 +1,5 @@
+--clear-on-reload
+Whenever /etc/resolv.conf is re-read or the upstream servers are set
+via DBus, clear the DNS cache.
+This is useful when new nameservers may have different
+data than that held in cache.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/cname.html b/src/DnsmasqWebUI/wwwroot/option-help/cname.html
new file mode 100644
index 0000000..23e037f
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/cname.html
@@ -0,0 +1,12 @@
+--cname=<cname>,[<cname>,]<target>[,<TTL>]
+Return a CNAME record which indicates that <cname> is really
+<target>. There is a significant limitation on the target; it must be a
+DNS record which is known to dnsmasq and NOT a DNS record which comes from
+an upstream server. The cname must be unique, but it
+is permissible to have more than one cname pointing to the same target. Indeed
+it's possible to declare multiple cnames to a target in a single line, like so:
+--cname=cname1,cname2,target
+
+If the time-to-live is given, it overrides the default, which is zero
+or the value of --local-ttl. The value is a positive integer and gives
+the time-to-live in seconds.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/conntrack.html b/src/DnsmasqWebUI/wwwroot/option-help/conntrack.html
new file mode 100644
index 0000000..da280f6
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/conntrack.html
@@ -0,0 +1,9 @@
+--conntrack
+Read the Linux connection track mark associated with incoming DNS
+queries and set the same mark value on upstream traffic used to answer
+those queries. This allows traffic generated by dnsmasq to be
+associated with the queries which cause it, useful for bandwidth
+accounting and firewalling. Dnsmasq must have conntrack support
+compiled in and the kernel must have conntrack support
+included and configured. This option cannot be combined with
+--query-port.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-authoritative.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-authoritative.html
new file mode 100644
index 0000000..6f87ec7
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-authoritative.html
@@ -0,0 +1,10 @@
+-K, --dhcp-authoritative
+Should be set when dnsmasq is definitely the only DHCP server on a network.
+For DHCPv4, it changes the behaviour from strict RFC compliance so that DHCP requests on
+unknown leases from unknown hosts are not ignored. This allows new hosts
+to get a lease without a tedious timeout under all circumstances. It also
+allows dnsmasq to rebuild its lease database without each client needing to
+reacquire a lease, if the database is lost. For DHCPv6 it controls the same
+behaviour as DHCPv4 with missing leases (except for the RFC uncompliance - the
+DHCPv6 RFCs allow this behaviour if configured). It also sets the
+priority in replies to 255 (the maximum) instead of 0 (the minimum).
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-boot.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-boot.html
new file mode 100644
index 0000000..1811a6c
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-boot.html
@@ -0,0 +1,14 @@
+-M, --dhcp-boot=[tag:<tag>,]<filename>,[<servername>[,<server address>|<tftp_servername>]]
+(IPv4 only) Set BOOTP options to be returned by the DHCP server. Server name and
+address are optional: if not provided, the name is left empty, and the
+address set to the address of the machine running dnsmasq. If dnsmasq
+is providing a TFTP service (see
+--enable-tftp
+
+) then only the filename is required here to enable network booting.
+If the optional tag(s) are given,
+they must match for this configuration to be sent.
+Instead of an IP address, the TFTP server address can be given as a domain
+name which is looked up in /etc/hosts. This name can be associated in
+/etc/hosts with multiple IP addresses, which are used round-robin.
+This facility can be used to load balance the tftp load among a set of servers.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-host.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-host.html
new file mode 100644
index 0000000..4a958dd
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-host.html
@@ -0,0 +1,144 @@
+-G, --dhcp-host=[<hwaddr>][,id:<client_id>|*][,set:<tag>][,tag:<tag>][,<ipaddr>][,<hostname>][,<lease_time>][,ignore]
+Specify per host parameters for the DHCP server. This allows a machine
+with a particular hardware address to be always allocated the same
+hostname, IP address and lease time. A hostname specified like this
+overrides any supplied by the DHCP client on the machine. It is also
+allowable to omit the hardware address and include the hostname, in
+which case the IP address and lease times will apply to any machine
+claiming that name. For example
+--dhcp-host=00:20:e0:3b:13:af,wap,infinite
+
+tells dnsmasq to give
+the machine with hardware address 00:20:e0:3b:13:af the name wap, and
+an infinite DHCP lease.
+--dhcp-host=lap,192.168.0.199
+
+tells
+dnsmasq to always allocate the machine lap the IP address
+192.168.0.199.
+
+Addresses allocated like this are not constrained to be
+in the range given by the --dhcp-range option, but they must be in
+the same subnet as some valid dhcp-range. For
+subnets which don't need a pool of dynamically allocated addresses,
+use the "static" keyword in the --dhcp-range declaration.
+
+It is allowed to use client identifiers (called client
+DUID in IPv6-land) rather than
+hardware addresses to identify hosts by prefixing with 'id:'. Thus:
+--dhcp-host=id:01:02:03:04,.....
+
+refers to the host with client identifier 01:02:03:04. It is also
+allowed to specify the client ID as text, like this:
+--dhcp-host=id:clientidastext,.....
+
+A single
+--dhcp-host
+
+may contain an IPv4 address or one or more IPv6 addresses, or both. IPv6 addresses must be bracketed by square brackets thus:
+--dhcp-host=laptop,[1234::56]
+
+IPv6 addresses may contain only the host-identifier part:
+--dhcp-host=laptop,[::56]
+
+in which case they act as wildcards in constructed DHCP ranges, with
+the appropriate network part inserted. For IPv6, an address may include a prefix length:
+--dhcp-host=laptop,[1234:50/126]
+
+which (in this case) specifies four addresses, 1234::50 to 1234::53. This (an the ability
+to specify multiple addresses) is useful
+when a host presents either a consistent name or hardware-ID, but varying DUIDs, since it allows
+dnsmasq to honour the static address allocation but assign a different address for each DUID. This
+typically occurs when chain netbooting, as each stage of the chain gets in turn allocates an address.
+
+Note that in IPv6 DHCP, the hardware address may not be
+available, though it normally is for direct-connected clients, or
+clients using DHCP relays which support RFC 6939.
+
+
+For DHCPv4, the special option id:* means "ignore any client-id
+and use MAC addresses only." This is useful when a client presents a client-id sometimes
+but not others.
+
+If a name appears in /etc/hosts, the associated address can be
+allocated to a DHCP lease, but only if a
+--dhcp-host
+
+option specifying the name also exists. Only one hostname can be
+given in a
+--dhcp-host
+
+option, but aliases are possible by using CNAMEs. (See
+--cname
+
+). Note that /etc/hosts is NOT used when the DNS server side of dnsmasq
+is disabled by setting the DNS server port to zero.
+
+More than one
+--dhcp-host
+
+can be associated (by name, hardware address or UID) with a host. Which one is used
+(and therefore which address is allocated by DHCP and appears in the DNS) depends
+on the subnet on which the host last obtained a DHCP lease:
+the
+--dhcp-host
+
+with an address within the subnet is used. If more than one address is within the subnet,
+the result is undefined. A corollary to this is that the name associated with a host using
+--dhcp-host
+
+does not appear in the DNS until the host obtains a DHCP lease.
+
+
+The special keyword ignore tells dnsmasq never to offer a DHCP lease
+to a machine. The machine
+can be specified by hardware address, client ID or hostname. For
+example: --dhcp-host=00:20:e0:3b:13:af,ignore.
+This can be useful when there is another DHCP server on the network which should
+be used by some machines.
+
+The set:<tag> construct sets the tag
+whenever this --dhcp-host directive is in use. This can be used to
+selectively send DHCP options just for this host. More than one tag
+can be set in a --dhcp-host directive (but not in other places where
+set:<tag> is allowed). When a host matches any
+--dhcp-host directive (or one implied by /etc/ethers) then the special
+tag known is set. This allows dnsmasq to be configured to
+ignore requests from unknown machines using
+--dhcp-ignore=tag:!known.
+If the host matches only a --dhcp-host directive which cannot
+be used because it specifies an address on a different subnet, the tag known-othernet is set.
+
+The tag:<tag> construct filters which dhcp-host directives are used. More than
+one tag can be provided. In this case, the request must match all tags. Tagged
+directives are used in preference to untagged ones. Note that one of <hwaddr>,
+<client_id> or <hostname> still must be specified (can be a wildcard).
+
+Ethernet addresses (but not client-ids) may have
+wildcard bytes, so for example
+--dhcp-host=00:20:e0:3b:13:*,ignore
+
+will cause dnsmasq to ignore the given range of hardware addresses. Note that
+the "*" will need to be escaped or quoted on a command line, but not
+in the configuration file.
+
+Hardware addresses normally match any
+network (ARP) type, but it is possible to restrict them to a single
+ARP type by preceding them with the ARP-type (in HEX) and "-". so
+--dhcp-host=06-00:20:e0:3b:13:af,1.2.3.4
+
+will only match a
+Token-Ring hardware address, since the ARP-address type for token ring
+is 6.
+
+As a special case, in DHCPv4, it is possible to include more than one
+hardware address. eg:
+--dhcp-host=11:22:33:44:55:66,12:34:56:78:90:12,192.168.0.2.
+This allows an IP address to be associated with
+multiple hardware addresses, and gives dnsmasq permission to abandon a
+DHCP lease to one of the hardware addresses when another one asks for
+a lease. Beware that this is a dangerous thing to do: it will only
+work reliably if only one of the hardware addresses is active at any
+time and there is no way for dnsmasq to enforce this. It is, for instance,
+useful to allocate a stable IP address to a laptop which
+has both wired and wireless interfaces.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-hostsdir.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-hostsdir.html
new file mode 100644
index 0000000..559fe0b
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-hostsdir.html
@@ -0,0 +1,8 @@
+--dhcp-hostsdir=<path>
+This is equivalent to --dhcp-hostsfile, except for the following. The path MUST be a
+directory, and not an individual file. Changed or new files within
+the directory are read automatically, without the need to send SIGHUP.
+If a file is deleted or changed after it has been read by dnsmasq, then the
+host record it contained will remain until dnsmasq receives a SIGHUP, or
+is restarted; ie host records are only added dynamically. The order in which the
+files in a directory are read is not defined.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-hostsfile.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-hostsfile.html
new file mode 100644
index 0000000..7c7cae1
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-hostsfile.html
@@ -0,0 +1,7 @@
+--dhcp-hostsfile=<path>
+Read DHCP host information from the specified file. If a directory
+is given, then read all the files contained in that directory in alphabetical order. The file contains
+information about one host per line. The format of a line is the same
+as text to the right of '=' in --dhcp-host. The advantage of storing DHCP host information
+in this file is that it can be changed without re-starting dnsmasq:
+the file will be re-read when dnsmasq receives SIGHUP.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ignore-names.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ignore-names.html
new file mode 100644
index 0000000..8de805c
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ignore-names.html
@@ -0,0 +1,7 @@
+--dhcp-ignore-names[=tag:<tag>[,tag:<tag>]]
+When all the given tags appear in the tag set, ignore any hostname
+provided by the host. Note that, unlike --dhcp-ignore, it is permissible
+to supply no tags, in which case DHCP-client supplied hostnames
+are always ignored, and DHCP hosts are added to the DNS using only
+--dhcp-host configuration in dnsmasq and the contents of /etc/hosts and
+/etc/ethers.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ignore.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ignore.html
new file mode 100644
index 0000000..39f21d5
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ignore.html
@@ -0,0 +1,3 @@
+-J, --dhcp-ignore=tag:<tag>[,tag:<tag>]
+When all the given tags appear in the tag set, ignore the host and do
+not allocate it a DHCP lease.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-lease-max.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-lease-max.html
new file mode 100644
index 0000000..61eb93b
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-lease-max.html
@@ -0,0 +1,5 @@
+-X, --dhcp-lease-max=<number>
+Limits dnsmasq to the specified maximum number of DHCP leases. The
+default is 1000. This limit is to prevent DoS attacks from hosts which
+create thousands of leases and use lots of memory in the dnsmasq
+process.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-leasefile.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-leasefile.html
new file mode 100644
index 0000000..c128f8d
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-leasefile.html
@@ -0,0 +1,2 @@
+-l, --dhcp-leasefile=<path>
+Use the specified file to store DHCP lease information.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-mac.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-mac.html
new file mode 100644
index 0000000..ffc3bcf
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-mac.html
@@ -0,0 +1,6 @@
+-4, --dhcp-mac=set:<tag>,<MAC address>
+Map from a MAC address to a tag. The MAC address may include
+wildcards. For example
+--dhcp-mac=set:3com,01:34:23:*:*:*
+
+will set the tag "3com" for any host whose MAC address matches the pattern.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-match.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-match.html
new file mode 100644
index 0000000..8909538
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-match.html
@@ -0,0 +1,22 @@
+--dhcp-match=set:<tag>,<option number>|option:<option name>|vi-encap:<enterprise>[,<value>]
+Without <value>, set <tag> if the client sends a DHCP
+option of the given number or name. With <value>, set <tag> only if
+the client sends the option matching or containing <value>.
+
+The value may be of the form
+"01:ff:*:02" in which case the value must match (apart from wildcards)
+but the option sent may have unmatched data past the end of the
+value. The value may also be of the same form as in
+--dhcp-option
+
+in which case the option sent is treated as an array, and one element
+must match.
+--dhcp-match=set:efi-ia32,option:client-arch,6
+
+sets the tag efi-ia32 if the number 6 appears in the list of
+architectures sent by the client in option 93. (See RFC 4578 for
+details.) If the value is a string, substring matching is used.
+
+The special form with vi-encap:<enterprise number> matches against
+vendor-identifying vendor classes for the specified enterprise. Please
+see RFC 3925 for more details of these rare and interesting beasts.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-name-match.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-name-match.html
new file mode 100644
index 0000000..b077189
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-name-match.html
@@ -0,0 +1,2 @@
+--dhcp-name-match=set:<tag>,<name>[*]
+Set a <tag> if the given <name> is supplied by a DHCP client. There may be a single trailing wildcard *, with a glob meaning. Combined with dhcp-ignore or dhcp-ignore-names this gives the ability to ignore certain clients by name, or disallow certain hostnames from being claimed by a client.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-option-force.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-option-force.html
new file mode 100644
index 0000000..4ee9bd9
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-option-force.html
@@ -0,0 +1,7 @@
+--dhcp-option-force=[tag:<tag>,[tag:<tag>,]][encap:<opt>,][vi-encap:<enterprise>,][vendor:[<vendor-class>],]<opt>,[<value>[,<value>]]
+This works in exactly the same way as
+--dhcp-option
+
+except that the option will always be sent, even if the client does
+not ask for it in the parameter request list. This is sometimes
+needed, for example when sending options to PXELinux.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-option.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-option.html
new file mode 100644
index 0000000..1d80c83
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-option.html
@@ -0,0 +1,99 @@
+-O, --dhcp-option=[tag:<tag>,[tag:<tag>,]][encap:<opt>,][vi-encap:<enterprise>,][vendor:[<vendor-class>],][<opt>|option:<opt-name>|option6:<opt>|option6:<opt-name>],[<value>[,<value>]]
+Send various extra options to DHCP clients. By default,
+dnsmasq sends some standard options to DHCP clients, the netmask and
+broadcast address are set to the same as the host running dnsmasq, and
+the DNS server and default route are set to the address of the machine
+running dnsmasq. (Equivalent rules apply for IPv6.) If the domain name option has been set, that is sent.
+This configuration allows these defaults to be overridden,
+or other options specified. The option to be sent may be given as a
+decimal number or as option:<option-name>.
+
+Option numbers are
+specified in RFC2132 and subsequent RFCs. The set of option-names
+known by dnsmasq can be discovered by running dnsmasq --help dhcp.
+For example, to set the default route option to 192.168.4.4, use
+--dhcp-option=3,192.168.4.4 or
+--dhcp-option=option:router,192.168.4.4
+and to set the time-server address to 192.168.0.4, use
+--dhcp-option=42,192.168.0.4 or
+--dhcp-option=option:ntp-server,192.168.0.4.
+The special address 0.0.0.0 means "the address of the system running dnsmasq".
+
+An option without data is valid, and includes just the option without data.
+(There is only one option with a zero length data field currently defined for DHCPv4, 80:rapid commit, so this feature is not very useful in practice). Options for which dnsmasq normally
+provides default values can be omitted by defining the option with no data. These are
+netmask, broadcast, router, DNS server, domainname and hostname. Thus, for DHCPv4
+--dhcp-option = option:router
+
+will result in no router option being sent, rather than the default of the host on which dnsmasq is running. For DHCPv6, the same is true of the options DNS server and refresh time.
+
+
+Data types allowed are comma separated
+dotted-quad IPv4 addresses, []-wrapped IPv6 addresses, a decimal number, colon-separated hex digits
+and a text string. If the optional tags are given then
+this option is only sent when all the tags are matched.
+
+Special processing is done on a text argument for option 119, to
+conform with RFC 3397. Text or dotted-quad IP addresses as arguments
+to option 120 are handled as per RFC 3361. Dotted-quad IP addresses
+which are followed by a slash and then a netmask size are encoded as
+described in RFC 3442.
+
+IPv6 options are specified using the option6:
+keyword, followed by the option number or option name. The IPv6 option
+name space is disjoint from the IPv4 option name space. IPv6 addresses
+in options must be bracketed with square brackets, eg.
+ --dhcp-option=option6:ntp-server,[1234::56].
+For IPv6, [::] means "the global address of
+the machine running dnsmasq", whilst [fd00::] is replaced with the
+ULA, if it exists, and [fe80::] with the link-local address.
+
+Be careful: data-type suitability for the option number sent is not checked.
+It is quite possible to persuade dnsmasq to generate illegal DHCP packets with
+injudicious use of this flag.
+When the value is a decimal number, dnsmasq must determine how
+large the data item is. It does this by examining the option number and/or the
+value, but can be overridden by appending a single letter flag as follows:
+b = one byte, s = two bytes, i = four bytes. This is mainly useful with
+encapsulated vendor class options (see below) where dnsmasq cannot
+determine data size from the option number. Option data which
+consists solely of periods and digits will be interpreted by dnsmasq
+as an IP address, and inserted into an option as such. To force a
+literal string, use quotes. For instance when using option 66 to send
+a literal IP address as TFTP server name, it is necessary to do
+--dhcp-option=66,"1.2.3.4".
+
+Encapsulated Vendor-class options may also be specified (IPv4 only) using
+--dhcp-option: for instance
+--dhcp-option=vendor:PXEClient,1,0.0.0.0
+
+sends the encapsulated vendor
+class-specific option "mftp-address=0.0.0.0" to any client whose
+vendor-class matches "PXEClient". The vendor-class matching is
+substring based (see --dhcp-vendorclass for details). If a
+vendor-class option (number 60) is sent by dnsmasq, then that is used
+for selecting encapsulated options in preference to any sent by the
+client. It is
+possible to omit the vendorclass completely;
+--dhcp-option=vendor:,1,0.0.0.0
+
+in which case the encapsulated option is always sent.
+
+Options may be encapsulated (IPv4 only) within other options: for instance
+--dhcp-option=encap:175, 190, iscsi-client0
+
+will send option 175, within which is the option 190. If multiple
+options are given which are encapsulated with the same option number
+then they will be correctly combined into one encapsulated option.
+encap: and vendor: may not both be set in the same --dhcp-option.
+
+The final variant on encapsulated options is "Vendor-Identifying
+Vendor Options" as specified by RFC3925. These are denoted like this:
+--dhcp-option=vi-encap:2, 10, text
+
+The number in the vi-encap: section is the IANA enterprise number
+used to identify this option. This form of encapsulation is supported
+in IPv6.
+
+The address 0.0.0.0 is not treated specially in
+encapsulated options.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-optsfile.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-optsfile.html
new file mode 100644
index 0000000..84c9112
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-optsfile.html
@@ -0,0 +1,11 @@
+--dhcp-optsfile=<path>
+Read DHCP option information from the specified file. If a directory
+is given, then read all the files contained in that directory in alphabetical order. The advantage of
+using this option is the same as for --dhcp-hostsfile: the
+--dhcp-optsfile will be re-read when dnsmasq receives SIGHUP. Note that
+it is possible to encode the information in a
+--dhcp-boot
+
+flag as DHCP options, using the options names bootfile-name,
+server-ip-address and tftp-server. This allows these to be included
+in a --dhcp-optsfile.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-range.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-range.html
new file mode 100644
index 0000000..a7ddb01
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-range.html
@@ -0,0 +1,2 @@
+-F, --dhcp-range=[tag:<tag>[,tag:<tag>],][set:<tag>,]<start-addr>[,<end-addr>|<mode>[,<netmask>[,<broadcast>]]][,<lease time>]
+
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-rapid-commit.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-rapid-commit.html
new file mode 100644
index 0000000..e7193c7
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-rapid-commit.html
@@ -0,0 +1,6 @@
+--dhcp-rapid-commit
+Enable DHCPv4 Rapid Commit Option specified in RFC 4039. When enabled, dnsmasq
+will respond to a DHCPDISCOVER message including a Rapid Commit
+option with a DHCPACK including a Rapid Commit option and fully committed
+address and configuration information. Should only be enabled if either the
+server is the only server for the subnet, or multiple servers are present and they each commit a binding for all clients.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-script.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-script.html
new file mode 100644
index 0000000..5d8bf6c
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-script.html
@@ -0,0 +1,146 @@
+-6 --dhcp-script=<path>
+Whenever a new DHCP lease is created, or an old one destroyed, or a
+TFTP file transfer completes, the
+executable specified by this option is run. <path>
+must be an absolute pathname, no PATH search occurs.
+The arguments to the process
+are "add", "old" or "del", the MAC
+address of the host (or DUID for IPv6) , the IP address, and the hostname,
+if known. "add" means a lease has been created, "del" means it has
+been destroyed, "old" is a notification of an existing lease when
+dnsmasq starts or a change to MAC address or hostname of an existing
+lease (also, lease length or expiry and client-id, if --leasefile-ro is set
+and lease expiry if --script-on-renewal is set).
+If the MAC address is from a network type other than ethernet,
+it will have the network type prepended, eg "06-01:23:45:67:89:ab" for
+token ring. The process is run as root (assuming that dnsmasq was originally run as
+root) even if dnsmasq is configured to change UID to an unprivileged user.
+
+The environment is inherited from the invoker of dnsmasq, with some or
+all of the following variables added
+
+For both IPv4 and IPv6:
+
+DNSMASQ_DOMAIN if the fully-qualified domain name of the host is
+known, this is set to the domain part. (Note that the hostname passed
+to the script as an argument is never fully-qualified.)
+
+If the client provides a hostname, DNSMASQ_SUPPLIED_HOSTNAME
+
+If the client provides user-classes, DNSMASQ_USER_CLASS0..DNSMASQ_USER_CLASSn
+
+If dnsmasq was compiled with HAVE_BROKEN_RTC, then
+the length of the lease (in seconds) is stored in
+DNSMASQ_LEASE_LENGTH, otherwise the time of lease expiry is stored in
+DNSMASQ_LEASE_EXPIRES. The number of seconds until lease expiry is
+always stored in DNSMASQ_TIME_REMAINING.
+
+DNSMASQ_DATA_MISSING is set to "1" during "old" events for existing
+leases generated at startup to indicate that data not stored in the
+persistent lease database will not be present. This comprises everything
+other than IP address, hostname, MAC address, DUID, IAID and lease length
+or expiry time.
+
+If a lease used to have a hostname, which is
+removed, an "old" event is generated with the new state of the lease,
+ie no name, and the former name is provided in the environment
+variable DNSMASQ_OLD_HOSTNAME.
+
+DNSMASQ_INTERFACE stores the name of
+the interface on which the request arrived; this is not set for "old"
+actions when dnsmasq restarts.
+
+DNSMASQ_RELAY_ADDRESS is set if the client
+used a DHCP relay to contact dnsmasq and the IP address of the relay
+is known.
+
+DNSMASQ_TAGS contains all the tags set during the
+DHCP transaction, separated by spaces.
+
+DNSMASQ_LOG_DHCP is set if
+--log-dhcp
+
+is in effect.
+
+DNSMASQ_REQUESTED_OPTIONS a string containing the decimal values in the Parameter Request List option, comma separated, if the parameter request list option is provided by the client.
+
+DNSMASQ_MUD_URL the Manufacturer Usage Description URL if provided by the client. (See RFC8520 for details.)
+
+
+For IPv4 only:
+
+DNSMASQ_CLIENT_ID if the host provided a client-id.
+
+DNSMASQ_CIRCUIT_ID, DNSMASQ_SUBSCRIBER_ID, DNSMASQ_REMOTE_ID if a
+DHCP relay-agent added any of these options.
+
+If the client provides vendor-class, DNSMASQ_VENDOR_CLASS.
+
+For IPv6 only:
+
+If the client provides vendor-class, DNSMASQ_VENDOR_CLASS_ID,
+containing the IANA enterprise id for the class, and
+DNSMASQ_VENDOR_CLASS0..DNSMASQ_VENDOR_CLASSn for the data.
+
+DNSMASQ_SERVER_DUID containing the DUID of the server: this is the same for
+every call to the script.
+
+DNSMASQ_IAID containing the IAID for the lease. If the lease is a
+temporary allocation, this is prefixed to 'T'.
+
+DNSMASQ_MAC containing the MAC address of the client, if known.
+
+Note that the supplied hostname, vendorclass and userclass data is
+only supplied for
+"add" actions or "old" actions when a host resumes an existing lease,
+since these data are not held in dnsmasq's lease
+database.
+
+
+
+All file descriptors are
+closed except stdin, which is open to /dev/null, and stdout and stderr which capture output for logging by dnsmasq.
+(In debug mode, stdio, stdout and stderr file are left as those inherited from the invoker of dnsmasq).
+
+The script is not invoked concurrently: at most one instance
+of the script is ever running (dnsmasq waits for an instance of script to exit
+before running the next). Changes to the lease database are which
+require the script to be invoked are queued awaiting exit of a running instance.
+If this queueing allows multiple state changes occur to a single
+lease before the script can be run then
+earlier states are discarded and the current state of that lease is
+reflected when the script finally runs.
+
+At dnsmasq startup, the script will be invoked for
+all existing leases as they are read from the lease file. Expired
+leases will be called with "del" and others with "old". When dnsmasq
+receives a HUP signal, the script will be invoked for existing leases
+with an "old" event.
+
+
+There are five further actions which may appear as the first argument
+to the script, "init", "arp-add", "arp-del", "relay-snoop" and "tftp".
+More may be added in the future, so
+scripts should be written to ignore unknown actions. "init" is
+described below in
+--leasefile-ro
+
+The "tftp" action is invoked when a TFTP file transfer completes: the
+arguments are the file size in bytes, the address to which the file
+was sent, and the complete pathname of the file.
+
+The "relay-snoop" action is invoked when dnsmasq is configured as a DHCP
+relay for DHCPv6 and it relays a prefx delegation to a client. The arguments
+are the name of the interface where the client is connected, its (link-local)
+address on that interface and the delegated prefix. This information is
+sufficient to install routes to the delegated prefix of a router. See
+--dhcp-relay
+
+for more details on configuring DHCP relay.
+
+The "arp-add" and "arp-del" actions are only called if enabled with
+--script-arp
+
+They are are supplied with a MAC address and IP address as arguments. "arp-add" indicates
+the arrival of a new entry in the ARP or neighbour table, and "arp-del" indicates the deletion of same.
+
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ttl.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ttl.html
new file mode 100644
index 0000000..78a48ec
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-ttl.html
@@ -0,0 +1,2 @@
+--dhcp-ttl=<time>
+As for --local-ttl, but affects only replies with information from DHCP leases. If both are given, --dhcp-ttl applies for DHCP information, and --local-ttl for others. Setting this to zero eliminates the effect of --local-ttl for DHCP.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-userclass.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-userclass.html
new file mode 100644
index 0000000..c3aac22
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-userclass.html
@@ -0,0 +1,8 @@
+-j, --dhcp-userclass=set:<tag>,<user-class>
+Map from a user-class string to a tag (with substring
+matching, like vendor classes). Most DHCP clients provide a
+"user class" which is configurable. This option
+maps user classes to tags, so that DHCP options may be selectively delivered
+to different classes of hosts. It is possible, for instance to use
+this to set a different printer server for hosts in the class
+"accounts" than for hosts in the class "engineering".
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dhcp-vendorclass.html b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-vendorclass.html
new file mode 100644
index 0000000..1f149af
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dhcp-vendorclass.html
@@ -0,0 +1,19 @@
+-U, --dhcp-vendorclass=set:<tag>,[enterprise:<IANA-enterprise number>,]<vendor-class>
+Map from a vendor-class string to a tag. Most DHCP clients provide a
+"vendor class" which represents, in some sense, the type of host. This option
+maps vendor classes to tags, so that DHCP options may be selectively delivered
+to different classes of hosts. For example
+--dhcp-vendorclass=set:printers,Hewlett-Packard JetDirect
+
+will allow options to be set only for HP printers like so:
+--dhcp-option=tag:printers,3,192.168.4.4
+
+The vendor-class string is
+substring matched against the vendor-class supplied by the client, to
+allow fuzzy matching. The set: prefix is optional but allowed for
+consistency.
+
+Note that in IPv6 only, vendorclasses are namespaced with an
+IANA-allocated enterprise number. This is given with enterprise:
+keyword and specifies that only vendorclasses matching the specified
+number should be searched.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dns-loop-detect.html b/src/DnsmasqWebUI/wwwroot/option-help/dns-loop-detect.html
new file mode 100644
index 0000000..45c1763
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dns-loop-detect.html
@@ -0,0 +1,9 @@
+--dns-loop-detect
+Enable code to detect DNS forwarding loops; ie the situation where a query sent to one
+of the upstream server eventually returns as a new query to the dnsmasq instance. The
+process works by generating TXT queries of the form <hex>.test and sending them to
+each upstream server. The hex is a UID which encodes the instance of dnsmasq sending the query
+and the upstream server to which it was sent. If the query returns to the server which sent it, then
+the upstream server through which it was sent is disabled and this event is logged. Each time the
+set of upstream servers changes, the test is re-run on all of them, including ones which
+were previously disabled.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dnssec-check-unsigned.html b/src/DnsmasqWebUI/wwwroot/option-help/dnssec-check-unsigned.html
new file mode 100644
index 0000000..3f289ee
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dnssec-check-unsigned.html
@@ -0,0 +1,15 @@
+--dnssec-check-unsigned[=no]
+As a default, dnsmasq checks that unsigned DNS replies are
+legitimate: this entails possible extra queries even for the majority of DNS
+zones which are not, at the moment, signed. If
+--dnssec-check-unsigned=no
+
+appears in the configuration, then such replies they are assumed to be valid and passed on (without the
+"authentic data" bit set, of course). This does not protect against an
+attacker forging unsigned replies for signed DNS zones, but it is
+fast.
+
+Versions of dnsmasq prior to 2.80 defaulted to not checking unsigned replies, and used
+--dnssec-check-unsigned
+
+to switch this on. Such configurations will continue to work as before, but those which used the default of no checking will need to be altered to explicitly select no checking. The new default is because switching off checking for unsigned replies is inherently dangerous. Not only does it open the possibility of forged replies, but it allows everything to appear to be working even when the upstream namesevers do not support DNSSEC, and in this case no DNSSEC validation at all is occurring.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dnssec.html b/src/DnsmasqWebUI/wwwroot/option-help/dnssec.html
new file mode 100644
index 0000000..8991423
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dnssec.html
@@ -0,0 +1,16 @@
+--dnssec
+Validate DNS replies and cache DNSSEC data. When forwarding DNS queries, dnsmasq requests the
+DNSSEC records needed to validate the replies. The replies are validated and the result returned as
+the Authenticated Data bit in the DNS packet. In addition the DNSSEC records are stored in the cache, making
+validation by clients more efficient. Note that validation by clients is the most secure DNSSEC mode, but for
+clients unable to do validation, use of the AD bit set by dnsmasq is useful, provided that the network between
+the dnsmasq server and the client is trusted. Dnsmasq must be compiled with HAVE_DNSSEC enabled, and DNSSEC
+trust anchors provided, see
+--trust-anchor.
+
+Because the DNSSEC validation process uses the cache, it is not
+permitted to reduce the cache size below the default when DNSSEC is
+enabled. The nameservers upstream of dnsmasq must be DNSSEC-capable,
+ie capable of returning DNSSEC records with data. If they are not,
+then dnsmasq will not be able to determine the trusted status of
+answers and this means that DNS service will be entirely broken.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/domain-needed.html b/src/DnsmasqWebUI/wwwroot/option-help/domain-needed.html
new file mode 100644
index 0000000..bbafb98
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/domain-needed.html
@@ -0,0 +1,4 @@
+-D, --domain-needed
+Tells dnsmasq to never forward A or AAAA queries for plain names, without dots
+or domain parts, to upstream nameservers. If the name is not known
+from /etc/hosts or DHCP then a "not found" answer is returned.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/domain.html b/src/DnsmasqWebUI/wwwroot/option-help/domain.html
new file mode 100644
index 0000000..d32b0eb
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/domain.html
@@ -0,0 +1,43 @@
+-s, --domain=<domain>[[,<address range>[,local]]|<interface>]
+Specifies DNS domains for the DHCP server. Domains may be be given
+unconditionally (without the IP range) or for limited IP ranges. This has two effects;
+firstly it causes the DHCP server to return the domain to any hosts
+which request it, and secondly it sets the domain which it is legal
+for DHCP-configured hosts to claim. The intention is to constrain
+hostnames so that an untrusted host on the LAN cannot advertise
+its name via DHCP as e.g. "microsoft.com" and capture traffic not
+meant for it. If no domain suffix is specified, then any DHCP
+hostname with a domain part (ie with a period) will be disallowed
+and logged. If suffix is specified, then hostnames with a domain
+part are allowed, provided the domain part matches the suffix. In
+addition, when a suffix is set then hostnames without a domain
+part have the suffix added as an optional domain part. Eg on my network I can set
+--domain=thekelleys.org.uk
+
+and have a machine whose DHCP hostname is "laptop". The IP address for that machine is available from
+dnsmasq
+
+both as "laptop" and "laptop.thekelleys.org.uk". If the domain is
+given as "#" then the domain is read from the first "search" directive
+in /etc/resolv.conf (or equivalent).
+
+The address range can be of the form
+<ip address>,<ip address> or <ip address>/<netmask> or just a single
+<ip address>. See
+--dhcp-fqdn
+
+which can change the behaviour of dnsmasq with domains.
+
+If the address range is given as ip-address/network-size, then a
+additional flag "local" may be supplied which has the effect of adding
+--local declarations for forward and reverse DNS queries. Eg.
+--domain=thekelleys.org.uk,192.168.0.0/24,local
+
+is identical to
+--domain=thekelleys.org.uk,192.168.0.0/24
+--local=/thekelleys.org.uk/ --local=/0.168.192.in-addr.arpa/
+
+The address range can also be given as a network interface name, in which case
+all of the subnets currently assigned to the interface are used in matching the
+address. This allows hosts on different physical subnets to be given different
+domains in a way which updates automatically as the interface addresses change.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/dynamic-host.html b/src/DnsmasqWebUI/wwwroot/option-help/dynamic-host.html
new file mode 100644
index 0000000..5600ed6
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/dynamic-host.html
@@ -0,0 +1,6 @@
+--dynamic-host=<name>,[IPv4-address],[IPv6-address],<interface>
+Add A, AAAA and PTR records to the DNS in the same subnet as the specified interface. The address is derived from the network part of each address associated with the interface, and the host part from the specified address. For example
+--dynamic-host=example.com,0.0.0.8,eth0
+
+will, when eth0 has the address 192.168.78.x and netmask 255.255.255.0 give the
+name example.com an A record for 192.168.78.8. The same principle applies to IPv6 addresses. Note that if an interface has more than one address, more than one A or AAAA record will be created. The TTL of the records is always zero, and any changes to interface addresses will be immediately reflected in them.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/edns-packet-max.html b/src/DnsmasqWebUI/wwwroot/option-help/edns-packet-max.html
new file mode 100644
index 0000000..e0416f3
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/edns-packet-max.html
@@ -0,0 +1,4 @@
+-P, --edns-packet-max=<size>
+Specify the largest EDNS.0 UDP packet which is supported by the DNS
+forwarder. Defaults to 1232, which is the recommended size following the
+DNS flag day in 2020. Only increase if you know what you are doing.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/enable-dbus.html b/src/DnsmasqWebUI/wwwroot/option-help/enable-dbus.html
new file mode 100644
index 0000000..b238c8e
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/enable-dbus.html
@@ -0,0 +1,7 @@
+-1, --enable-dbus[=<service-name>]
+Allow dnsmasq configuration to be updated via DBus method calls. The
+configuration which can be changed is upstream DNS servers (and
+corresponding domains) and cache clear. Requires that dnsmasq has
+been built with DBus support. If the service name is given, dnsmasq
+provides service at that name, rather than the default which is
+uk.org.thekelleys.dnsmasq
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/enable-ra.html b/src/DnsmasqWebUI/wwwroot/option-help/enable-ra.html
new file mode 100644
index 0000000..2e21288
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/enable-ra.html
@@ -0,0 +1,18 @@
+--enable-ra
+Enable dnsmasq's IPv6 Router Advertisement feature. DHCPv6 doesn't
+handle complete network configuration in the same way as DHCPv4. Router
+discovery and (possibly) prefix discovery for autonomous address
+creation are handled by a different protocol. When DHCP is in use,
+only a subset of this is needed, and dnsmasq can handle it, using
+existing DHCP configuration to provide most data. When RA is enabled,
+dnsmasq will advertise a prefix for each --dhcp-range, with default
+router as the relevant link-local address on
+the machine running dnsmasq. By default, the "managed address" bits are set, and
+the "use SLAAC" bit is reset. This can be changed for individual
+subnets with the mode keywords described in
+--dhcp-range.
+
+RFC6106 DNS parameters are included in the advertisements. By default,
+the relevant link-local address of the machine running dnsmasq is sent
+as recursive DNS server. If provided, the DHCPv6 options dns-server and
+domain-search are used for the DNS server (RDNSS) and the domain search list (DNSSL).
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/enable-tftp.html b/src/DnsmasqWebUI/wwwroot/option-help/enable-tftp.html
new file mode 100644
index 0000000..9c8d7bb
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/enable-tftp.html
@@ -0,0 +1,6 @@
+--enable-tftp[=<interface>[,<interface>]]
+Enable the TFTP server function. This is deliberately limited to that
+needed to net-boot a client. Only reading is allowed; the tsize and
+blksize extensions are supported (tsize is only supported in octet
+mode). Without an argument, the TFTP service is provided to the same set of interfaces as DHCP service.
+If the list of interfaces is provided, that defines which interfaces receive TFTP service.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/enable-ubus.html b/src/DnsmasqWebUI/wwwroot/option-help/enable-ubus.html
new file mode 100644
index 0000000..ec8a8c4
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/enable-ubus.html
@@ -0,0 +1,10 @@
+--enable-ubus[=<service-name>]
+Enable dnsmasq UBus interface. It sends notifications via UBus on
+DHCPACK and DHCPRELEASE events. Furthermore it offers metrics
+and allows configuration of Linux connection track mark based filtering.
+When DNS query filtering based on Linux connection track marks is enabled
+UBus notifications are generated for each resolved or filtered DNS query.
+Requires that dnsmasq has been built with UBus support. If the service
+name is given, dnsmasq provides service at that namespace, rather than
+the default which is
+dnsmasq
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/except-interface.html b/src/DnsmasqWebUI/wwwroot/option-help/except-interface.html
new file mode 100644
index 0000000..00d386d
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/except-interface.html
@@ -0,0 +1,15 @@
+-I, --except-interface=<interface name>
+Do not listen on the specified interface. Note that the order of
+--listen-address
+--interface
+
+and
+--except-interface
+
+options does not matter and that
+--except-interface
+
+options always override the others. The comments about interface labels for
+--listen-address
+
+apply here.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/expand-hosts.html b/src/DnsmasqWebUI/wwwroot/option-help/expand-hosts.html
new file mode 100644
index 0000000..dac644e
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/expand-hosts.html
@@ -0,0 +1,4 @@
+-E, --expand-hosts
+Add the domain to simple names (without a period) in /etc/hosts
+in the same way as for DHCP-derived names. Note that this does not
+apply to domain names in cnames, PTR records, TXT records etc.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/fast-dns-retry.html b/src/DnsmasqWebUI/wwwroot/option-help/fast-dns-retry.html
new file mode 100644
index 0000000..546b7a5
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/fast-dns-retry.html
@@ -0,0 +1,10 @@
+--fast-dns-retry=[<initial retry delay in ms>[,<time to continue retries in ms>]]
+Under normal circumstances, dnsmasq relies on DNS clients to do retries; it
+does not generate timeouts itself. Setting this option
+instructs dnsmasq to generate its own retries starting after a delay
+which defaults to 1000ms. If the second parameter is given this controls
+how long the retries will continue for
+otherwise this defaults to 10000ms. Retries are repeated with exponential
+backoff. Using this option increases memory usage and
+network bandwidth. If not otherwise configured, this option is activated
+with the default parameters when --dnssec is set.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/filter-a.html b/src/DnsmasqWebUI/wwwroot/option-help/filter-a.html
new file mode 100644
index 0000000..9d14c9a
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/filter-a.html
@@ -0,0 +1,2 @@
+--filter-A
+Remove A records from answers. No IPv4 addresses will be returned.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/filter-aaaa.html b/src/DnsmasqWebUI/wwwroot/option-help/filter-aaaa.html
new file mode 100644
index 0000000..e210ce7
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/filter-aaaa.html
@@ -0,0 +1,2 @@
+--filter-AAAA
+Remove AAAA records from answers. No IPv6 addresses will be returned.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/filter-rr.html b/src/DnsmasqWebUI/wwwroot/option-help/filter-rr.html
new file mode 100644
index 0000000..fc348e8
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/filter-rr.html
@@ -0,0 +1,6 @@
+--filter-rr=<rrtype>[,<rrtype>...]
+Remove records of the specified type(s) from answers. The otherwise-nonsensical --filter-rr=ANY has
+a special meaning: it filters replies to queries for type ANY. Everything other than A, AAAA, MX and CNAME
+records are removed. Since ANY queries with forged source addresses can be used in DNS amplification attacks
+(replies to ANY queries can be large) this defangs such attacks, whilst still supporting the
+one remaining possible use of ANY queries. See RFC 8482 para 4.3 for details.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/filterwin2k.html b/src/DnsmasqWebUI/wwwroot/option-help/filterwin2k.html
new file mode 100644
index 0000000..df9050c
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/filterwin2k.html
@@ -0,0 +1,6 @@
+-f, --filterwin2k
+Later versions of windows make periodic DNS requests which don't get sensible answers from
+the public DNS and can cause problems by triggering dial-on-demand links. This flag turns on an option
+to filter such requests. The requests blocked are for records of type ANY
+where the requested name has underscores, to catch LDAP requests, and for
+all records of types SOA and SRV.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/group.html b/src/DnsmasqWebUI/wwwroot/option-help/group.html
new file mode 100644
index 0000000..a78d50d
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/group.html
@@ -0,0 +1,4 @@
+-g, --group=<groupname>
+Specify the group which dnsmasq will run
+as. The default is "dip", if available, to facilitate access to
+/etc/ppp/resolv.conf which is not normally world readable.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/host-record.html b/src/DnsmasqWebUI/wwwroot/option-help/host-record.html
new file mode 100644
index 0000000..675c9b3
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/host-record.html
@@ -0,0 +1,25 @@
+--host-record=<name>[,<name>....],[<IPv4-address>],[<IPv6-address>][,<TTL>]
+Add A, AAAA and PTR records to the DNS. This adds one or more names to
+the DNS with associated IPv4 (A) and IPv6 (AAAA) records. A name may
+appear in more than one
+--host-record
+
+and therefore be assigned more than one address. Only the first
+address creates a PTR record linking the address to the name. This is
+the same rule as is used reading hosts-files.
+--host-record
+
+options are considered to be read before host-files, so a name
+appearing there inhibits PTR-record creation if it appears in
+hosts-file also. Unlike hosts-files, names are not expanded, even when
+--expand-hosts
+
+is in effect. Short and long names may appear in the same
+--host-record,
+
+eg.
+--host-record=laptop,laptop.thekelleys.org,192.168.0.1,1234::100
+
+If the time-to-live is given, it overrides the default, which is zero
+or the value of --local-ttl. The value is a positive integer and gives
+the time-to-live in seconds.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/hostsdir.html b/src/DnsmasqWebUI/wwwroot/option-help/hostsdir.html
new file mode 100644
index 0000000..8483eff
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/hostsdir.html
@@ -0,0 +1,4 @@
+--hostsdir=<path>
+Read all the hosts files contained in the directory. New or changed files
+are read automatically and modified and deleted files have removed records
+automatically deleted.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/ignore-address.html b/src/DnsmasqWebUI/wwwroot/option-help/ignore-address.html
new file mode 100644
index 0000000..2604c2e
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/ignore-address.html
@@ -0,0 +1,5 @@
+--ignore-address=<ipaddr>[/prefix]
+Ignore replies to A or AAAA queries which include the specified address or subnet.
+No error is generated, dnsmasq simply continues to listen for another reply.
+This is useful to defeat blocking strategies which rely on quickly supplying a
+forged answer to a DNS request for certain domain, before the correct answer can arrive.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/interface-name.html b/src/DnsmasqWebUI/wwwroot/option-help/interface-name.html
new file mode 100644
index 0000000..8875549
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/interface-name.html
@@ -0,0 +1,13 @@
+--interface-name=<name>,<interface>[/4|/6]
+Return DNS records associating the name with the address(es) of
+the given interface. This flag specifies an A or AAAA record for the given
+name in the same way as an /etc/hosts line, except that the address is
+not constant, but taken from the given interface. The interface may be
+followed by "/4" or "/6" to specify that only IPv4 or IPv6 addresses
+of the interface should be used. If the interface is
+down, not configured or non-existent, an empty record is returned. The
+matching PTR record is also created, mapping the interface address to
+the name. More than one name may be associated with an interface
+address by repeating the flag; in that case the first instance is used
+for the reverse address-to-name mapping. Note that a name used in
+--interface-name may not appear in /etc/hosts.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/interface.html b/src/DnsmasqWebUI/wwwroot/option-help/interface.html
new file mode 100644
index 0000000..729bc0f
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/interface.html
@@ -0,0 +1,36 @@
+-i, --interface=<interface name>
+Listen only on the specified interface(s). Dnsmasq automatically adds
+the loopback (local) interface to the list of interfaces to use when
+the
+--interface
+
+option is used. If no
+--interface
+
+or
+--listen-address
+
+options are given dnsmasq listens on all available interfaces except any
+given in
+--except-interface
+
+options. On Linux, when
+--bind-interfaces
+
+or
+--bind-dynamic
+
+are in effect, IP alias interface labels (eg "eth1:0") are checked, rather than
+interface names. In the degenerate case when an interface has one address, this amounts to the same thing but when an interface has multiple addresses it
+allows control over which of those addresses are accepted.
+The same effect is achievable in default mode by using
+--listen-address.
+
+A simple wildcard, consisting of a trailing '*',
+can be used in
+--interface
+
+and
+--except-interface
+
+options.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/ipset.html b/src/DnsmasqWebUI/wwwroot/option-help/ipset.html
new file mode 100644
index 0000000..85f8455
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/ipset.html
@@ -0,0 +1,11 @@
+--ipset=/<domain>[/<domain>...]/<ipset>[,<ipset>...]
+Places the resolved IP addresses of queries for one or more domains in
+the specified Netfilter IP set. If multiple setnames are given, then the
+addresses are placed in each of them, subject to the limitations of an
+IP set (IPv4 addresses cannot be stored in an IPv6 IP set and vice
+versa). Domains and subdomains are matched in the same way as
+--address.
+These IP sets must already exist. See
+ipset(8)
+
+for more details.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/keep-in-foreground.html b/src/DnsmasqWebUI/wwwroot/option-help/keep-in-foreground.html
new file mode 100644
index 0000000..b802f0f
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/keep-in-foreground.html
@@ -0,0 +1,4 @@
+-k, --keep-in-foreground
+Do not go into the background at startup but otherwise run as
+normal. This is intended for use when dnsmasq is run under daemontools
+or launchd.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/leasefile-ro.html b/src/DnsmasqWebUI/wwwroot/option-help/leasefile-ro.html
new file mode 100644
index 0000000..f80bb08
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/leasefile-ro.html
@@ -0,0 +1,14 @@
+-9, --leasefile-ro
+Completely suppress use of the lease database file. The file will not
+be created, read, or written. Change the way the lease-change
+script (if one is provided) is called, so that the lease database may
+be maintained in external storage by the script. In addition to the
+invocations given in
+--dhcp-script
+
+the lease-change script is called once, at dnsmasq startup, with the
+single argument "init". When called like this the script should write
+the saved state of the lease database, in dnsmasq leasefile format, to
+stdout and exit with zero exit code. Setting this
+option also forces the leasechange script to be called on changes
+to the client-id and lease length and expiry time.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/listen-address.html b/src/DnsmasqWebUI/wwwroot/option-help/listen-address.html
new file mode 100644
index 0000000..d9f5b86
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/listen-address.html
@@ -0,0 +1,20 @@
+-a, --listen-address=<ipaddr>
+Listen on the given IP address(es). Both
+--interface
+
+and
+--listen-address
+
+options may be given, in which case the set of both interfaces and
+addresses is used. Note that if no
+--interface
+
+option is given, but
+--listen-address
+
+is, dnsmasq will not automatically listen on the loopback
+interface. To achieve this, its IP address, 127.0.0.1, must be
+explicitly given as a
+--listen-address
+
+option.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/local-service.html b/src/DnsmasqWebUI/wwwroot/option-help/local-service.html
new file mode 100644
index 0000000..f1cb9c8
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/local-service.html
@@ -0,0 +1,9 @@
+--local-service[=net|host]
+Without parameter or with net parameter, restricts service to connected network.
+Accept DNS queries only from hosts whose address is on a local subnet,
+ie a subnet for which an interface exists on the server. With host parameter, listens
+only on lo interface and accepts queries from localhost only. This option
+only has effect if there are no --interface, --except-interface,
+--listen-address or --auth-server options. It is intended to be set as
+a default on installation, to allow unconfigured installations to be
+useful but also safe from being used for DNS amplification attacks.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/local-ttl.html b/src/DnsmasqWebUI/wwwroot/option-help/local-ttl.html
new file mode 100644
index 0000000..e9b594b
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/local-ttl.html
@@ -0,0 +1,8 @@
+-T, --local-ttl=<time>
+When replying with information from /etc/hosts or configuration or the DHCP leases
+file dnsmasq by default sets the time-to-live field to zero, meaning
+that the requester should not itself cache the information. This is
+the correct thing to do in almost all situations. This option allows a
+time-to-live (in seconds) to be given for these replies. This will
+reduce the load on the server at the expense of clients using stale
+data under some circumstances.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/local.html b/src/DnsmasqWebUI/wwwroot/option-help/local.html
new file mode 100644
index 0000000..3e877cb
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/local.html
@@ -0,0 +1,78 @@
+-S, --local, --server=[/[<domain>]/[domain/]][<server>[#<port>]][@<interface>][@<source-ip>[#<port>]]
+Specify upstream servers directly. Setting this flag does
+not suppress reading of /etc/resolv.conf, use --no-resolv to do that. If one or more
+optional domains are given, that server is used only for those domains
+and they are queried only using the specified server. This is
+intended for private nameservers: if you have a nameserver on your
+network which deals with names of the form
+xxx.internal.thekelleys.org.uk at 192.168.1.1 then giving the flag
+--server=/internal.thekelleys.org.uk/192.168.1.1
+
+will send all queries for
+internal machines to that nameserver, everything else will go to the
+servers in /etc/resolv.conf. An empty domain specification,
+//
+
+has the special meaning of "unqualified names only" ie names without any
+dots in them. A non-standard port may be specified as
+part of the IP
+address using a # character.
+More than one --server flag is allowed, with
+repeated domain or ipaddr parts as required.
+
+More specific domains take precedence over less specific domains, so:
+--server=/google.com/1.2.3.4
+--server=/www.google.com/2.3.4.5
+
+will send queries for google.com and gmail.google.com to 1.2.3.4, but www.google.com
+will go to 2.3.4.5
+
+Matching of domains is normally done on complete labels, so /google.com/ matches google.com and www.google.com
+but NOT supergoogle.com. This can be overridden with a * at the start of a pattern only: /*google.com/
+will match google.com and www.google.com AND supergoogle.com. The non-wildcard form has priority, so
+if /google.com/ and /*google.com/ are both specified then google.com and www.google.com will match /google.com/
+and /*google.com/ will only match supergoogle.com.
+
+For historical reasons, the pattern /.google.com/ is equivalent to /google.com/ if you wish to match any subdomain
+of google.com but NOT google.com itself, use /*.google.com/
+
+The special server address '#' means, "use the standard servers", so
+--server=/google.com/1.2.3.4
+--server=/www.google.com/#
+
+will send queries for google.com and its subdomains to 1.2.3.4, except www.google.com (and its subdomains) which will
+be forwarded as usual.
+
+Also permitted is a -S
+flag which gives a domain but no IP address; this tells dnsmasq that
+a domain is local and it may answer queries from /etc/hosts or DHCP
+but should never forward queries on that domain to any upstream
+servers.
+--local
+
+is a synonym for
+--server
+
+to make configuration files clearer in this case.
+
+IPv6 addresses may include an %interface scope-id, eg
+fe80::202:a412:4512:7bbf%eth0.
+
+The optional string after the @ character tells dnsmasq how to set the source of
+the queries to this nameserver. It can either be an ip-address, an interface
+name or both. The ip-address should belong to the machine on which dnsmasq is
+running, otherwise this server line will be logged and then ignored. If an
+interface name is given, then queries to the server will be forced via that
+interface; if an ip-address is given then the source address of the queries will
+be set to that address; and if both are given then a combination of ip-address
+and interface name will be used to steer requests to the server.
+The query-port flag is ignored for any servers which have a
+source address specified but the port may be specified directly as
+part of the source address. Forcing queries to an interface is not
+implemented on all platforms supported by dnsmasq.
+
+Upstream servers may be specified with a hostname rather than an IP address.
+In this case, dnsmasq will try to use the system resolver to get the IP address
+of a server during startup. If name resolution fails, starting dnsmasq fails, too.
+If the system's configuration is such that the system resolver sends DNS queries
+through the dnsmasq instance which is starting up then this will time-out and fail.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/localise-queries.html b/src/DnsmasqWebUI/wwwroot/option-help/localise-queries.html
new file mode 100644
index 0000000..2a67c51
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/localise-queries.html
@@ -0,0 +1,10 @@
+-y, --localise-queries
+Return answers to DNS queries from /etc/hosts and --interface-name and --dynamic-host which depend on the interface over which the query was
+received. If a name has more than one address associated with
+it, and at least one of those addresses is on the same subnet as the
+interface to which the query was sent, then return only the
+address(es) on that subnet and return all the available addresses otherwise.
+This allows for a server to have multiple
+addresses in /etc/hosts corresponding to each of its interfaces, and
+hosts will get the correct address based on which network they are
+attached to. Currently this facility is limited to IPv4.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/log-async.html b/src/DnsmasqWebUI/wwwroot/option-help/log-async.html
new file mode 100644
index 0000000..ef96f75
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/log-async.html
@@ -0,0 +1,10 @@
+--log-async[=<lines>]
+Enable asynchronous logging and optionally set the limit on the
+number of lines
+which will be queued by dnsmasq when writing to the syslog is slow.
+Dnsmasq can log asynchronously: this
+allows it to continue functioning without being blocked by syslog, and
+allows syslog to use dnsmasq for DNS queries without risking deadlock.
+If the queue of log-lines becomes full, dnsmasq will log the
+overflow, and the number of messages lost. The default queue length is
+5, a sane value would be 5-25, and a maximum limit of 100 is imposed.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/log-debug.html b/src/DnsmasqWebUI/wwwroot/option-help/log-debug.html
new file mode 100644
index 0000000..889b60a
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/log-debug.html
@@ -0,0 +1,2 @@
+--log-debug
+Enable extra logging intended for debugging rather than information.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/log-dhcp.html b/src/DnsmasqWebUI/wwwroot/option-help/log-dhcp.html
new file mode 100644
index 0000000..7822ddb
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/log-dhcp.html
@@ -0,0 +1,3 @@
+--log-dhcp
+Extra logging for DHCP: log all the options sent to DHCP clients and
+the tags used to determine them.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/log-facility.html b/src/DnsmasqWebUI/wwwroot/option-help/log-facility.html
new file mode 100644
index 0000000..2f8e22f
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/log-facility.html
@@ -0,0 +1,11 @@
+-8, --log-facility=<facility>
+Set the facility to which dnsmasq will send syslog entries, this
+defaults to DAEMON, and to LOCAL0 when debug mode is in operation. If
+the facility given contains at least one '/' character, it is taken to
+be a filename, and dnsmasq logs to the given file, instead of
+syslog. If the facility is '-' then dnsmasq logs to stderr.
+(Errors whilst reading configuration will still go to syslog,
+but all output from a successful startup, and all output whilst
+running, will go exclusively to the file.) When logging to a file,
+dnsmasq will close and reopen the file when it receives SIGUSR2. This
+allows the log file to be rotated without stopping dnsmasq.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/log-queries.html b/src/DnsmasqWebUI/wwwroot/option-help/log-queries.html
new file mode 100644
index 0000000..9ec049d
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/log-queries.html
@@ -0,0 +1,7 @@
+-q, --log-queries
+Log the results of DNS queries handled by dnsmasq. Enable a full cache dump on receipt of SIGUSR1. If the argument "extra" is supplied, ie
+--log-queries=extra
+
+then the log has extra information at the start of each line.
+This consists of a serial number which ties together the log lines associated with an individual query, and the IP address of the requestor. If the argument "proto" is supplied, this shows everything that "extra" does and also the network protocol used to communicate the queries. Logging of only queries to the authoritative server can be configured with
+--log-queries=auth
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/max-cache-ttl.html b/src/DnsmasqWebUI/wwwroot/option-help/max-cache-ttl.html
new file mode 100644
index 0000000..f155521
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/max-cache-ttl.html
@@ -0,0 +1,2 @@
+--max-cache-ttl=<time>
+Set a maximum TTL value for entries in the cache.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/max-port.html b/src/DnsmasqWebUI/wwwroot/option-help/max-port.html
new file mode 100644
index 0000000..c7d6110
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/max-port.html
@@ -0,0 +1,5 @@
+--max-port=<port>
+Use ports lower than that given as source for outbound DNS queries.
+Dnsmasq picks random ports as source for outbound queries:
+when this option is given, the ports used will always be lower
+than that specified. Useful for systems behind firewalls.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/max-ttl.html b/src/DnsmasqWebUI/wwwroot/option-help/max-ttl.html
new file mode 100644
index 0000000..044c40f
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/max-ttl.html
@@ -0,0 +1,5 @@
+--max-ttl=<time>
+Set a maximum TTL value that will be handed out to clients. The specified
+maximum TTL will be given to clients instead of the true TTL value if it is
+lower. The true TTL value is however kept in the cache to avoid flooding
+the upstream DNS servers.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/min-cache-ttl.html b/src/DnsmasqWebUI/wwwroot/option-help/min-cache-ttl.html
new file mode 100644
index 0000000..918d4dd
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/min-cache-ttl.html
@@ -0,0 +1,5 @@
+--min-cache-ttl=<time>
+Extend short TTL values to the time given when caching them. Note that
+artificially extending TTL values is in general a bad idea, do not do it
+unless you have a good reason, and understand what you are doing.
+Dnsmasq limits the value of this option to one hour, unless recompiled.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/min-port.html b/src/DnsmasqWebUI/wwwroot/option-help/min-port.html
new file mode 100644
index 0000000..2057002
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/min-port.html
@@ -0,0 +1,6 @@
+--min-port=<port>
+Do not use ports less than that given as source for outbound DNS
+queries. Dnsmasq picks random ports as source for outbound queries:
+when this option is given, the ports used will always be larger
+than that specified. Useful for systems behind firewalls. If not specified,
+defaults to 1024.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/mx-host.html b/src/DnsmasqWebUI/wwwroot/option-help/mx-host.html
new file mode 100644
index 0000000..90dcbf8
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/mx-host.html
@@ -0,0 +1,8 @@
+-m, --mx-host=<mx name>[[,<hostname>],<preference>]
+Return an MX record named <mx name> pointing to the given hostname (if
+given), or
+the host specified in the --mx-target switch
+or, if that switch is not given, the host on which dnsmasq
+is running. The default is useful for directing mail from systems on a LAN
+to a central server. The preference value is optional, and defaults to
+1 if not given. More than one MX record may be given for a host.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/mx-target.html b/src/DnsmasqWebUI/wwwroot/option-help/mx-target.html
new file mode 100644
index 0000000..41ebe52
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/mx-target.html
@@ -0,0 +1,5 @@
+-t, --mx-target=<hostname>
+Specify the default target for the MX record returned by dnsmasq. See
+--mx-host. If --mx-target is given, but not --mx-host, then dnsmasq
+returns a MX record containing the MX target for MX queries on the
+hostname of the machine on which dnsmasq is running.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/naptr-record.html b/src/DnsmasqWebUI/wwwroot/option-help/naptr-record.html
new file mode 100644
index 0000000..d5e8afb
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/naptr-record.html
@@ -0,0 +1,2 @@
+--naptr-record=<name>,<order>,<preference>,<flags>,<service>,<regexp>[,<replacement>]
+Return an NAPTR DNS record, as specified in RFC3403.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/neg-ttl.html b/src/DnsmasqWebUI/wwwroot/option-help/neg-ttl.html
new file mode 100644
index 0000000..8a14e16
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/neg-ttl.html
@@ -0,0 +1,7 @@
+--neg-ttl=<time>
+Negative replies from upstream servers normally contain time-to-live
+information in SOA records which dnsmasq uses for caching. If the
+replies from upstream servers omit this information, dnsmasq does not
+cache the reply. This option gives a default value for time-to-live
+(in seconds) which dnsmasq uses to cache negative replies even in
+the absence of an SOA record.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/nftset.html b/src/DnsmasqWebUI/wwwroot/option-help/nftset.html
new file mode 100644
index 0000000..b748e15
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/nftset.html
@@ -0,0 +1,9 @@
+--nftset=/<domain>[/<domain>...]/[(6|4)#[<family>#]<table>#<set>[,[(6|4)#[<family>#]<table>#<set>]...]
+Similar to the --ipset option, but accepts one or more nftables
+sets to add IP addresses into.
+These sets must already exist. See
+nft(8)
+
+for more details. The family, table and set are passed directly to the nft. If the spec starts with 4# or 6# then
+only A or AAAA records respectively are added to the set. Since an nftset can hold only IPv4 or IPv6 addresses, this
+avoids errors being logged for addresses of the wrong type.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/no-daemon.html b/src/DnsmasqWebUI/wwwroot/option-help/no-daemon.html
new file mode 100644
index 0000000..8103435
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/no-daemon.html
@@ -0,0 +1,7 @@
+-d, --no-daemon
+Debug mode: don't fork to the background, don't write a pid file,
+don't change user id, generate a complete cache dump on receipt on
+SIGUSR1, log to stderr as well as syslog, don't fork new processes
+to handle TCP queries. Note that this option is for use in debugging
+only, to stop dnsmasq daemonising in production, use
+--keep-in-foreground.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/no-dhcp-interface.html b/src/DnsmasqWebUI/wwwroot/option-help/no-dhcp-interface.html
new file mode 100644
index 0000000..9087874
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/no-dhcp-interface.html
@@ -0,0 +1,2 @@
+-2, --no-dhcp-interface=<interface name>
+Do not provide DHCP, TFTP or router advertisement on the specified interface, but do provide DNS service.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/no-dhcpv4-interface.html b/src/DnsmasqWebUI/wwwroot/option-help/no-dhcpv4-interface.html
new file mode 100644
index 0000000..0f57588
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/no-dhcpv4-interface.html
@@ -0,0 +1,2 @@
+--no-dhcpv4-interface=<interface name>
+Disable only IPv4 DHCP on the specified interface.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/no-dhcpv6-interface.html b/src/DnsmasqWebUI/wwwroot/option-help/no-dhcpv6-interface.html
new file mode 100644
index 0000000..5047b94
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/no-dhcpv6-interface.html
@@ -0,0 +1,2 @@
+--no-dhcpv6-interface=<interface name>
+Disable IPv6 DHCP and router advertisement on the specified interface.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/no-hosts.html b/src/DnsmasqWebUI/wwwroot/option-help/no-hosts.html
new file mode 100644
index 0000000..6bc6c98
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/no-hosts.html
@@ -0,0 +1,2 @@
+-h, --no-hosts
+Don't read the hostnames in /etc/hosts.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/no-negcache.html b/src/DnsmasqWebUI/wwwroot/option-help/no-negcache.html
new file mode 100644
index 0000000..d560f3a
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/no-negcache.html
@@ -0,0 +1,4 @@
+-N, --no-negcache
+Disable negative caching. Negative caching allows dnsmasq to remember
+"no such domain" answers from upstream nameservers and answer
+identical queries without forwarding them again.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/no-poll.html b/src/DnsmasqWebUI/wwwroot/option-help/no-poll.html
new file mode 100644
index 0000000..bebd3fb
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/no-poll.html
@@ -0,0 +1,2 @@
+-n, --no-poll
+Don't poll /etc/resolv.conf for changes.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/no-resolv.html b/src/DnsmasqWebUI/wwwroot/option-help/no-resolv.html
new file mode 100644
index 0000000..8ef2a12
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/no-resolv.html
@@ -0,0 +1,3 @@
+-R, --no-resolv
+Don't read /etc/resolv.conf. Get upstream servers only from the command
+line or the dnsmasq configuration file.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/pid-file.html b/src/DnsmasqWebUI/wwwroot/option-help/pid-file.html
new file mode 100644
index 0000000..66604cf
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/pid-file.html
@@ -0,0 +1,2 @@
+-x, --pid-file=<path>
+Specify an alternate path for dnsmasq to record its process-id in. Normally /var/run/dnsmasq.pid.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/port-limit.html b/src/DnsmasqWebUI/wwwroot/option-help/port-limit.html
new file mode 100644
index 0000000..52d8f88
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/port-limit.html
@@ -0,0 +1,7 @@
+--port-limit=<#ports>
+By default, when sending a query via random ports to multiple upstream servers or
+retrying a query dnsmasq will use a single random port for all the tries/retries.
+This option allows a larger number of ports to be used, which can increase robustness
+in certain network configurations. Note that increasing this to more than
+two or three can have security and resource implications and should only
+be done with understanding of those.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/port.html b/src/DnsmasqWebUI/wwwroot/option-help/port.html
new file mode 100644
index 0000000..2f47a59
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/port.html
@@ -0,0 +1,3 @@
+-p, --port=<port>
+Listen on <port> instead of the standard DNS port (53). Setting this
+to zero completely disables DNS function, leaving only DHCP and/or TFTP.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/proxy-dnssec.html b/src/DnsmasqWebUI/wwwroot/option-help/proxy-dnssec.html
new file mode 100644
index 0000000..cd4a50a
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/proxy-dnssec.html
@@ -0,0 +1,7 @@
+--proxy-dnssec
+Copy the DNSSEC Authenticated Data bit from upstream servers to downstream clients. This is an
+alternative to having dnsmasq validate DNSSEC, but it depends on the security of the network between
+dnsmasq and the upstream servers, and the trustworthiness of the upstream servers. Note that caching the
+Authenticated Data bit correctly in all cases is not technically possible. If the AD bit is to be relied upon
+when using this option, then the cache should be disabled using --cache-size=0. In most cases, enabling DNSSEC validation
+within dnsmasq is a better option. See --dnssec for details.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/ptr-record.html b/src/DnsmasqWebUI/wwwroot/option-help/ptr-record.html
new file mode 100644
index 0000000..3e71c03
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/ptr-record.html
@@ -0,0 +1,2 @@
+--ptr-record=<name>[,<target>]
+Return a PTR DNS record.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/pxe-prompt.html b/src/DnsmasqWebUI/wwwroot/option-help/pxe-prompt.html
new file mode 100644
index 0000000..5d86382
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/pxe-prompt.html
@@ -0,0 +1,35 @@
+--pxe-prompt=[tag:<tag>,]<prompt>[,<timeout>]
+Setting this provides a prompt to be displayed after PXE boot. If the
+timeout is given then after the
+timeout has elapsed with no keyboard input, the first available menu
+option will be automatically executed. If the timeout is zero then the first available menu
+item will be executed immediately. If
+--pxe-prompt
+
+is omitted the system will wait for user input if there are multiple
+items in the menu, but boot immediately if
+there is only one. See
+--pxe-service
+
+for details of menu items.
+
+Dnsmasq supports PXE "proxy-DHCP", in this case another DHCP server on
+the network is responsible for allocating IP addresses, and dnsmasq
+simply provides the information given in
+--pxe-prompt
+
+and
+--pxe-service
+
+to allow netbooting. This mode is enabled using the
+proxy
+
+keyword in
+--dhcp-range.
+
+If the "other" DHCP server is on a remote network, it is
+possible, and useful, to configure dnsmasq as both a PXE proxy-DHCP server
+and a DHCP relay to the remote DHCP server. See
+--dhcp-relay
+
+for details. PXE is only supported over IPv4 at this time.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/pxe-service.html b/src/DnsmasqWebUI/wwwroot/option-help/pxe-service.html
new file mode 100644
index 0000000..ab43f92
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/pxe-service.html
@@ -0,0 +1,32 @@
+--pxe-service=[tag:<tag>,]<CSA>,<menu text>[,<basename>|<bootservicetype>][,<server address>|<server_name>]
+Most uses of PXE boot-ROMS simply allow the PXE
+system to obtain an IP address and then download the file specified by
+--dhcp-boot
+
+and execute it. However the PXE system is capable of more complex
+functions when supported by a suitable DHCP server.
+
+This specifies a boot option which may appear in a PXE boot menu. <CSA> is
+client system type, only services of the correct type will appear in a
+menu. The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
+Intel_Lean_Client, IA32_EFI, x86-64_EFI, Xscale_EFI, BC_EFI, ARM32_EFI and ARM64_EFI; an
+integer may be used for other types. The
+parameter after the menu text may be a file name, in which case dnsmasq acts as a
+boot server and directs the PXE client to download the file by TFTP,
+either from itself (
+--enable-tftp
+
+must be set for this to work) or another TFTP server if the final server
+address/name is given.
+Note that the "layer"
+suffix (normally ".0") is supplied by PXE, and need not be added to
+the basename. Alternatively, the basename may be a filename, complete with suffix, in which case
+no layer suffix is added. If an integer boot service type, rather than a basename
+is given, then the PXE client will search for a
+suitable boot service for that type on the network. This search may be done
+by broadcast, or direct to a server if its IP address/name is provided.
+If no boot service type or filename is provided (or a boot service type of 0 is specified)
+then the menu entry will abort the net boot procedure and
+continue booting from local media. The server address can be given as a domain
+name which is looked up in /etc/hosts. This name can be associated in
+/etc/hosts with multiple IP addresses, which are used round-robin.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/query-port.html b/src/DnsmasqWebUI/wwwroot/option-help/query-port.html
new file mode 100644
index 0000000..f25bba8
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/query-port.html
@@ -0,0 +1,7 @@
+-Q, --query-port=<query_port>
+Send outbound DNS queries from, and listen for their replies on, the
+specific UDP port <query_port> instead of using random ports. NOTE
+that using this option will make dnsmasq less secure against DNS
+spoofing attacks but it may be faster and use less resources. Setting this option
+to zero makes dnsmasq use a single port allocated to it by the
+OS: this was the default behaviour in versions prior to 2.43.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/ra-param.html b/src/DnsmasqWebUI/wwwroot/option-help/ra-param.html
new file mode 100644
index 0000000..5f3fc09
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/ra-param.html
@@ -0,0 +1,20 @@
+--ra-param=<interface>,[mtu:<integer>|<interface>|off,][high,|low,]<ra-interval>[,<router lifetime>]
+Set non-default values for router advertisements sent via an
+interface. The priority field for the router may be altered from the
+default of medium with eg
+--ra-param=eth0,high.
+
+The interval between router advertisements may be set (in seconds) with
+--ra-param=eth0,60.
+
+The lifetime of the route may be changed or set to zero, which allows
+a router to advertise prefixes but not a route via itself.
+--ra-param=eth0,0,0
+
+(A value of zero for the interval means the default value.) All four parameters may be set at once.
+--ra-param=eth0,mtu:1280,low,60,1200
+
+The interface field may include a wildcard.
+
+The mtu: parameter may be an arbitrary interface name, in which case the MTU value for that interface is used. This is useful
+for (eg) advertising the MTU of a WAN interface on the other interfaces of a router.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/read-ethers.html b/src/DnsmasqWebUI/wwwroot/option-help/read-ethers.html
new file mode 100644
index 0000000..28107ca
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/read-ethers.html
@@ -0,0 +1,9 @@
+-Z, --read-ethers
+Read /etc/ethers for information about hosts for the DHCP server. The
+format of /etc/ethers is a hardware address, followed by either a
+hostname or dotted-quad IP address. When read by dnsmasq these lines
+have exactly the same effect as
+--dhcp-host
+
+options containing the same information. /etc/ethers is re-read when
+dnsmasq receives SIGHUP. IPv6 addresses are NOT read from /etc/ethers.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/rebind-domain-ok.html b/src/DnsmasqWebUI/wwwroot/option-help/rebind-domain-ok.html
new file mode 100644
index 0000000..aebc4a3
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/rebind-domain-ok.html
@@ -0,0 +1,5 @@
+--rebind-domain-ok=[<domain>]|[[/<domain>/[<domain>/]
+Do not detect and block dns-rebind on queries to these domains. The
+argument may be either a single domain, or multiple domains surrounded
+by '/', like the --server syntax, eg.
+--rebind-domain-ok=/domain1/domain2/domain3/
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/rebind-localhost-ok.html b/src/DnsmasqWebUI/wwwroot/option-help/rebind-localhost-ok.html
new file mode 100644
index 0000000..9e083f7
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/rebind-localhost-ok.html
@@ -0,0 +1,4 @@
+--rebind-localhost-ok
+Exempt 127.0.0.0/8 and ::1 from rebinding checks. This address range is
+returned by realtime black hole servers, so blocking it may disable
+these services.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/resolv-file.html b/src/DnsmasqWebUI/wwwroot/option-help/resolv-file.html
new file mode 100644
index 0000000..108962c
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/resolv-file.html
@@ -0,0 +1,10 @@
+-r, --resolv-file=<file>
+Read the IP addresses of the upstream nameservers from <file>, instead of
+/etc/resolv.conf. For the format of this file see
+resolv.conf(5).
+
+The only lines relevant to dnsmasq are nameserver ones. Dnsmasq can
+be told to poll more than one resolv.conf file, the first file name specified
+overrides the default, subsequent ones add to the list. This is only
+allowed when polling; the file with the currently latest modification
+time is the one used.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/rev-server.html b/src/DnsmasqWebUI/wwwroot/option-help/rev-server.html
new file mode 100644
index 0000000..8604554
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/rev-server.html
@@ -0,0 +1,11 @@
+--rev-server=<ip-address>[/<prefix-len>][,<server>][#<port>][@<interface>][@<source-ip>[#<port>]]
+This is functionally the same as
+--server,
+
+but provides some syntactic sugar to make specifying address-to-name queries easier. For example
+--rev-server=1.2.3.0/24,192.168.0.1
+
+is exactly equivalent to
+--server=/3.2.1.in-addr.arpa/192.168.0.1
+
+Allowed prefix lengths are 1-32 (IPv4) and 1-128 (IPv6). If the prefix length is omitted, dnsmasq substitutes either 32 (IPv4) or 128 (IPv6).
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/server.html b/src/DnsmasqWebUI/wwwroot/option-help/server.html
new file mode 100644
index 0000000..3e877cb
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/server.html
@@ -0,0 +1,78 @@
+-S, --local, --server=[/[<domain>]/[domain/]][<server>[#<port>]][@<interface>][@<source-ip>[#<port>]]
+Specify upstream servers directly. Setting this flag does
+not suppress reading of /etc/resolv.conf, use --no-resolv to do that. If one or more
+optional domains are given, that server is used only for those domains
+and they are queried only using the specified server. This is
+intended for private nameservers: if you have a nameserver on your
+network which deals with names of the form
+xxx.internal.thekelleys.org.uk at 192.168.1.1 then giving the flag
+--server=/internal.thekelleys.org.uk/192.168.1.1
+
+will send all queries for
+internal machines to that nameserver, everything else will go to the
+servers in /etc/resolv.conf. An empty domain specification,
+//
+
+has the special meaning of "unqualified names only" ie names without any
+dots in them. A non-standard port may be specified as
+part of the IP
+address using a # character.
+More than one --server flag is allowed, with
+repeated domain or ipaddr parts as required.
+
+More specific domains take precedence over less specific domains, so:
+--server=/google.com/1.2.3.4
+--server=/www.google.com/2.3.4.5
+
+will send queries for google.com and gmail.google.com to 1.2.3.4, but www.google.com
+will go to 2.3.4.5
+
+Matching of domains is normally done on complete labels, so /google.com/ matches google.com and www.google.com
+but NOT supergoogle.com. This can be overridden with a * at the start of a pattern only: /*google.com/
+will match google.com and www.google.com AND supergoogle.com. The non-wildcard form has priority, so
+if /google.com/ and /*google.com/ are both specified then google.com and www.google.com will match /google.com/
+and /*google.com/ will only match supergoogle.com.
+
+For historical reasons, the pattern /.google.com/ is equivalent to /google.com/ if you wish to match any subdomain
+of google.com but NOT google.com itself, use /*.google.com/
+
+The special server address '#' means, "use the standard servers", so
+--server=/google.com/1.2.3.4
+--server=/www.google.com/#
+
+will send queries for google.com and its subdomains to 1.2.3.4, except www.google.com (and its subdomains) which will
+be forwarded as usual.
+
+Also permitted is a -S
+flag which gives a domain but no IP address; this tells dnsmasq that
+a domain is local and it may answer queries from /etc/hosts or DHCP
+but should never forward queries on that domain to any upstream
+servers.
+--local
+
+is a synonym for
+--server
+
+to make configuration files clearer in this case.
+
+IPv6 addresses may include an %interface scope-id, eg
+fe80::202:a412:4512:7bbf%eth0.
+
+The optional string after the @ character tells dnsmasq how to set the source of
+the queries to this nameserver. It can either be an ip-address, an interface
+name or both. The ip-address should belong to the machine on which dnsmasq is
+running, otherwise this server line will be logged and then ignored. If an
+interface name is given, then queries to the server will be forced via that
+interface; if an ip-address is given then the source address of the queries will
+be set to that address; and if both are given then a combination of ip-address
+and interface name will be used to steer requests to the server.
+The query-port flag is ignored for any servers which have a
+source address specified but the port may be specified directly as
+part of the source address. Forcing queries to an interface is not
+implemented on all platforms supported by dnsmasq.
+
+Upstream servers may be specified with a hostname rather than an IP address.
+In this case, dnsmasq will try to use the system resolver to get the IP address
+of a server during startup. If name resolution fails, starting dnsmasq fails, too.
+If the system's configuration is such that the system resolver sends DNS queries
+through the dnsmasq instance which is starting up then this will time-out and fail.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/srv-host.html b/src/DnsmasqWebUI/wwwroot/option-help/srv-host.html
new file mode 100644
index 0000000..641c08c
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/srv-host.html
@@ -0,0 +1,11 @@
+-W, --srv-host=<_service>.<_prot>[.<domain>],[<target>[,<port>[,<priority>[,<weight>]]]]
+Return a SRV DNS record. See RFC2782 for details. If not supplied, the
+domain defaults to that given by
+--domain.
+
+The default for the target domain is empty, and the default for port
+is one and the defaults for
+weight and priority are zero. Be careful if transposing data from BIND
+zone files: the port, weight and priority numbers are in a different
+order. More than one SRV record for a given service/domain is allowed,
+all that match are returned.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/stop-dns-rebind.html b/src/DnsmasqWebUI/wwwroot/option-help/stop-dns-rebind.html
new file mode 100644
index 0000000..10a7664
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/stop-dns-rebind.html
@@ -0,0 +1,6 @@
+--stop-dns-rebind
+Reject (and log) addresses from upstream nameservers which are in the
+private ranges. This blocks an attack where a browser behind a
+firewall is used to probe machines on the local network. For IPv6, the
+private range covers the IPv4-mapped addresses in private space plus
+all link-local (LL) and site-local (ULA) addresses.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/strict-order.html b/src/DnsmasqWebUI/wwwroot/option-help/strict-order.html
new file mode 100644
index 0000000..0c764b9
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/strict-order.html
@@ -0,0 +1,5 @@
+-o, --strict-order
+By default, dnsmasq will send queries to any of the upstream servers
+it knows about and tries to favour servers that are known to
+be up. Setting this flag forces dnsmasq to try each query with each
+server strictly in the order they appear in /etc/resolv.conf
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/tftp-no-blocksize.html b/src/DnsmasqWebUI/wwwroot/option-help/tftp-no-blocksize.html
new file mode 100644
index 0000000..cc3cb0c
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/tftp-no-blocksize.html
@@ -0,0 +1,4 @@
+--tftp-no-blocksize
+Stop the TFTP server from negotiating the "blocksize" option with a
+client. Some buggy clients request this option but then behave badly
+when it is granted.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/tftp-no-fail.html b/src/DnsmasqWebUI/wwwroot/option-help/tftp-no-fail.html
new file mode 100644
index 0000000..ad6b69a
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/tftp-no-fail.html
@@ -0,0 +1,2 @@
+--tftp-no-fail
+Do not abort startup if specified tftp root directories are inaccessible.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/tftp-root.html b/src/DnsmasqWebUI/wwwroot/option-help/tftp-root.html
new file mode 100644
index 0000000..45cd8a9
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/tftp-root.html
@@ -0,0 +1,7 @@
+--tftp-root=<directory>[,<interface>]
+Look for files to transfer using TFTP relative to the given
+directory. When this is set, TFTP paths which include ".." are
+rejected, to stop clients getting outside the specified root.
+Absolute paths (starting with /) are allowed, but they must be within
+the tftp-root. If the optional interface argument is given, the
+directory is only used for TFTP requests via that interface.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/tftp-secure.html b/src/DnsmasqWebUI/wwwroot/option-help/tftp-secure.html
new file mode 100644
index 0000000..835cc97
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/tftp-secure.html
@@ -0,0 +1,10 @@
+--tftp-secure
+Enable TFTP secure mode: without this, any file which is readable by
+the dnsmasq process under normal unix access-control rules is
+available via TFTP. When the --tftp-secure flag is given, only files
+owned by the user running the dnsmasq process are accessible. If
+dnsmasq is being run as root, different rules apply: --tftp-secure
+has no effect, but only files which have the world-readable bit set
+are accessible. It is not recommended to run dnsmasq as root with TFTP
+enabled, and certainly not without specifying --tftp-root. Doing so
+can expose any world-readable file on the server to any host on the net.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/trust-anchor.html b/src/DnsmasqWebUI/wwwroot/option-help/trust-anchor.html
new file mode 100644
index 0000000..ac7b799
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/trust-anchor.html
@@ -0,0 +1,9 @@
+--trust-anchor=<domain>,[<class>,][<key-tag>,<algorithm>,<digest-type>,<digest>]
+Provide DS records to act a trust anchors for DNSSEC
+validation. The class defaults to IN. Typically these will be the DS record(s) for Key Signing
+key(s) (KSK) of the root zone,
+but trust anchors for limited domains are also possible.
+A negative trust anchor (ie. proof that a DS record doesn't exist) may be configured be specifying
+only the name or only the name and class. This can be useful for forcing dnsmasq to treat zones delegated
+using --server=/<domain>/<ip-address> as unsigned. The current
+root-zone trust anchors may be downloaded from https://data.iana.org/root-anchors/root-anchors.xml
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/txt-record.html b/src/DnsmasqWebUI/wwwroot/option-help/txt-record.html
new file mode 100644
index 0000000..3288743
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/txt-record.html
@@ -0,0 +1,5 @@
+-Y, --txt-record=<name>[[,<text>],<text>]
+Return a TXT DNS record. The value of TXT record is a set of strings,
+so any number may be included, delimited by commas; use quotes to put
+commas into a string. Note that the maximum length of a single string
+is 255 characters, longer strings are split into 255 character chunks.
\ No newline at end of file
diff --git a/src/DnsmasqWebUI/wwwroot/option-help/user.html b/src/DnsmasqWebUI/wwwroot/option-help/user.html
new file mode 100644
index 0000000..6a98cdb
--- /dev/null
+++ b/src/DnsmasqWebUI/wwwroot/option-help/user.html
@@ -0,0 +1,4 @@
+-u, --user=<username>
+Specify the userid to which dnsmasq will change after startup. Dnsmasq must normally be started as root, but it will drop root
+privileges after startup by changing id to another user. Normally this user is "nobody" but that
+can be over-ridden with this switch.
\ No newline at end of file