=== JanC_ is now known as JanC [17:05] Hey guys. I'm running a script to get files from a server to Linux, but I always get: scp: ambiguous target. The file path has no spaces, very strange. [17:05] sshpass -p "$PASSW" scp -v -d -t $USER@$SERVER:"E:/Backup/PortalComunicacao/PortalComunicacao_backup_`date +%d-%m-%Y`*.bak" /opt/Allan [17:29] AllanLinux: are you sure there's a '-d' option to scp? [17:32] What is the remote scp server, eopnssh on WSL? Is the remote path format acceptable to the remote server? [17:32] scp doesn't have -t (tty force) either [17:33] the actual issue is probably the lacking trailing slash on the local path, though: if /opt/Allan is a directory, then make it /opt/Allan/ instead [17:33] won't the *.bak get expanded by the local shell? [17:34] probably that, too, due to double quotes. [17:35] the remote syntax threw me but I assume it is just the Windows/CIFs way [20:17] Greetings. I'm in the process of moving from 14.04 LTS to 18.04, and I'm finding a number of strange things [20:18] Annoyed: just explain what you're struggling with and people will help if they can [20:20] The current question is name resolution. This is gonna be a nameserver for my local network, but it doesn't seem to have BIND installed by default. Is that correct? [20:20] Annoyed: by default BIND is not installed, correct. [20:20] you would have to install BIND and set it up accordingly [20:22] That I expect to have to do. Byt I have not yet installed it. AS of now, nslookup at the command prompt gives me 127.0.0.53 as the responding server.. IS there already another DNS server that comes with this ? [20:23] Annoyed: 127.0.0.53 tells us that systemd-resolved is in use [20:23] So, there is another nameserver installed [20:24] Annoyed: no [20:24] that's a local resolver system inbuilt to the systemd locally [20:24] it's *not* a NameServer that you would want to use to serve DNS to the local network itself [20:24] or is that forwarding to the ISP's servers and claiming to do it itself? [20:24] you can configure it to use your BIND instance once you set it up for recursive DNS [20:25] Annoyed: forwarding to the ISP servers configured by DHCP or in your static netowrk config [20:26] Ok, will bind's install scripts change that? or how do I tell it to use BIND instead of whatever it is using. I've gathered that it's not as simple as a simple file edit as it was in 14.04 [20:30] Annoyed: you would configure your network settings to use 127.0.0.1:53 as your nameserver - that should make it point to BIND [20:31] your computer would still use systemd-resolved to issue DNS quereies, but it'll just query your BIND server directly localy [20:31] but configure the BIND server first and make sure lookups work right ;) [20:31] THEN mess with the local system's DNS [20:33] I've still got all the config (actually, the entire old hard drive) stored on this, so I can copy the old config directly, that has worked for years. So that's not an issue.. problem is telling the damned system to use it [20:38] Thanks [20:39] I'll see what happens when I try to set it up. [20:40] Oh, PS: TJ- what you were helping me w/ earlier is a PITA. Nothing that uses that inside interface works if nothing is plugged into it.. Had to get an old router to plug into it to keep it up. [20:43] I am trying to join my Ubuntu 18.04 LTS server to an AD [20:43] net join works [20:44] but I can't log on to the server with credentials of a domain user [20:44] I'm using sssd + realmd and stuff