serverfault.com

The answers to updating the email server made me think about my current DNS settings at my Domain Registrar. 1.) DNS Settings What are the correct DNS settings for an Email Server, that also hosts postfixadmin on a subdomain (postfixadmin.domain.tld ) and uses apache webserver for Let's Encrypt (LE) certs? The Multi-Domain Email Server, sends and receives emails for multiple domains (dogs.tld, cats.tld, etc. ), managed by postfixadmin using virtual mailboxes. For simplicity the DKIM and DMARC settings are not included in the Screenshot below, nor are the settings found in the screenshot concerning the domains used in this scenario. The domain and IP are in the screenshot are redacted. The "n" is the first letter of the domain.tld The A Record @ has an IP as Value The CNAME Record mx has the value domain.tld The CNAME Record postfixadmin has t

I have two systems: System A: Windows 11 System B: Windows Server 2019 My requirement is to mount the disk of System B on System A so that it appears as a locally attached disk. In simple terms, I want to enter only the IP address of System B on System A, and then be able to see the complete disk details of System B, including: Physical disk view (disk layout, partitions, sector-level information) Logical view (volumes, file systems, and files) On Windows Server, I am facing a limitation while trying to achieve this using built-in tools only. Windows does not allow exporting a physical disk directly by specifying its device path (for example \.\PhysicalDrive1). Instead, Windows requires the disk to be converted into a VHDX file before it can be shared using the built-in iSCSI Target Server role. When I attempt to map the physical disk directly using the following command: Add-IscsiServerTargetMapping -TargetName �

We'd like to limit the source IP CIDR for M2M requests obtaining tokens. In a large organization, we have multiple AWS accounts for different departments. It's common enough for Application Client's to be allocated by one team to another to allow the other team to access specific services. However when we do this we'd like to ensure that the other team requests tokens via a passthrough on our own VLAN. We've had an incident of another team requesting tokens directly from Cognito itself rather than going to our passthrough and the result was a pretty large AWS bill. Is there a way that we can set a policy on an application client or user pool such that tokens will only be given to clients originating on our own VLAN?

I’m stuck and hoping someone here can help. I forgot the password for my Gmail account and I’m unable to recover it. The main issue is with the recovery email I had set up. My email is something like: [email protected] But for the recovery email, I mistakenly added: [email protected] (without the dot) As we know, Gmail treats emails with and without dots as the same account. So effectively, my recovery email is the same Gmail account I’m locked out of. During recovery: I do receive and enter the OTP sent to my registered mobile number But after that, Google still asks for an OTP sent to the recovery email Since I can’t access that email (it’s the same account), I’m completely stuck Has anyone faced this issue before? Is there any way to bypass the recovery email step or contact Google support for this kind of situation? Any advice would really help. Thanks in advance.

I am trying to set up a Windows 11 Azure Virtual Desktop that has access to an Azure file share via a mapped drive letter. I created the File Share and can connect to it just fine from my own workstation running Windows 11, using net use S: "\\mystorageaccount.file.core.windows.net\sharename", or New-PSDrive -Name S -PSProvider FileSystem -Root "\\mystorageaccount.file.core.windows.net\sharename" or New-SMBMapping However, I get System error 67 any time I try to mount the exact same path from any Azure machine. The hostname is found by nslookup and Test-Connection -ComputerName mystorageaccount.file.core.windows.net -Port 445 I also created a Windows Server 2022 VM to try and replicate it with an older OS, and it was exactly the same. I am authenticating using the Storage Account Key. The File Share is in the same region as the VM. I don't have any Azure Firewalls

I have Nginx running in Docker on Ubuntu 22.04 To rotate logs, I use Logrotate 3.19 After the upgrade from Ubuntu 20.04 to 22.04, Nginx stoped writing to new access.log after rotation. Manually running logrotate would run without errors and Nginx starts writing to new file. I have no idea where to look for problem here. Nginx just writes 8Gb to access.log.1 until there is no space left on device. Logrotate config file is default, not altered: /var/log/nginx/*.log { daily missingok rotate 14 compress delaycompress notifempty create 0640 www-data adm sharedscripts prerotate if [ -d /etc/logrotate.d/httpd-prerotate ]; then \ run-parts /etc/logrotate.d/httpd-prerotate; \ fi \ endscript postrotate invoke-rc.d nginx rotate >/dev/null 2>&1 endscript }

Server OS - windpws server 2022 troubleshooting leVel - L2 Need step by step process. Server is in production, Mention service or process that could be stopped to reduce utilization and also tell which service or process cannot be stopped in production.

I created a new debian 13 server, and proftpd is failing because the file '/etc/ssh/ssh_host_dsa_key' does not exist. proftpd has lines with this content: SFTPHostKey /etc/ssh/ssh_host_rsa_key SFTPHostKey /etc/ssh/ssh_host_dsa_key The error message for proftpd: 2026-01-27 16:04:26,720 example proftpd[42786]: fatal: SFTPHostKey: unable to check '/etc/ssh/ssh_host_dsa_key': No such file or directory on line 13 of '/etc/proftpd/conf.d/sftpd.conf' I looked into debian bugs to see if there's mention of removing the ssh_host_dsa_key file, but I couldn't find anything. I will remove the line with the error and stay with the rsa key, but I'd like to find the cause.

I installed proxmox on a DELL PowerEdge C6400 with a Broadcom BCM57416, using the driver bnxt-en. The ethernet controller is recognized with lspci | grep -i ethernet, and the interfaces are configured but are DOWN. The LEDs do not turn on when connected to the cable, but I'm sure it's not the cable because I exchanged the cables with the iDRAC port and both work correctly. Running ethtool -t nic0 fails at Link test (online) and Ext loopback test (offline). I looked at dmesg and journalctl but I didn't find meaningful information.

My DigitalOcean droplets are compromised and used for DDoS attacks. This is the third occurrence. Each time I destroy the droplet, start from scratch, add more security, and within a day it occurs again. Is there something in the application code that is exploited? Are GitHub Actions deployment pipeline compromised? Is there something at the DigitalOcean account level that could be the issue? Node.js application with Docker containers, PostgreSQL and Redis, Nginx as reverse proxy, Deploying via GitHub Actions Security measures implemented: SSH: Disabled password auth, disabled root login, using ED25519 keys only, changed default port, added fail2ban Firewall: UFW configured, only ports open are custom SSH port, 80, and 443 System: Auto security updates, removed unnecessary services, non-root user for everything Docker: Isolated containers, proper networking Full cre