---
id: 4479674f-16de-4cfb-afc1-73042d4ab8db
type: fix
title: "Fix: Gitea SSH remote (git@git.manticorum.com) resolves to Pi-hole instead of Gitea LXC"
tags: [gitea, ssh, dns, networking, fix, pihole, homelab, dotfiles]
importance: 0.65
confidence: 0.8
created: "2026-02-27T05:48:03.833429+00:00"
updated: "2026-02-27T05:48:35.579070+00:00"
relations:
  - target: 5f31ea7f-9b53-427d-b601-ab98dabaa2e3
    type: RELATED_TO
    direction: incoming
    strength: 0.9
    edge_id: b1d439b6-456f-4271-bd16-0d612564e7f4
  - target: f4683542-eb76-4397-9e84-673c86a05904
    type: RELATED_TO
    direction: outgoing
    strength: 0.75
    edge_id: 4cb3054a-c8d4-4eb5-bc5e-bdae9732b7cc
  - target: 62b643f2-5ed7-4ea5-b87f-ef0687ad83ec
    type: RELATED_TO
    direction: outgoing
    strength: 0.7
    edge_id: f054dc64-4a57-4581-b389-b8ee0928ebe2
---

# Gitea SSH Remote Resolves to Pi-hole

## Problem
`git@git.manticorum.com:cal/repo.git` SSH remotes fail because `git.manticorum.com` DNS resolves to Pi-hole (10.10.0.16) instead of the Gitea LXC (10.10.0.225).

## Root Cause
Pi-hole is configured as the local DNS resolver. The DNS record for `git.manticorum.com` points to Pi-hole, not directly to the Gitea server.

## Fix (Preferred): Use HTTPS Remote
```bash
https://git.manticorum.com/cal/repo.git
```
Works because `~/.gitconfig` has a credential helper configured. No SSH key routing issues.

## Alternative Fix: SSH Config Override
Add to `~/.ssh/config`:
```
Host git.manticorum.com
    HostName 10.10.0.225
    User git
```
This bypasses DNS and connects directly to the Gitea LXC.

## Infrastructure Notes
- Gitea LXC IP: 10.10.0.225
- Pi-hole IP: 10.10.0.16
- HTTPS is the simpler solution since the git credential helper is already configured

## Context
Discovered while setting up ~/dotfiles repo and pushing to Gitea.