Difference between revisions of "Time to live (TTL)"
Jump to navigation
Jump to search
| (3 intermediate revisions by one other user not shown) | |||
| Line 16: | Line 16: | ||
* [[ICMP Time Exceeded]] | * [[ICMP Time Exceeded]] | ||
* Redis, Set a [[TTL]] value for [[keys]] on your node. | * Redis, Set a [[TTL]] value for [[keys]] on your node. | ||
| + | * [[Karpenter]]: <code>[[ttlSecondsUntilExpired]]</code> | ||
| + | [[node.alpha.kubernetes.io/ttl]] | ||
== See also == | == See also == | ||
| + | * {{TTL}} | ||
* {{mtr}} | * {{mtr}} | ||
* {{DNS}} | * {{DNS}} | ||
Latest revision as of 19:58, 1 March 2023
- Windows:
ping -i 2 8.8.8.8-iflag
- Windows:
Related terms[edit]
pingtraceroute- keepalive
- ICMP Time Exceeded
- Redis, Set a TTL value for keys on your node.
- Karpenter:
ttlSecondsUntilExpired
node.alpha.kubernetes.io/ttl
See also[edit]
- TTL, node.alpha.kubernetes.io/ttl, ttlSecondsUntilExpired
- IP:
route,mtr,traceroute,tcptraceroute,lft, TTL - DNS: Linux DNS, IP,
systemd-resolve,/etc/hosts,whois, Domain registrar,dig,host,nslookup,scutil --dnsdnsmasq,bind,delv,.local,.internal, .onion, FQDN, TTL,/etc/resolv.conf,/etc/systemd/resolved.conf,dscacheutil(macOS),hostname, hostnamectl,bind,resolvectl status, DNS sinkhole, Domain name server, LLMNR, Resource records:MX, TXT, NS, CAA, SSHFP, Apex, CNAME, Wildcard DNS records, Subdomain, /etc/nsswitch.conf,1.1.1.1,8.8.8.8, CoreDNS, dnsPolicy:, Google Public DNS, DNS caches, Kubernetes ExternalDNS, DNS forwarding, IDNA2008, DNS-1035, Domain name registrars, Split-view DNS, Pi-hole, NextDNS - TCP/IP, Transport protocol, UDP, SCTP, QUIC, subnet mask, Routing protocols: BGP, routing table, Policy based routing, multicast, TCP Fast Open, RDP, TTL, RTT, MPTCP, Large send offload (LSO): (TSO, GRO, GSO, TCP checksum),
ethtool, SCTP, 5-Tuple, Check TCP connectivity, TCP window size,/proc/sys/net/ipv4/tcp_rmem, ack, List of TCP ports, localhost, broadcast address
Advertising:
