To look up the address of “you don’t need to first configure your client to use Google’s DNS servers. To look up the address of “you don’t need to first configure your client to use Amazon’s DNS servers. Or, conversely, that the client needs to be configured to use the DNS server where the service discovery records exist. It makes a lot more sense and is a lot more useful to set the domain to be one that you do have control over.Ī common misperception is that the service discovery records need to be created on a DNS server that the service discovery client is configured to use. There’s really no reason to do this, since you have no control over your ISP’s domain. In many cases people set their home gateway’s DHCP server to return their ISP’s domain name in the DHCP packet, without giving it much thought. If you don’t have have administrative access to the domain currently being returned by your DHCP server, but you do control the DHCP server, then you can change the DHCP server to return a different domain - one that you do have control over. Therefore, as long as you have administrative access to that domain’s authoritative DNS server(s), you can easily add the necessary records so the clients will discover web pages, printers, and other network services of your choosing. When clients get a response packet from the local network’s DHCP server, there’s a domain in that packet, and clients running Mac OS X 10.4 (Tiger) or later, or iOS, or Bonjour for Windows, automatically query that domain for advertised services. One of easiest applications of Wide-Area DNS-SD is simply to add a few records to your domain’s authoritative DNS server(s), to automatically advertise selected services to clients, with zero configuration on the client side. Setting up DNS for Zero-Configuration Wide-Area Service Discovery by Clients Dynamic DNS Update Leases (draft-sekar-dns-ul) describes a protocol for performing DNS Dynamic Updates with an attached lease time, that are automatically deleted unless renewed before the lease expires, much like a DHCP address lease.DNS Long-Lived Queries (draft-sekar-dns-llq) describes a protocol for setting up long-lived DNS queries with change notification, as a more efficient alternative to rapidly polling the server.Hybrid Unicast/Multicast DNS-Based Service Discovery (draft-cheshire-mdnsext-hybrid) describes a way to provide wide-area service discovery for devices that only advertise their services using link-local Multicast DNS.RFC 6887 Port Control Protocol (PCP) describes a protocol for asking a home NAT gateway for its “public” address, so that a host behind a NAT gateway can create a DNS Dynamic Update using that public address, rather than its less useful private address, and similarly for asking a home NAT gateway to assign a public port number and an inbound port maping, so that a host behind a NAT gateway can create DNS SRV records using that public port number rather than its less useful private internal port number.DNS-SD is not dependent on Multicast DNS (it works with unicast as well) DNS-SD and mDNS are complementary technologies that can be used together. RFC 6763 DNS-Based Service Discovery describes how to perform network browsing and service discovery using only standard DNS packets and record types.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |