utility to get fqdn of machine
TypeScript definitions for is-fqdn
Node module to get FQDN from local machine. Multiplatform.
Lookup the fully qualified domain name ("FQDN") of the current server's IP (default) or a custom IP. 90x faster than `hostname -f` and works with Node v6.4+.
Get fqdn of machine. Multiplatform (Win & UX).
Get fqdn.
Node module to get FQDN synchronously from local machine (Linux support)
Check if a string represent a fully qualified domain name
A Node.js library for checking if an FQDN (Fully Qualified Domain Name) is alive or not, uses a combination techniques of `NS` records, WHOIS/RDAP lookups, `A/AAAA` records
Fully Qualified Domain Name is a simple tool for getting the fully qualified domain name (FQDN) of an IP. It returns the fully qualified domain name of the ip provided.
Client Store implementation for @atproto-labs/oauth-provider. This implementation interprets client_id as Fully Qualified Domain Name (FQDN) in order to retrieve Client Metadata.
Get the fully qualified domain name via a Promise
A library of Svelte components for interacting with Viam-powered machines. Each widget provides a test interface for a specific resource type -- arms, bases, cameras, motors, sensors, and more -- allowing users to send commands, view live data, and contro
NTLM single-sign-on for Node.js. Only Windows OS supported.
Extract the TLD/domain/subdomain parts of an URL/hostname against mozilla TLDs 'official' listing .
Validator for ThinkJS
Use `format` to specify in which format the value has to represented and modified. This may impose some validation and will influence how the UI shows the value.
Corellium CLI Tool
A set of types to be used with CortexQL
Comprehensive list of TLDs and subdomain registrars
UI5 middleware for delivering a dedicated welcome/start page
A Papertrail transport for winston
Apps health monitor and mail notification module for pm2
Self-signed certificate for development use, generated using openssl. Expires in the year 4754 (4754-06-06).
FQDN (Fully Qualified Domain Name)
FQDN (Fully Qualified Domain Name) lookup structures (based on tries)
Active Directory data collector for Bloodhound written in rust.
A tool to play and attack DHCP
ANS Trust Verification library for the Agent Name Service
A split-horizon DNS server and forwarding resolver with gRPC management
Shared types for the Agent Name Service (ANS) ecosystem
Terminal-agnostic, PTY-based, regex-driven output colorizer.
A native Sync/Async Rust implementation of client DNS resolver.
Distributed monitoring for Round Robin DNS load balancing and high availability
Cloudflare dynamic DNS client
Async + `no_std` + no-alloc implementation of the Websockets protocol
FqdnFacts allows you to create fact handlers for different FQDN formats. This is primarily intended for use with Puppet/Facter to facilitate dynamic fact generation based on FQDNs.
Adds domain, subdomain and fqdn routing support to Rails
A Test Kitchen Provisioner for Chef Nodes
Converts the FQDN to the IP address.
String self is a simple tool to create Java FQDN like objects in Ruby.
Find computer name, FQDN, and IP address(es) of all DCs.
= DESCRIPTION: Provides a Chef handler which can report run status, including any changes that were made, to a Graylog2 server. In the case of failed runs a backtrace will be included in the details reported. = REQUIREMENTS: * A Graylog2 server running somewhere. = USAGE: This example makes of the chef_handler cookbook, place some thing like this in cookbooks/chef_handler/recipes/gelf.rb and add it to your run list. It also assumes your Graylog2 server has set the attribute rsyslog_server to true. log_server = search(:node, "rsyslog_server:true").first if log_server include_recipe "chef_handler::default" gem_package "chef-gelf" do action :nothing end.run_action(:install) # Make sure the newly installed Gem is loaded. Gem.clear_paths require 'chef/gelf' chef_handler "Chef::GELF::Handler" do source "chef/gelf" arguments({ :server => log_server['fqdn'] }) supports :exception => true, :report => true end.run_action(:enable) end Arguments take the form of an options hash, with the following options: * :server - The server to send messages to. * :port (12201) - The port to send on. * :facility (chef-client) - The facility to report under. * :host (node.fqdn) - The host to report messages as coming from. * :blacklist ({}) - A hash of cookbooks, resources and actions to ignore in the change list. = BLACKLISTING: Some resources report themselves as having updated on every run even if nothing changed, or are just things you don't care about. To reduce the amount of noise in your logs these can be ignored by providing a blacklist. In this example we don't want to be told about the GELF handler being activated: chef_handler "Chef::GELF::Handler" do source "chef/gelf" arguments({ :server => log_server['fqdn'], :blacklist => { "chef_handler" => { "chef_handler" => [ "nothing", "enable" ] } } }) supports :exception => true, :report => true end.run_action(:enable) = LICENSE and AUTHOR: Author:: Jon Wood (<jon@blankpad.net>) Copyright:: 2011, Blank Pad Development Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
No description provided.
No description provided.
No description provided.
No description provided.