Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #266901

Re: Network Problem: Redirection

From Charles Curley <charlescurley@charlescurley.com>
Newsgroups linux.debian.user
Subject Re: Network Problem: Redirection
Date 2024-02-03 00:00 +0100
Message-ID <I3aFP-7sFF-11@gated-at.bofh.it> (permalink)
References <I38Xo-7rQ4-21@gated-at.bofh.it> <I39gJ-7rW1-3@gated-at.bofh.it> <I39A7-7s2O-13@gated-at.bofh.it> <I39JL-7s62-5@gated-at.bofh.it>
Organization occasionally

Show all headers | View raw


On Fri, 2 Feb 2024 16:52:48 -0500
Greg Wooledge <greg@wooledge.org> wrote:

> Well, we don't know what's "right" or "wrong" on your networks.  These
> are private (non-routable) addresses with no meaning to anyone but you
> and your fellow network denizens.

Agree.

> 
> If you need different name resolution depending on whether you're
> running on the host vs. running on the guest, then I would imagine
> there is some well-known way to define that.  Perhaps a different
> hosts file that's only used by guests?  I don't know virtualization
> stuff well.

Yup. I took a quick and dirty route to solve a problem, and it leaked
over into another area. Sigh. The solution I took depends on the fact
that the libvirtual stuff uses dnsmasq for DNS and DHCP. And dnsmasq
reads the host machine's hosts file. Nice. But, as you pointed out, so
does the host machine's DNS lookup stuff. Sigh.

Possibly the solution to this problem is to see if I can take it out of
hosts, add it to dnsmasq directly, and finagle dnsmasq to only be
visible to the virtual machines.

But I don't think that will solve the routing problem.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Network Problem: Redirection Charles Curley <charlescurley@charlescurley.com> - 2024-02-02 22:10 +0100
  Re: Network Problem: Redirection Marco Moock <mm@dorfdsl.de> - 2024-02-02 22:20 +0100
    Re: Network Problem: Redirection Charles Curley <charlescurley@charlescurley.com> - 2024-02-02 22:50 +0100
  Re: Network Problem: Redirection Greg Wooledge <greg@wooledge.org> - 2024-02-02 22:30 +0100
    Re: Network Problem: Redirection Charles Curley <charlescurley@charlescurley.com> - 2024-02-02 22:50 +0100
      Re: Network Problem: Redirection Greg Wooledge <greg@wooledge.org> - 2024-02-02 23:00 +0100
        Re: Network Problem: Redirection Charles Curley <charlescurley@charlescurley.com> - 2024-02-03 00:00 +0100
          Re: Network Problem: Redirection Charles Curley <charlescurley@charlescurley.com> - 2024-02-03 00:50 +0100
            Re: Network Problem: Redirection hw <hw@adminart.net> - 2024-02-04 12:50 +0100
    Re: Network Problem: Redirection Gremlin <scott-andrews@columbus.rr.com> - 2024-02-02 23:20 +0100
      Re: Network Problem: Redirection Marco Moock <mm@dorfdsl.de> - 2024-02-04 08:50 +0100
        Re: Network Problem: Redirection Gremlin <scott-andrews@columbus.rr.com> - 2024-02-04 13:20 +0100
          Re: Network Problem: Redirection Marco Moock <mm@dorfdsl.de> - 2024-02-04 15:10 +0100
            Re: Network Problem: Redirection Gremlin <scott-andrews@columbus.rr.com> - 2024-02-04 15:30 +0100

csiph-web