大网数据广告活动
服务器运维问答

When 'dig' returns a single A record, the IP address changes between calls. What is this a sign of?

· 52CE 我爱测

In my internal work network, whenever I launch dig against a particular hostname, I get result similar to this: ;; ANSWER SECTION: some.internal.host.com. 10 IN A 10.210.54.121 If I keep spamming the same dig some.internal.host.c…

问题原文

原帖链接 · CBlew · CC BY-SA 4.0

In my internal work network, whenever I launch dig against a particular hostname, I get result similar to this:

;; ANSWER SECTION:
some.internal.host.com.     10  IN  A   10.210.54.121

If I keep spamming the same dig some.internal.host.com command, the response always has a single A record, but the IP address is changing between calls.

I assume it is some form of load-balancing, but the full list of IP addresses in the pool is hidden from inquisitive persons.

What could be the technique that is used here to achieve the described result?

已采纳解答

原帖链接 · Jiri B · CC BY-SA 4.0

'10' in the output is TTL. It is short, 10 seconds, so one can guess that this is dynamically changing. That's why it should not live in DNS recursive servers' cache for more than 10 seconds.

How is it done? It depends on remote DNS server and the way it is implemented. Either hidden nodes dynamically (de-)register into DNS or DNS could be "detecting" alive backend hosts itself.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2021-03-19)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。