fredlGood morning folks07:27
fredlSo about 16.04 servers which have been upgraded from 16.04 to 18.04... I learned yesterday that this means that netplan is usually not set up and the old /etc/network/interfaces is still used unless other actians are taken07:28
lordievaderGood morning07:43
fredlI'm trying to find a way where for a certain domain only one DNS will be used, if that DNS is down somehow it should not try to resolve using other resolvers08:14
fredlSomebody pointed met to the networkd config yesterday instead of systemd-resolvd08:14
lordievaderIs this from the authoritative side or from the client side?08:26
fredlSituation is that we have a network gateway with a VPN tunnel to Google cloud08:55
fredlClient have a mere route for the GCP services to that gateway08:56
fredlSo I'm trying to figure out how I'd configure networkd to 1) for domain such.com go to DNS gcp ONLY, 2) for other domains use 'normal' DNS servers. In any case we need to prevent that queries for such.com NEVER go to the default DNS servers, also in case of VPN failure or so08:57
lordievaderIn that case setting up a single resolver should do what you want.08:58
fredlI tried first to simply add the Google Cloud DNS server to the list of resolvers08:58
fredlBut then the customer simulated a down VPN by blocking port 5308:59
fredlApparently that results in long, unwanted negative caching as the default DNS server can't resolve those queries then08:59
lordievaderIt should just give timeouts (which can be long), but not negative caching.09:04
fredlI configured systemd-resolved to use Cache=no-negative09:13
fredlSo it shouldn't do negative caching at all anyway09:13
fredlin debugging output that's also what I see: Not caching negative entry for: blabla.nl IN AAAA, cache mode set to no-negative09:14
fredlSo that's why I'm assuming that somehow our main DNS keeps a negative cache somehow?09:14
fredlAnd that after the VPN link goes down, perhaps systemd-resolved remembers the DNS it *got* that from and queries that one again and again09:15
fredlThat's the only plausible explanation I see.09:16
Odd_Blokerbasak: Congrats on git-ubuntu 1.0!14:49
tsukasadtHopefully an easy question: can you combine `grep` and `tail` to realtime track a log file but only get entries containing a specific string? If so, how?17:13
sdezieltsukasadt: tail -f /var/log/mylog | grep 'my pattern of interest'17:13
tsukasadtNow I really feel stupid. I had almost that, but I put the file in the grep. ^^'17:15
tsukasadtty, sdeziel17:15

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!