Re: Named keeps dying on me
by Tom Horsley
On Thu, 15 Dec 2022 14:21:34 -0800
ToddAndMargo via users wrote:
> Your in frustration,
Has resolv.conf changed? Sometimes DHCP comes along on lease renewal
and rewrites sutff. Somewhere there is a NetworkManager option to
make it leave resolv.conf alone (always takes me an hour to find it
though).
Look at journalctl to see if named printed any useless messages
before dying.
I had lots of problems with named when the defaults were changed to insist
on encrypted DNS and never really got it working reliably which is why
I switched to dnsmasq (nice small man page for configuration instead of
the 12,742 pages of bind config info :-).
1 year, 5 months
Re: 127.0.0.53 question
by Bill C
Is that Dnsmasq like bind? The only thing I've ever cared to run would be
something like rsync and ssh as far as servers.
On Sat, Dec 17, 2022, 1:44 AM ToddAndMargo via users <
users(a)lists.fedoraproject.org> wrote:
> On 12/16/22 22:11, Samuel Sieb wrote:
> > On 12/16/22 21:18, ToddAndMargo via users wrote:
> >> On 12/16/22 20:23, Mike Wright wrote:
> >>> 127.0.0.0/8 is the loopback address. That means that any IP that
> >>> begins with 127 is a valid loopback address. The three 0's can each
> >>> be any number from 0 through 255.
> >>
> >>
> >> So the 127.0.0.53 was the bind guys being sneaky!
> >
> > That's not bind. systemd-resolved is on 127.0.0.53 and 127.0.0.54 on my
> > system. bind would most likely try to get 127.0.0.1 as you demonstrated
> > in your other email. If you want systemd-resolved to use your bind
> > server instead of the dhcp offered one, then modify
> > /etc/systemd/resolved.conf to set 127.0.0.1 as the primary DNS server.
>
> Named/bind uses port 53
>
> $ grep -i 53 /etc/services
> domain 53/tcp # name-domain server
> domain 53/udp
>
>
> Everything is commented out in my
> /etc/systemd/resolved.conf
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
1 year, 5 months
Re: No nameserver found after kernel upgrade
by Tom Horsley
On Sat, 14 Jan 2023 20:39:49 +0100
lejeczek via users wrote:
> I wonder now, if it is possible, nowadays, to "bypass"
> systemd's resolver - except if a separate DNS server is ran
> locally.
Just disable (and mask for belt and suspenders) systemd-resolved.
Then edit /etc/NetworkManager/NetworkManager.conf and add
dns=none after the "[main]" section, then you can remove the
/etc/resolv.conf symlink and replace it with a real file
you can point to your real server and network manager and
systemd will leave you alone :-).
I do that, plus run dnsmasq as a local dns server for my lan
which picks up all the names from /etc/hosts so everyone
on the local network can talk (as long as my main server is up,
anyway :-). Of course, I also have to tell the DHCP on my
router to inform everyone to point to my local server for DNS.
1 year, 4 months
Re: what is my dns?
by Tim
On Mon, 2023-04-03 at 20:26 +0200, Petr Menšík wrote:
> dnsmasq allows you to query servers using dig @localhost ch txt
> servers.bind. But no other server implements it.
Huh, what? "dig" comes from bind-utils, utilities for the BIND server.
There's also "rndc" to twiddle with BIND from the command line.
> Servers like bind, unbound or knot-resolver do not require forwarders
> to work. It may work just fine even without them.
They *should* always work fine without them, unless you have a peculiar
ISP which interferes with normal DNS functionality. But the original
poster used them on purpose, to indirectly use the internet with
external censorship filtering.
--
NB: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
The following system info data is generated fresh for each post:
uname -rsvp
Linux 6.2.8-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Mar 22 19:14:19
UTC 2023 x86_64
1 year, 1 month
Re: Certbot error
by Tom Horsley
On Sun, 23 Apr 2023 15:10:58 +0100
Patrick O'Callaghan wrote:
> BTW 'certbot certonly ..." also failed. I'm 99% sure this is a problem
> with my Apache installation.
Well, the apache documentation is only 11,371 pages, so it should
be easy to find :-).
That's basically why I'm using dnsmasq now instead of named.
1 year, 1 month
Re: freaking TFTP
by Chris Adams
Once upon a time, lejeczek <peljasz(a)yahoo.co.uk> said:
> 2nd meanwhile - I'm trying _dnsmasq_ which I'm new to thus errors
> are possible but... it seems that the same issue remains.
>
> with _dnsmasq_. tftp client - as with in.tftp as the server - "times
> out" but _dnsmasq_ server thinks and says that:
I use dnsmasq's TFTP server on a bridge, with this config:
bind-interfaces
interface=br0
port=0
enable-tftp
tftp-root=/srv/tftpboot
"port=0" disables DNS, and I then don't configure DHCP, so it's just a
TFTP server.
--
Chris Adams <linux(a)cmadams.net>
6 months, 3 weeks
Re: freaking TFTP
by lejeczek
On 07/11/2023 15:42, Chris Adams wrote:
> Once upon a time, lejeczek <peljasz(a)yahoo.co.uk> said:
>> 2nd meanwhile - I'm trying _dnsmasq_ which I'm new to thus errors
>> are possible but... it seems that the same issue remains.
>>
>> with _dnsmasq_. tftp client - as with in.tftp as the server - "times
>> out" but _dnsmasq_ server thinks and says that:
> I use dnsmasq's TFTP server on a bridge, with this config:
>
> bind-interfaces
> interface=br0
> port=0
> enable-tftp
> tftp-root=/srv/tftpboot
>
> "port=0" disables DNS, and I then don't configure DHCP, so it's just a
> TFTP server.
>
I started with that - got logs as shown in my last email.
One thing I should perhaps mention, is that libvirt uses my
NM bridges, but it's simple:
-> $ virsh net-dumpxml 10_1_1
<network>
<name>10_1_1</name>
<uuid>864fb78e-0fb0-4c32-bb47-0e5ac68d9491</uuid>
<forward mode='bridge'/>
<bridge name='nm-bridge1011'/>
</network>
and I guess, but that does not "add" to on-bare-metal NM
bridge.
6 months, 3 weeks
Re: freaking TFTP
by lejeczek
On 07/11/2023 15:42, Chris Adams wrote:
> Once upon a time, lejeczek <peljasz(a)yahoo.co.uk> said:
>> 2nd meanwhile - I'm trying _dnsmasq_ which I'm new to thus errors
>> are possible but... it seems that the same issue remains.
>>
>> with _dnsmasq_. tftp client - as with in.tftp as the server - "times
>> out" but _dnsmasq_ server thinks and says that:
> I use dnsmasq's TFTP server on a bridge, with this config:
>
> bind-interfaces
> interface=br0
> port=0
> enable-tftp
> tftp-root=/srv/tftpboot
>
> "port=0" disables DNS, and I then don't configure DHCP, so it's just a
> TFTP server.
>
I also should have added that it's Centos I'm doing all this
on, with kernel from _elrepo_
Anybody here do/use Centos that way, with net bridges?
6 months, 3 weeks
Re: Getting DHCP to work/f10 declines to start network
by tom
On Sun, 21 Dec 2008, Anoop wrote:
> On Sun, Dec 21, 2008 at 11:48 PM, tom <tfreeman(a)intel.digichem.net> wrote:
>>
>> I'm giving f10 a try on a new disk, and therefor a fresh install.
>> I'm supposed to be picking up (and was with f8) the ip4 address
>> from a dnsmasq server via dhcp, but f10 is barfing. Well, not
>> entirely, as the IP6 style networking shows on ifconfig, but since
>> I don't want IP6 networking at this moment, that isn't exactly
>> usefull.
>>
>> Now since I dislike Network Manage on a desktop machine, and would
>> prefe to have the network come up during boot, what is the prefered
>> way to get rid of Netwreck Mangler (sp?), and bring the network
>> up the old fashioned way.
> Disable 'NetworkManager' and enable 'network' service. You can do that
> by running 'setup' on your shell. Then you can edit interface related
> files in '/etc/sysconfig/networking/' to setup addresses. I am
> suggesting this because, 'system-config-network' has some issues of
> late.
>
Ok. Yet another fresh install. Disabled "NetworkManager" and enabled
"network". Going with dhcp, I get hung at boot "Determining IP information
for eth0." Hard hung as big red switch time.
Things do seem to be willing to work if I set the IP address by hand, and
not have dhclient try to do the job.
Is the dhcp system busted here? Or am I nuts?
>>
>> I'd love to see pointers or suggestions on trouble shooting this
>> type issue also.
>>
>> And now to go pester fiend Google and find out how little I
>> understand 8-/.
>>
>> Thanks for the assistance.
>>
>> --
>> fedora-list mailing list
>> fedora-list(a)redhat.com
>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>
>
>
15 years, 5 months
Re: What are your unsatisfied NetworkManager use cases?
by Michael H. Warfield
On Wed, 2008-10-22 at 13:23 -0500, Arthur Pemberton wrote:
> Many people seem to have different issues with NetworkManager. I would
> like to attempt to assist with the progress of NetworkManager by
> collecting use cases which it does not cover at all or properly.
> So please reply with a use case that you have that is not covered, I
> will attempt to collect clarify and log them on the wiki (just
> reactivated my account).
> For my sake please do one use case per email.
Last time I looked, there was no way to prevent NetworkManager from
screwing over /etc/resolve.conf. I have several cases where I want to
run a local caching nameserver (dnsmasq or bind) and/or need statically
configured IPv6 name servers (IPv4 dhcp can not hand out IPv6 nameserver
addresses and NetworkManagers IPv6 support is non-existent - another
issue) and need to have NetworkManager keep it's bleeping hands off
resolve.conf.
This was trivial under the network scripts. Just set PEERDNS=no.
I got so fed up with NetworkManager overriding my specified
resolve.conf that I finally made it immutable. I was also using
dhclient hook scripts to update the dns configuration files but I
understand that might be possible under the NetworkManger directories.
I never found any way to prevent it from committing not-so-random acts
of terrorism to /etc/resolve.conf, though.
Bottom line is failure to support or honor full range of configuration
options available under ifcfg-{interface}.
For me. That's a hard stop show stopper. You can not take features
away that people are using.
NetworkManager seems great for wireless and I use it for wireless but
it just seems like a great big PITA for wired.
> --
> Fedora 9 : sulphur is good for the skin
> ( www.pembo13.com )
Mike
--
Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
15 years, 7 months
