Name Resolution Protocols
This section covers protocols and systems used to resolve hostnames to IP addresses on local networks and the internet. These protocols help identify and reach systems using human-readable names.
Protocol |
Description |
Use Case |
---|---|---|
ALLJOYN-NS |
Part of the AllJoyn framework, used for name resolution and service discovery in IoT environments. Resolves names and services in proximity networks using a decentralized approach. |
IoT device name resolution and service discovery |
DNS (Domain Name System) |
Core protocol that translates domain names to IP addresses on the internet. Hierarchical and distributed naming system. |
Accessing websites, resolving hostnames in enterprise networks |
DDNS (Dynamic DNS) |
Extension of DNS that automatically updates records when IPs change. Useful for hosts with dynamic IP addresses. |
Home networks, dynamic IP systems, remote access |
LLMNR (Link-Local Multicast Name Resolution) |
Allows name resolution for hosts on the same local network without a DNS server. Uses multicast over IPv4 or IPv6. |
Peer-to-peer name resolution in small networks |
mDNS (Multicast DNS) |
Resolves hostnames to IPs in small networks without needing a DNS server. Used by Apple Bonjour and other zero-configuration systems. |
Home/office network device discovery |
NBNS (NetBIOS Name Service) |
Resolves NetBIOS names to IP addresses in local networks. Used in legacy Windows environments. |
Legacy file and print sharing |
Main Features:
Part of the AllJoyn IoT framework
Decentralized name resolution and service discovery
Operates in proximity-based networks without central DNS
Use Cases:
Smart home or industrial IoT environments
Ad hoc device discovery and communication
Secure, local device resolution without DNS infrastructure
Alternative Protocols:
mDNS – Zero-configuration multicast resolution
LLMNR – Link-local resolution on IPv4/IPv6
Let us learn more about ALLJOYN-NS:
RFCs: RFC 1034, RFC 1035
Main Features:
Distributed and hierarchical resolution system
Maps human-readable domain names to IP addresses
Supports caching, zone transfers, and recursive/iterative queries
Use Cases:
Resolving domains on the internet
Internal network resource mapping
Email routing and service discovery
Alternative Protocols:
DDNS – Dynamic record updates
NBNS – Legacy NetBIOS resolution
Let us learn more about DNS:
RFC: RFC 2136
Main Features:
Allows real-time updates of DNS entries
Integrates with DHCP for automatic IP resolution
Helps maintain consistent hostname mappings for dynamic clients
Use Cases:
Home/remote access where IPs change frequently
Dynamic cloud-based VM deployments
VPN and DNS automation
Alternative Protocols:
Static DNS – Manual updates
mDNS – For local dynamic discovery
Let us learn more about DDNS:
RFC: RFC 4795
Main Features:
Peer-to-peer name resolution over local link
Uses multicast queries on IPv4 and IPv6
Works without DNS or DHCP servers
Use Cases:
Small networks and ad-hoc setups
Temporary networking scenarios (labs, conferences)
Environments with limited infrastructure
Alternative Protocols:
mDNS – Similar local multicast discovery
NBNS – Legacy broadcast resolution
Let us learn more about LLMNR:
RFC: RFC 6762
Main Features:
Resolves hostnames on local networks via multicast
Foundation for zero-configuration networking (Bonjour, Avahi)
No need for centralized DNS infrastructure
Use Cases:
Home/office device discovery
Smart TVs, printers, IoT gadgets
Network service advertisement (e.g., AirPlay, Chromecast)
Alternative Protocols:
LLMNR – Also multicast-based, but less commonly supported
NBNS – Broadcast-based for legacy Windows systems
Let us learn more about mDNS:
RFC: RFC 1001, RFC 1002
Main Features:
Broadcast-based NetBIOS name resolution
Supports legacy Windows file/print sharing
Works with or without WINS servers
Use Cases:
Legacy networks with older Windows OS
SMB file sharing environments
Networks transitioning from NetBIOS to DNS
Alternative Protocols:
DNS – Modern, hierarchical resolution
LLMNR/mDNS – Local name resolution options
Let us learn more about NBNS: