You can advertise a single webpage to local devices by adding just five records to your authoritative DNS server’s zone file. Advertising additional pages requires just three more records each. You must have write access to your zone files.
Note: You may want to set a short DNS TTL (time-to-live) so you can test and make changes without having to wait a long time for the updates to propagate.
; 1. Domain Enumeration
; These records invite devices to browse this domain.
; (The '@' sign means "the current domain" --
; i.e. the domain being described by this zone file.)
b._dns-sd._udp IN PTR @ ; b = browse domain
lb._dns-sd._udp IN PTR @ ; lb = legacy browse domain
; (domain that will be used for devices that don’t specify a domain to browse)
; 2. List of named service entities
; These records list the named 'http' service entities you want devices
; to be able to discover. You can use upper-case, punctuation,
; UTF-8 rich text, etc., in service names, but certain punctuation
; like spaces and dots needs to be escaped with a backslash in the
; name server zone file (because that file’s content is sent as raw data, not escaped).
_http._tcp PTR New\ User\ Information\ Page._http._tcp
; 3. SRV & TXT records describing each service entity named above
; These records tell devices how to access the named 'http' service entities
; listed above. In the example below, fill in the correct host name.
; If it’s a fully qualified host name, it needs to end with a dot, as shown.
; If it’s a partial host name relative to the current zone (e.g. just "nu-info",
; with the remainder of the name being implicit) then don’t end it with a dot.
; The "path=/xxx" in the TXT record tells the web browser the specific
; page on the server it should request in its "HTTP GET" command.
; Often, but not always, the path will be just "/".
New\ User\ Information\ Page._http._tcp SRV 0 0 80 nu-info.example.com.