Which Two Protocols Are Service Discovery Protocols
Engineers often ask which two protocols are service discovery protocols in modern networks. The two main protocols are Multicast DNS (mDNS) and DNS Service Discovery (DNS-SD). Network exams also pair Cisco Discovery Protocol (CDP) with Link Layer Discovery Protocol (LLDP). Both pairs help apps and devices find each other on a network without manual setup. Teams use them so databases, servers, and AI agents can locate active endpoints right away. How which two protocols are service discovery p
Emergency Access Protocols + AI-Assisted Vulnerability Discovery: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
Engineers often ask which two protocols are service discovery protocols in modern networks. The two main protocols are Multicast DNS (mDNS) and DNS Service Discovery (DNS-SD).
Network exams also pair Cisco Discovery Protocol (CDP) with Link Layer Discovery Protocol (LLDP). Both pairs help apps and devices find each other on a network without manual setup. Teams use them so databases, servers, and AI agents can locate active endpoints right away.
How which two protocols are service discovery protocols work in practice
In cloud and local networks, mDNS and DNS-SD work together to find running services. A new server joins the network and announces its name and port to nearby hosts. MDNS sends these small messages across the local network without needing a central name server.
DNS-SD adds extra details to standard DNS records so clients know what service runs where. An app or AI agent reads these records to find the right database host and port. When a server moves to a new address, the records update so traffic keeps flowing.
On physical hardware, CDP and LLDP work at the link layer between switches and routers. Each device sends out short status updates to its direct neighbors every few seconds. Network tools read these updates to map out cables, ports, and device types across racks.
Comparing link layer and name based discovery protocols
Choosing between these protocol pairs depends on what layer of the stack your team manages. CDP and LLDP run directly on network cables between physical switches, routers, and host servers. They do not route across subnets, so their messages stay on one single wire segment.
Cisco built CDP for its own gear, while LLDP works across many hardware vendors. System admins read neighbor tables from these protocols to fix bad cabling or port mismatches.
MDNS and DNS-SD work higher up the stack to help software find other software. A microservice or AI worker queries DNS-SD to locate an active database or cache node. This keeps IP addresses out of app files and makes scaling up much simpler.
Emergency Access Protocols + AI-Assisted Vulnerability Discovery: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Security and operational tradeoffs after discovery
Service discovery protocols make network setup fast, but they also bring clear security risks. Open discovery lets any host on the local network see where critical databases run. Attackers who get inside a network can listen to mDNS or LLDP messages to map targets.
Even when discovery is locked down, finding a host is only the first step. After an engineer or AI agent finds a database, it still needs to log in. Most teams rely on static keys or basic role rules to control this step.
Static keys and broad roles create big blind spots once a live session starts. A role might let an app or user log in to a production database server. Once inside, that role rarely checks individual queries or commands sent during the session.
Shared database keys can leak in logs, scripts, or agent memory without anyone noticing. If a human or AI agent runs a bad query, static roles will not stop it. Raw results can also return sensitive data like emails, phone numbers, or card numbers.
Data masking is needed to rewrite matched fields like national IDs in query results. Teams need controls that check every command and log actions at the session level.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
What are the two main service discovery protocols in networking exams?
Networking tests usually look for Cisco Discovery Protocol (CDP) and Link Layer Discovery Protocol (LLDP). In software and cloud setups, the top pair is mDNS and DNS-SD.
Why do AI agents and apps need service discovery?
Cloud servers change IP addresses often when teams scale apps or replace broken hosts. Service discovery lets apps and AI agents look up current addresses by name right away.
Does service discovery secure database sessions?
No, service discovery only helps a client find the network address and port of a service. Teams still need strong login checks, command rules, and data masking during the live session.