An abstract-encoding compliant module for encoding / decoding DNS packets
Cloud DNS Client Library for Node.js
Google Fonts module for Nuxt
Compare DNS record strings for equality
OpenTelemetry instrumentation for `node:dns` name resolution module
the http/https agent used by the npm cli
An abstract-encoding compliant module for encoding / decoding DNS packets
Encode/decode DNS-SD TXT record RDATA fields
Low level multicast-dns implementation in pure javascript
A DNS Server and Client Implementation in Pure JavaScript with no dependencies.
dns
Make low-level DNS requests with retry and timeout support.
Parse and stringify mdns service types
Abstraction for exponential and custom retry strategies for failed operations.
TypeScript definitions for dns-packet
Middleware to set X-DNS-Prefetch-Control header.
whois, with actual JavaScript (not flat string) results!
An abstract-encoding compliant module for encoding / decoding DNS packets
Resolve DNS queries with browser fallback
Discover publicly available DNS Records for a domain
A decorator on top of `fetch` that caches the DNS query of the `hostname` of the passed URL
Caches dns resolutions made with async dns.resolve instead of default sync dns.lookup, refreshes in background
TypeScript definitions for multicast-dns
Get your public IP address — very fast!
google-dns-rs is a third party Google DNS client for rust
Unified telemetry system for monitoring and observability
Client to update google domains dynamic dns
Client to update google domains dynamic dns
A complete library to interact with Dns (protocol v1)
A complete library to interact with Dns (protocol v1)
A complete library to interact with dns (protocol v1beta1)
A complete library to interact with Dns (protocol v2)
A complete library to interact with Dns (protocol v2)
This is the simple REST client for Cloud DNS API V1. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Cloud DNS API, but note that some services may provide a separate modern client that is easier to use.
google-cloud-dns is the official library for Google Cloud DNS.
Make ruby use Google's DNS servers
This is the simple REST client for Cloud DNS API V1beta2. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Cloud DNS API, but note that some services may provide a separate modern client that is easier to use.
This gem is a plugin for acmesmith and implements an automated dns-01 challenge responder using Google Cloud DNS
This is the simple REST client for Cloud DNS API V2. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Cloud DNS API, but note that some services may provide a separate modern client that is easier to use.
Google Cloud DNS for VMPooler
This library provides a simple set of helper methods to manage slices and DNS zones/records on your Slicehost account (http://slicehost.com). == Capistrano tasks There are two capistrano tasks: cap slicehost:zone:add # Create DNS zone cap slicehost:zone:mx:google # Add Google Apps MX records To your config/deploy.rb, add the following: require "slicehost/recipes/capistrano" if Capistrano::Version::MAJOR >= 2 # Used to setup/update DNS registry of url => ip set :domain_mapping, "myurl.com" => "123.456.789.012" == Underlying API The current API is very alpha. It was just the simplest thing that worked. There are unit tests demonstrating it working and everything. Future releases will have a nicer, class-based API. Contact: Dr Nic Williams, drnicwilliams@gmail.com
A Rails engine for verifying that requests claiming to be from search engine bots (Google, Bing, etc.) and AI bots (GPTBot, PerplexityBot) are actually from those services, using IP range matching and reverse DNS verification.
Apigee Connect allows the Apigee hybrid management plane to connect securely to the MART service in the runtime plane without requiring you to expose the MART endpoint on the internet. If you use Apigee Connect, you do not need to configure the MART ingress gateway with a host alias and an authorized DNS certificate. Note that google-cloud-apigee_connect-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-apigee_connect instead. See the readme for more details.
This is the simple REST client for ACME DNS API V1. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the ACME DNS API, but note that some services may provide a separate modern client that is easier to use.
A daemon, running in background on a Linux router or firewall, monitoring the state of multiple internet uplinks and changing the routing accordingly. LAN/DMZ internet traffic (outgoing connections) is load balanced between the uplinks using Linux multipath routing. The daemon monitors the state of the uplinks by routinely pinging well known IP addresses (Google public DNS servers, etc.) through each outgoing interface: once an uplink goes down, it is excluded from the multipath routing, when it comes back up, it is included again. An uplink may be assigned to a priority group: lower priority uplinks will only be used if all higher priority ones are down. That's useful to only use pay-per-traffic uplinks if no regular uplink is working. All of the routing changes are notified to the administrator by email. Fault Tolerant Router is well tested and has been used in production for several years, in several sites. See https://github.com/drsound/fault_tolerant_router for full documentation.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.