2

Remote Dns Jobs in Utah (NOW HIRING)

$56.50 - $75.25/hr

... remote state on S3. * strong> CI/CD & automation: pipeline design in GitHub Actions or GitLab CI ... S trong problem-solving and analytical abilities; comfortable debugging across the stack (DNS → ...

Remote; Ability to travel up to 25% * Sales motion: Technical consultative selling across net-new ... Troubleshooting DNS, proxies, firewalls, VPCs, and NLBs within NIPR/SIPR and DoD network enclaves ...

Remote Dns information

What is the difference between Remote Dns vs Remote Network Technician?

AspectRemote DnsRemote Network Technician
Required CertificationsDNS, Network+Network+, CCNA
Work EnvironmentRemote, IT support, troubleshootingRemote, network setup, maintenance
Industry UsageIT, cybersecurity, hosting providersIT, telecommunications, enterprise networks
Common Search/ComparisonYesYes

Remote Dns specialists focus on managing and troubleshooting DNS servers and related network services remotely, often within IT or cybersecurity contexts. Remote Network Technicians handle broader network infrastructure tasks, including configuring and maintaining network hardware and software. While both roles are remote and require networking certifications, Remote Dns is more specialized in DNS management, whereas Remote Network Technicians have a wider scope in network support and maintenance.

What are the key skills and qualifications needed to thrive as a remote DNS engineer, and why are they important?

To excel as a Remote DNS Engineer, you need a deep understanding of DNS protocols, networking fundamentals, and experience with DNS server configuration, often supported by certifications like CompTIA Network+ or Cisco CCNA. Familiarity with DNS management tools (such as BIND, Unbound, or Windows DNS), monitoring systems, and security protocols is crucial for managing distributed environments. Strong problem-solving skills, attention to detail, and effective remote communication help you stand out in this position. These abilities ensure reliable domain resolution, network security, and seamless collaboration with distributed teams.

What is a remote DNS?

Remote DNS jobs involve managing, configuring, and troubleshooting Domain Name System (DNS) servers and services from a remote location. These roles typically include tasks like setting up DNS records, ensuring domain availability, preventing DNS-related security threats, and resolving connectivity issues. Remote DNS professionals often work for internet service providers, web hosting companies, or large organizations with distributed networks. The work can span supporting public DNS infrastructure, internal corporate networks, or cloud-based systems.

What are common challenges faced by remote DNS administrators when supporting distributed environments?

Remote DNS administrators often encounter challenges such as ensuring consistent DNS configurations across multiple locations, troubleshooting latency or propagation delays, and maintaining security against threats like DNS spoofing. Coordinating with remote teams to implement updates and handle outages can also be complex, as it requires strong communication and documentation skills. Effective use of remote management tools and automated monitoring can help address these challenges and ensure reliable DNS service delivery.
What are popular job titles related to Remote Dns jobs in Utah? For Remote Dns jobs in Utah, the most frequently searched job titles are:
What cities in Utah are hiring for Remote Dns jobs? Cities in Utah with the most Remote Dns job openings:

$56.50 - $75.25/hr

Full-time

Medical

Posted 6 days ago


Job description

Cloud Platform Engineer (AWS / EKS / Terraform)
Team: Infrastructure · Reports to Head of Infrastructure
About the role
You will build and operate TookiTaki's cloud platform: AWS EKS clusters managed as code, GitOps-driven delivery with the Argo suite, operator-managed data services running on Kubernetes, and a Terraform-based self-service layer that lets application teams request infrastructure through reviewed YAML instead of tickets. The job is platform engineering, not click-ops — everything ships through version control, automated pipelines, and policy gates.
Requirements
Education

  • R
  • equired: Bachelor's degree in Computer Science, Engineering, or a related field — or equivalent practical experience.
  • P
  • referred: Relevant certifications over a Master's — CKA (Certified Kubernetes Administrator), HashiCorp Terraform Associate, AWS Solutions Architect Associate or higher.
    Experience
  • 3
  • –5+ years in cloud, platform, or DevOps engineering.
  • P
  • roven track record running production Kubernetes on a managed cloud (EKS strongly preferred), including stateful workloads.
  • E
  • xperience operating infrastructure entirely through Infrastructure as Code — no console-driven change management.
    Technical expertise
  • <
  • strong>Kubernetes / EKS: cluster lifecycle and upgrades, autoscaling (Karpenter, KEDA, VPA), ingress and load balancing, IRSA/Pod Identity, core add-ons (cert-manager, external-dns, CoreDNS, node-local-dns).
  • <
  • strong>GitOps / Argo: ArgoCD for platform and application delivery (app-of-apps, Helm chart authoring, sync and rollback strategies), Argo Rollouts for progressive delivery, Argo Workflows/Events for automation.
  • <
  • strong>Databases and stateful services on Kubernetes: deploying and operating databases via Kubernetes operators — PostgreSQL and MySQL (Percona operators), ScyllaDB, Elasticsearch, Valkey/Redis, Kafka (Strimzi) — plus AWS RDS/Aurora where managed services fit better; backup/restore, upgrades, and capacity management for stateful workloads.
  • <
  • strong>Terraform: authoring reusable, versioned, tested modules (not just consuming them) — variable/output interface design, `terraform test`, semantic versioning, remote state on S3.
  • <
  • strong>CI/CD & automation: pipeline design in GitHub Actions or GitLab CI; plan/apply automation with Atlantis; policy-as-code gates (OPA/Conftest, checkov, tflint); pre-merge validation and drift detection.
  • <
  • strong>AWS core services: VPC and network design, Route 53, IAM (least-privilege roles and policies), S3, RDS/Aurora.
  • <
  • strong>Observability: Datadog, OpenTelemetry (collector and kube-stack), Grafana; alerting hygiene with low false-positive rates; log and event pipelines.
  • <
  • strong>Programming: solid scripting/tooling ability in Python or Go — enough to build renderers, validators, and pipeline tooling, not just glue scripts.
  • <
  • strong>Nice to have: data platform tooling (Airflow, Spark on Kubernetes, Temporal, StarRocks), identity and SSO (Keycloak, Dex, oauth2-proxy), load testing with k6, FinOps practices (tagging standards, cost allocation, rightsizing).
    Soft skills
  • S
  • trong problem-solving and analytical abilities; comfortable debugging across the stack (DNS → LB → cluster → workload → database).
  • C
  • lear written communication — design docs, runbooks, and PR descriptions are first-class deliverables here.
  • C
  • ollaborative mindset: infrastructure changes ship through peer review, and platform decisions are made with (not for) application teams.
    Key competencies
  • <
  • strong>Platform thinking: design paved roads that make the secure, cost-efficient path the easy path for application teams.
  • <
  • strong>Automation-first: if a task is done twice manually, the third time is a pipeline.
  • <
  • strong>Ownership: own services end to end — provisioning, upgrades, incidents, cost, and documentation.
  • <
  • strong>Cost awareness: treat cloud spend as an engineering metric; tag, measure, and optimize continuously.
  • <
  • strong>Adaptability: comfortable in a fast-moving environment where the platform itself is under active development.
    Success metrics (first 6–12 months)
  • A
  • pplication teams provision standard infrastructure through the self-service platform with no manual Terraform written by requesters.
  • E
  • KS cluster and node-group upgrades executed as routine, zero-downtime operations via blue/green rollout.
  • O
  • perator-managed data services (PostgreSQL, Kafka, Elasticsearch, etc.) run with tested backup/restore and rehearsed upgrade procedures.
  • 1
  • 00% of infrastructure changes delivered through reviewed, policy-gated pipelines — zero out-of-band console changes.
  • D
  • eployment lead time for platform changes reduced measurably (target: same-day merge-to-production for routine changes).
  • C
  • ost visibility established via tagging and dashboards, with identified savings executed (rightsizing, autoscaling, storage tiering).
  • A
  • ctionable alerting: on-call pages correspond to real incidents; false-positive alerts trend toward zero.
  • M
  • ean time to recovery for platform incidents under 30 minutes.
    Benefits
  • <
  • strong>Competitive salary aligned with industry standards and experience.
  • <
  • strong>Professional development: certification support (CKA, AWS, Terraform) and training across cloud, platform, and data engineering.
  • <
  • strong>Comprehensive benefits: health insurance and flexible working options.
  • <
  • strong>Growth opportunities: career progression within TookiTaki's expanding infrastructure and platform organization.

    Employment Type: FULL_TIME