Timeline for Understanding how devices on a LAN/VLAN discover the existence of other local devices
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11, 2020 at 9:39 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 3 characters in body
|
| Aug 14, 2018 at 22:09 | vote | accept | ahelton | ||
| Aug 14, 2018 at 22:08 | comment | added | ahelton | Ah. Thanks for the clarification. I've been learning all these terms lately and am trying to figure out how it all works together. | |
| Aug 14, 2018 at 20:29 | comment | added | Zac67♦ | DDNS is a special case where an A record is dynamically updated when a host's IP address changes - commonly used with dynamic public IP addresses but not in use for servers within an organizational network. The rest is absolutely correct. A file server's name may be provided by a client login script that is in turn provided by a domain controller (or a similar authentication server) that is in turn provided by a DNS server that is in turn provided by DHCP, .... | |
| Aug 14, 2018 at 20:17 | comment | added | ahelton | I just thought of this after reading your response, but a DNS server uses DDNS to dynamically keeps its Name to IP address records up-to-date, correct? So if a host needs to access something from another host, it would just need to query the DNS server since it would have an accurate list of all nodes on a given domain (by communicating with the DHCP server, i.e. DDNS). Is that an accurate statement? I guess I am still a bit confused, though, on how a host would discover the name of a file server, for example. Is that where the "special DNS records" come in? | |
| Aug 14, 2018 at 19:47 | history | answered | Zac67♦ | CC BY-SA 4.0 |