[Dnssec-trigger] next version of dnssec trigger

Tomas Hozza thozza at redhat.com
Tue Apr 15 13:05:47 UTC 2014


----- Original Message -----
> On Tue, Apr 15, 2014 at 05:49:28AM -0400, Pavel Simerda wrote:
> > > it would probably be
> > > nice to know that we are planning to release a new version of
> > > dnssec-trigger very soon.
> > 
> > Hi,
> > 
> > could we coordinate a little bit? I have some important changes to the
> > integration with NetworkManager and would like to deliver them in time for
> > the next release.
> 
> Having just installed dnssec-trigger on Fedora 20, I'm having trouble
> with it noticing when I change wireless networks with NetworkManager.
> The forwarders aren't being changed, so it still shows the old DNS
> server addresses as cache in "dnssec-trigger-control status".  Is this
> a known issue that will be addressed?  I don't think the dispatcher
> scripts are running because I don't see any of the messages showing up
> in the journal.
> 
> NetworkManager-0.9.9.0-34.git20131003.fc20.x86_64

Hi.

This is not a known issue AFAIK. I'm running dnssec-trigger with NM
on Fedora 20 and it works OK and seamless most of the time.

Can you please do some more debugging? Please make sure the dispatcher
script is where it should be and it's executable.

If you are connected to a wired network at the same time when you are
changing wireless networks, the dispatcher script will use the DNS
servers from NM default connection (which is most of the time the
wired connection). You can check all your active connections using
'nmcli c s' and see which one is default. Then just use the same
command with the UUID of the connection in the end to see DNS
servers provided with it. It may bring some light on why is this
happening.

The dispatcher script also logs actions it does, but if there no change
it will do nothing. However the global forwarders are configured on
any network change.

Feel free to post some more information so we can resolve it somehow.
You can also create a Bug in Red Hat Bugzilla and we can discuss it
there.

Regards,
-- 
Tomas Hozza
Software Engineer - EMEA ENG Developer Experience

PGP: 1D9F3C2D
Red Hat Inc.                               http://cz.redhat.com



More information about the dnssec-trigger mailing list