I want my Apache web server running on a Livebox (home router appliance running Linux) to be accessible from the Internet (WAN). I installed and configured the application noip2 on my Ubuntu PC. When I ping my hostname, it redirects me to my WAN ip, which is what I wanted. But I cannot access my Apache web server. I tried this: - Disabling the iptables firewall configuration or the firewall of my Sagem modem. - Port forwarding on sagem modem (NAT). - Configuration of Apache. What else can I try? How can I make my web server accessible from the WAN side?

I have two DNS servers for different zones: subdomain.example.com (subdomain) example.com (main domain) The goal is to dynamically transfer A records from subdomain.example.com to example.com without using scripts, full zone transfers. Here are the constraints and requirements: The two servers have different SOA records and configurations. I cannot use scripts, zone transfers (AXFR) for synchronization. The A records need to be added automatically to the example.com zone without overwriting existing records. Can anyone help with the configuration steps and advice on how to set this up? Ideally, I need to ensure: Secure and authenticated updates between the servers. Only the A records should be transferred. No existing data in the example.com zone should be overwritten.

I'm working on setting up DNS and DHCP on my homelab network using BIND9 and Kea, and I'm having trouble getting my zone files to update consistently. My setup is BIND 9.18.26 and Kea 2.4.1 on the same FreeBSD 14.0 server; clients are an assortment of FreeBSD, Debian-based, Android and a couple of commercial IoT devices, with a mixture of static, reserved and dynamic addresses. Kea (so far as I can tell) is handing out all addresses, including the reserved addresses, correctly, but is not passing addresses to BIND, and since I have no idea what I'm doing, I appeal to those who do. My configuration is as follows:

// named.conf
include "/usr/local/etc/namedb/tsig.key";
include "/usr/local/etc/namedb/named.conf.options";
include "/usr/local/etc/namedb/named.conf.local";
include "/usr/local/etc/namedb/named.conf.default-zones";

acl internal-net {
        localhost;
        192.168.0.0/24;
};

server ::/0 {
        bogus yes;
};

// named.conf.options

options {
        // All file and path names are relative to the chroot directory,
        // if any, and should be fully qualified.
        directory       "/usr/local/etc/namedb/working";
        pid-file        "/var/run/named/pid";
        dump-file       "/var/dump/named_dump.db";
        statistics-file "/var/stats/named.stats";

        allow-query { internal-net; };
        allow-query-cache { internal-net; };
        allow-recursion { internal-net; };
        allow-transfer { none; };

        check-names master ignore;
        check-names slave ignore;
        check-names response ignore;

        forwarders {
                149.112.121.20;
                149.112.122.20;
        };
};

// named.conf.local
//
// Local configuration goes here
//

zone "voncorax.internal" {
        type            master;
        file            "/var/lib/named/voncorax.internal.hosts";
        allow-update    { key tsig-key; };
};

zone "0.168.192.in-addr.arpa" {
        type            master;
        file            "/var/lib/named/0.168.192.rev";
        allow-update    { key tsig-key; };
};

tsig.key:

key "tsig-key" {
        algorithm hmac-sha256;
        secret "Shh! It's a secret!";
};

kea-dhcp4.conf:

{
        "Dhcp4": {
                "valid-lifetime": 300,
                "interfaces-config": {
                        "interfaces": [ "em0" ]
                },
                "lease-database": {
                        "type": "memfile",
                        "persist": true,
                        "name": "/var/lib/kea/dhcp4.leases"
                },
                "subnet4": [
                        {
                                "id": 1,
                                "subnet": "192.168.0.0/24",
                                "pools": [
                                        {
                                                "pool": "192.168.0.100-192.168.0.254"
                                        }
                                ],
                                "option-data": [
                                        {
                                                "name": "routers",
                                                "data": "192.168.0.1"
                                        }
                                ],
                                "reservations": [
                                        {
                                                "hw-address": "dc:a6:32:12:2f:d2",
                                                "hostname": "dnsbox.voncorax.internal",
                                                "ip-address": "192.168.0.2"
                                        },
                                        {
                                                "hw-address": "b8:ca:3a:7d:69:ad",
                                                "hostname": "prometheus.voncorax.internal",
                                                "ip-address": "192.168.0.98"
                                        }
                                ]
                        }
                ],
                "option-data": [
                        {
                                "name": "domain-name-servers",
                                "data": "192.168.0.97, 192.168.0.2"
                        }
                ],
                "loggers": [
                        {
                                "name": "kea-dhcp4",
                                "output_options": [
                                        {
                                                "output": "/var/log/kea-dhcp4.log"
                                        }
                                ],
                                "severity": "INFO",
                                "debuglevel": 1
                        }
                ],
                "ddns-send-updates": true,
                "ddns-qualifying-suffix": "voncorax.internal",
                "ddns-override-no-update": true,
                "ddns-override-client-update": true,
                "dhcp-ddns": {
                        "enable-updates": true,
                        "server-ip": "127.0.0.1"
                }
        }
}

kea-dhcp-ddns.conf:

{
        "DhcpDdns":
        {
                "ip-address": "127.0.0.1",
                "port": 53001,
                "control-socket": {
                "socket-type": "unix",
                "socket-name": "/tmp/kea-ddns-ctrl-socket"
        },
        "tsig-keys": [
                {
                        "name": "tsig-key",
                        "algorithm": "hmac-sha256",
                        "secret": "Shh! It's a secret!"
                }
        ],
        "forward-ddns" : {
                "ddns-domains": [
                        {
                                "name": "voncorax.internal.",
                                "key-name": "tsig-key",
                                "dns-servers": [
                                        {
                                                "ip-address": "192.168.0.97"
                                        }
                                ]
                        }
                ]
        },
        "reverse-ddns" : {
                "ddns-domains": [
                        {
                                "name": "0.168.192.in-addr.arpa.",
                                "key-name": "tsig-key",
                                "dns-servers": [
                                        {
                                                "ip-address": "192.168.0.97"
                                        }
                                ]
                        }
                ]
        },

        "loggers": [
                {
                        "name": "kea-dhcp-ddns",
                        "output_options": [
                                {
                                        "output": "/var/log/kea-ddns.log"

                                }
                        ],
                        "severity": "INFO",
                        "debuglevel": 1
                        }
                ]
        }
}

I'm basing my work on Lee Hutchinson's Ars Technica article Doing DNS and DHCP for your LAN the old way—the way that works along with my reading of the BIND 9 and Kea documentation. Can anyone see what I'm doing wrong? EDIT: Here is the log output from kea-ddns:

2024-05-28 12:02:48.657 DEBUG [kea-dhcp-ddns.dhcpddns/10658.0xf2290c12000] DHCP_DDNS_CONFIGURE configuration update received: { "control-socket": { "socket-name": "/tmp/kea-ddns-ctrl-socket", "socket-type": "unix" }, "forward-ddns": { "ddns-domains": [ { "dns-servers": [ { "ip-address": "192.168.0.97" } ], "key-name": "tsig-key", "name": "voncorax.internal." } ] }, "ip-address": "127.0.0.1", "loggers": [ { "debuglevel": 10, "name": "kea-dhcp-ddns", "output_options": [ { "output": "/var/log/kea-ddns.log" } ], "severity": "INFO" } ], "port": 53001, "reverse-ddns": { "ddns-domains": [ { "dns-servers": [ { "ip-address": "192.168.0.97" } ], "key-name": "tsig-key", "name": "0.168.192.in-addr.arpa." } ] }, "tsig-keys": [ { "algorithm": "hmac-sha256", "name": "tsig-key", "secret": "*****" } ] }
2024-05-28 12:02:48.657 DEBUG [kea-dhcp-ddns.dctl/10658.0xf2290c12000] DCTL_CONFIG_START parsing new configuration: { "control-socket": { "socket-name": "/tmp/kea-ddns-ctrl-socket", "socket-type": "unix" }, "forward-ddns": { "ddns-domains": [ { "dns-servers": [ { "ip-address": "192.168.0.97" } ], "key-name": "tsig-key", "name": "voncorax.internal." } ] }, "ip-address": "127.0.0.1", "loggers": [ { "debuglevel": 10, "name": "kea-dhcp-ddns", "output_options": [ { "output": "/var/log/kea-ddns.log" } ], "severity": "INFO" } ], "port": 53001, "reverse-ddns": { "ddns-domains": [ { "dns-servers": [ { "ip-address": "192.168.0.97" } ], "key-name": "tsig-key", "name": "0.168.192.in-addr.arpa." } ] }, "tsig-keys": [ { "algorithm": "hmac-sha256", "name": "tsig-key", "secret": "*****" } ] }
2024-05-28 12:02:48.659 INFO  [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_ACCEPTOR_START Starting to accept connections via unix domain socket bound to /tmp/kea-ddns-ctrl-socket
2024-05-28 12:02:48.660 INFO  [kea-dhcp-ddns.dctl/10658.0xf2290c12000] DCTL_CONFIG_COMPLETE server has completed configuration: listening on 127.0.0.1, port 53001, using UDP
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.dctl/10658.0xf2290c12000] DCTL_RUN_PROCESS DhcpDdns starting application event loop
2024-05-28 12:02:48.660 INFO  [kea-dhcp-ddns.dhcpddns/10658.0xf2290c12000] DHCP_DDNS_STARTED Kea DHCP-DDNS server version 2.4.1 started
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command build-report registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command config-get registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command config-hash-get registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command config-reload registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command config-set registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command config-test registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command config-write registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command shutdown registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command status-get registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command version-get registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command statistic-get registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command statistic-get-all registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command statistic-reset registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.commands/10658.0xf2290c12000] COMMAND_REGISTERED Command statistic-reset-all registered
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.dhcpddns/10658.0xf2290c12000] DHCP_DDNS_QUEUE_MGR_RECONFIGURING application is reconfiguring the queue manager
2024-05-28 12:02:48.660 DEBUG [kea-dhcp-ddns.dhcpddns/10658.0xf2290c12000] DHCP_DDNS_QUEUE_MGR_STARTED application's queue manager has begun listening for requests.

This isn't an excerpt; that is literally the entirety of what's been logged since I restarted the daemon several days ago. I won't post the entire log from kea-dhcp4 because it's huge, but it appears that dhcp4 is doing its thing correctly, just not talking to d2. The following is an excerpt from kea-dhcp4.log which appears (to my inexperienced eye) to be all of a piece:

2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c12000] DHCP4_BUFFER_RECEIVED received buffer from 192.168.0.98:68 to 192.168.0.97:67 over interface em0
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.options/11509.0x1a25f9c15f00] DHCP4_BUFFER_UNPACK parsing buffer received from 192.168.0.98 to 192.168.0.97 over interface em0
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_PACKET_RECEIVED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: DHCPREQUEST (type 3) received from 192.168.0.98 to 192.168.0.97 on interface em0
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_QUERY_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501, packet details: local_address=192.168.0.97:67, remote_address=192.168.0.98:68, msg_type=DHCPREQUEST (3), transid=0xd3f53501,
options:
  type=012, len=010: "prometheus" (string)
  type=053, len=001: 3 (uint8)
  type=055, len=010: 1(uint8) 28(uint8) 2(uint8) 121(uint8) 3(uint8) 15(uint8) 6(uint8) 12(uint8) 119(uint8) 26(uint8)
  type=061, len=007: 01:b8:ca:3a:7d:69:ad
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection.
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty.
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 192.168.0.0/24 for packet received by matching address 192.168.0.98
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_SUBNET_SELECTED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: the subnet with ID 1 was selected for client assignments
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_SUBNET_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: the selected subnet details: 192.168.0.0/24
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation for subnet id 1, identified by hwaddr=B8CA3A7D69AD
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: hwaddr=B8CA3A7D69AD
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER_HOST using identifier: hwaddr=B8CA3A7D69AD, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none)
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=B8CA3A7D69AD, found 1 host(s)
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST using subnet id 1 and identifier hwaddr=B8CA3A7D69AD, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none)
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcp4/11509.0x1a25f9c15f00] DHCP4_CLASS_ASSIGNED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: client packet has been assigned to the following class(es): KNOWN
2024-05-28 17:25:55.169 DEBUG [kea-dhcp4.dhcp4/11509.0x1a25f9c15f00] DHCP4_CLASS_ASSIGNED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: client packet has been assigned to the following class(es): ALL, KNOWN
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c15f00] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: processing client's Hostname option
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c15f00] DHCP4_CLIENT_HOSTNAME_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: client sent Hostname option: prometheus
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.ddns/11509.0x1a25f9c15f00] DHCP4_RESERVED_HOSTNAME_ASSIGNED [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: server assigned reserved hostname prometheus.voncorax.internal
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client ID 01:b8:ca:3a:7d:69:ad
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for subnet id 1 and IPv4 address 192.168.0.98
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address 192.168.0.98
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_ADDRESS4_HOST using address 192.168.0.98 found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none)
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address 192.168.0.98, found 1 host(s)
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.hosts/11509.0x1a25f9c15f00] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_HOST using subnet id 1 and address 192.168.0.98, found host: hwaddr=B8CA3A7D69AD ipv4_subnet_id=1 hostname=prometheus.voncorax.internal ipv4_reservation=192.168.0.98 siaddr=(no) sname=(empty) file=(empty) key=(empty) ipv6_reservations=(none)
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address 192.168.0.98
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.alloc-engine/11509.0x1a25f9c15f00] ALLOC_ENGINE_V4_REQUEST_EXTEND_LEASE [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: extending lifetime of the lease for address 192.168.0.98
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.dhcpsrv/11509.0x1a25f9c15f00] DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address 192.168.0.98
2024-05-28 17:25:55.170 INFO  [kea-dhcp4.leases/11509.0x1a25f9c15f00] DHCP4_LEASE_ALLOC [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: lease 192.168.0.98 has been allocated for 300 seconds
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.options/11509.0x1a25f9c15f00] DHCP4_PACKET_PACK [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: preparing on-wire format of the packet to be sent
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_PACKET_SEND [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: trying to send packet DHCPACK (type 5) from 192.168.0.97:67 to 192.168.0.98:68 on interface em0
2024-05-28 17:25:55.170 DEBUG [kea-dhcp4.packets/11509.0x1a25f9c15f00] DHCP4_RESPONSE_DATA [hwtype=1 b8:ca:3a:7d:69:ad], cid=[01:b8:ca:3a:7d:69:ad], tid=0xd3f53501: responding with packet DHCPACK (type 5), packet details: local_address=192.168.0.97:67, remote_address=192.168.0.98:68, msg_type=DHCPACK (5), transid=0xd3f53501,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 192.168.0.1
  type=006, len=008: 192.168.0.97 192.168.0.2
  type=012, len=028: "prometheus.voncorax.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 5 (uint8)
  type=054, len=004: 192.168.0.97
  type=061, len=007: 01:b8:ca:3a:7d:69:ad

EDIT: I've hacked around with Wireshark a bit (from a Server Fault post ) and it appears that kea-dhcp4 is not sending anything to kea-ddns over the lo0 interface. Can anyone suggest why not, or how I can figure out why not?

I have a debian router that gives my entire house VPN access, it connects to the server that is in my parent's home in another city with wireguard. I need to do this because of firewall issues. However I want to SSH back into my debian router while I'm outside. The Debian router is directly connected to a Asus Router which is then connected to the ISP's gateway (router modem combo). I've tried creating a network namespace to run my ddns update, but I can't get any network access on it. I've tried to run a cron job that disables my VPN and updates, but that is not The issue is that the no-ip DDNS client, updates with the IP address of my parent's home (which makes sense). How do I update my DDNS while running a VPN? Are there any other easy way, besides a cron job that turns off my VPN and runs the DDNS update? Update: My network namespace config

#!/bin/bash
NS="nsx"
IF_MAIN="br0"
IF_NS="br0_ns"
IP="192.168.10.2/24"
GATEWAY="192.168.1.1"

ip netns del "$NS"
ip netns add "$NS"
ip link add link "$IF_MAIN" "$IF_NS" netns "$NS" type ipvlan mode l2
ip -n "$NS" link set dev lo up
ip -n "$NS" link set "$IF_NS" up
ip -n "$NS" addr add "$IP" dev "$IF_NS"
ip -n "$NS" route add default via "$GATEWAY" dev "$IF_NS"

I have a DDNS service with noip.com, but the link I have is so hard to remember. It's working, I can resolve it using resolveip link and I get the current IP of the router. I tried to use /etc/hosts but it didn't work, it requires that I put an IP. How can I give a short name to the DDSN link I have. for example ping name , so the system would resolve name for the DDNS link. I wonder if NetworkManager or ip addr can help me. Thanks a lot.

I am the sysadmin in a small company, where we build a lot of PC-/workstation type of computers. They usually come with several LAN ports as well as WIFI on the motherboard, and because the machines are moved around and disconnected a lot, they are rarely connected in the same way every time. This leads to a few, often occurring nuisances, namely that they change IP addresses - I try to set them up in DHCP with a single address based on the MAC address, and then add them to DNS, and this breaks it, of course. I have tried to set up DDNS, but couldn't get it to work, and getting my estimed colleagues to use just the same LAN port every time appears to be just outside their capabilities; they may simply be too highly trained to focus on such mundane matters. I have also tried to set up up several MAC addresses with the same IP and hostname, but the DHCP daemon (this is on Linux) very sensibly refuses to allow it; I suppose I could change the MAC addresses on the interfaces so they are the same on the machine, but that seems an unsound thing to do. So, what can I do to tame the situation a bit? What is the best way to make sure that people don't come to me, complaining that they can't connect to humbaba, which they've just started up?

You all probably know commercial dynamic DNS providers like dyndns.org or no-ip.com. But how to create a similar service for just a handful of machines? What server software would be best suited for such a setup (under Linux)? Advantages: - the service would be under your control - no tracking by some opaque company Minimal requirements: Probably something like: you own at least one host machine with a static IP, a domain and your domain provider let you configure DNS records. Clients: A few machines that are connected via cable/DSL and only get dynamic IP addresses on each dial-up and/or every x hours.

dns-options can be changed for connection name myname to the value value using nmcli con modify myname ipv4.dns-options value Using interactive mode, I get a short description of what dns-options does. nmcli> describe ipv4.dns-options === [dns-options] === [NM property description] Array of DNS options. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. **Question**: What are the value of dns-options field and what is the purpose of dns-option?

I run a VPS which I would like to secure using UFW, allowing connections only to port 80. However, in order to be able to administer it remotely, I need to keep port 22 open and make it reachable from home. I know that UFW can be configured to allow connections to a port only from specific IP address: ufw allow proto tcp from 123.123.123.123 to any port 22 But my IP address is dynamic, so this is not yet the solution. The question is: I have dynamic DNS resolution with DynDNS, so is it possible to create a Rule using the domain instead of the IP? I already tried this: ufw allow proto tcp from mydomain.dyndns.org to any port 22 but I got ERROR: Bad source address

I am using Ubuntu 20.04 OS with dnsjava client library to query DNS servers. I have nftables rule in this machine which block all traffic on ports except ephemeral port range 32768-61000 which will be used by dnsjava to get results from DNS server. table inet tb { chain input { type filter hook input priority 0; policy drop; tcp dport 32768-61000 accept udp dport 32768-61000 accept .... .... } chain forward { .... } chain output { ..... } } It looks like allowing 32768-61000 range might be security flaw. But completely blocking this port range is adding latency in dns resolution and many failure due to timeout. Is there way we can avoid this rule allowing port range in nftables? Is there any nftable feature which we can use to avoid this without impacting dns resolution latency?

A raspberry pi at home running Rasbian Jessie 8.0 is running Apache. Using dig TXT +short o-o.myaddr.l.google.com @ns1.google.com produces an IPv4 that is used to update the value in the record sets of the hosted zone in AWS's route 53 circled in red in the following image.  Testing the domain name is successful. What I'd like to do now is update AWS Route53 whenever my home's dynamic IP address changes from within the raspberry pi with out any assistance from me. Please let me know if you require anymore information.

I [want to use the Fritzbox update feature of DDClient](https://github.com/linuxserver/docker-ddclient#get-dynamic-ip-from-fritzbox) , but also want to have a fallback to a public web server, if that does not work for some reason (e.g. cause someone just switched to another router or whatever…). As far as I known, just duplicating the use=cmd key seems to override the previous configuration?

protocol=dyndns2
use=cmd, cmd='curl https://checkipv4.dedyn.io/ '
use=cmd, cmd=/etc/ddclient/get-ip-from-fritzbox
#use=if, if=eth0
ssl=yes

server=update.dedyn.io
login=domain.dedyn.io
password='___password_here____'
domain.dedyn.io

The syntax use=cmd, cmd='curl https://checkipv4.dedyn.io/ ', cmd=/etc/ddclient/get-ip-from-fritzbox also works, but I guess it does the same, or does not it? In any case [the official documentation](https://ddclient.net/usage.html) is of little help and does not explain the configuration format in a very elaborate way. So can you actually specify a fallback in ddclient? If so, how?

On my computer I have two network cards. Both are using different Internet Providers service. Both Internet service provider have different DNS server and their IP address are known to me. I want to make sure when nslookup sends queries, it passes through exactly by specified interface. Something like: ping -I eth1 google.com nslookup -I eth1 google.com is possible by any way, I know there is no -I option, I even don't want it to be specific in that way only. How do I do it?

I'm using Debian Bullseye to run KVM (Kernel-based Virtual Machine) with two guests vdeb02-10-base and vdeb03-10-base. Both guests have Debian Buster installed. For testing purposes vdeb03-10-base is just a clone of vdeb02-10-base, using the virt-clone utility to ensure that is has unique system parameter like mac address etc. On all devices (host, guests) I use **systemd-networkd**. If I start vdeb02-10-base with DHCP enabled to get an ip address from my ISC-DHCP-Server everything works fine as shown by the log of the DHCP-Server: Oct 05 18:43:49 vnetsvr30-10 dhcpd: DHCPDISCOVER from 52:54:00:ee:f5:0a via ens1 Oct 05 18:43:50 vnetsvr30-10 dhcpd: DHCPOFFER on 192.168.30.104 to 52:54:00:ee:f5:0a (vdeb02-10-base) via ens1 Oct 05 18:43:50 vnetsvr30-10 dhcpd: DHCPREQUEST for 192.168.30.104 (192.168.30.10) from 52:54:00:ee:f5:0a (vdeb02-10-base) via ens1 Oct 05 18:43:50 vnetsvr30-10 dhcpd: Wrote 56 leases to leases file. Oct 05 18:43:50 vnetsvr30-10 dhcpd: DHCPACK on 192.168.30.104 to 52:54:00:ee:f5:0a (vdeb02-10-base) via ens1 Oct 05 18:43:50 vnetsvr30-10 dhcpd: Added new forward map from vdeb02-10-base.home.hoeft-online.de. to 192.168.30.104 Oct 05 18:43:50 vnetsvr30-10 dhcpd: Added reverse map from 104.30.168.192.in-addr.arpa. to vdeb02-10-base.home.hoeft-online.de. The dynamic DNS name is mapped to the DNS server so I can query for it with ~$ dig +search +noall +answer vdeb02-10-base vdeb02-10-base.home.hoeft-online.de. 3600 IN A 192.168.30.104 If I start then vdeb03-10-base the DHCP-Server log shows me this: Oct 05 18:44:55 vnetsvr30-10 dhcpd: DHCPDISCOVER from 52:54:00:ed:c5:df (vdeb02-10-base) via ens1 Oct 05 18:44:55 vnetsvr30-10 dhcpd: ICMP Echo reply while lease 192.168.30.104 valid. Oct 05 18:44:55 vnetsvr30-10 dhcpd: Abandoning IP address 192.168.30.104: pinged before offer Oct 05 18:44:55 vnetsvr30-10 dhcpd: Removed forward map from vdeb02-10-base.home.hoeft-online.de. to 192.168.30.104 Oct 05 18:44:55 vnetsvr30-10 dhcpd: Removed reverse map on 104.30.168.192.in-addr.arpa. Oct 05 18:44:57 vnetsvr30-10 dhcpd: DHCPDISCOVER from 52:54:00:ed:c5:df via ens1 Oct 05 18:44:58 vnetsvr30-10 dhcpd: DHCPOFFER on 192.168.30.95 to 52:54:00:ed:c5:df (vdeb03-10-base) via ens1 Oct 05 18:44:58 vnetsvr30-10 dhcpd: DHCPREQUEST for 192.168.30.95 (192.168.30.10) from 52:54:00:ed:c5:df (vdeb03-10-base) via ens1 Oct 05 18:44:58 vnetsvr30-10 dhcpd: DHCPACK on 192.168.30.95 to 52:54:00:ed:c5:df (vdeb03-10-base) via ens1 Oct 05 18:44:58 vnetsvr30-10 dhcpd: Added new forward map from vdeb03-10-base.home.hoeft-online.de. to 192.168.30.95 Oct 05 18:44:58 vnetsvr30-10 dhcpd: Added reverse map from 95.30.168.192.in-addr.arpa. to vdeb03-10-base.home.hoeft-online.de. Why does the DHCP-Server mean that the DHCPDISCOVER comes from vdeb02-10-base and not from vdeb03-10-base? Mac address and hostname are different. Of course the DHCP-Server then means there is an ip address conflict on the network using the ping test. Then it removes the DNS mapping for vdeb02-10-base and replaces it with the mapping for vdeb03-10-base with the result that I cannot resolve the name for vdeb02-10-base anymore. What's going on here? Why does the DHCP-Server replaces the hostname on the DNS-Server instead of just adding the name of the second guest? Where could be the problem? At the guests, or at the host with a standard network bridge for the guests, or at the DHCP-Server, or by using systemd-networkd? Maybe there is an option to be used in /etc/dhcp/dhcpd.conf?

I'm running ddclient on Arch Linux with Namecheap. I want to force ddclient to use only HTTPS. Ddclient is a Perl client used to update dynamic DNS entries for accounts on 'Dynamic DNS Network Services' free DNS service. In the file /etc/ddclient/ddclient.conf I have ssl=yes I don't see another ddclient config setting related to this. Is there a way I can accomplish my goal?

I have a home server connected to a router which set to use a DDNS with an integreated provider pointing to a no-ip DNS server. After a power outage my domain can't be reached any longer. Checking the IP address with dig +short pacolola.net ...I get the address 188.151.207.219. According to the router's Public IPv4 Address and No-IP's user pages it should be 188.151.218.129. Using the later address shows the page content and the server's internal IP address is also working. I've attempted to restart the network with sudo service networking restart and various DNS cache reset commands without success. How do I resolve the hostname to the IP address which the DNS servers are using? Is this a DNS problem laying with no-ip router or SLL or something on the server? What diagnostic tools are valid in this case?

I'm setting up a couple of Raspberry Pi's on my router's DMZ (don't worry all the ports are closed); my router uses DNSMasq for DNS and so I added the MAC addresses; hostnames and IPs of the pi's to the dhcp static leases. Now that said, I'm only learning to use dhcpcd; I'm used to the old way of using /etc/networking/interfaces to configure ip address assignment. On the pi's themselves, I've configured them with /etc/dhcpcd.conf as having a static ip address and pointed them at my DNSMasq DNS Server. It seems a little strange to do this, but is it okay to do so? This way my pi's get a DNS record (so the devices can find each other) and a static ip address; I suppose I could configure it so that it pulls the IP based on the MAC address using the dhcpcd client. That said I don't really know how to configure dhcpcd to pull it's ip address from DNSMasq; I'm planning on adding additional DNS records (maybe from /etc/hosts) for the pi's to pick up for separate nginx server blocks , so is it okay to have static IPs configured in dhcpcd while I have static DHCP leases configured? Or is that weird and I shouldn't do that?

I have problems with my webserver. Normally you start the No-IP-DUC via

noip2

. I tried to automate it with a cronjob. Using

-e

, I created this file:

# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h  dom mon dow   command

@reboot cd /home/username/noip-2.1.9-1 && sudo noip2

It does not work and I do not know why. It would be nice if somebody could help me.

I intend to run a debian server at home, it will host various websites, SSH server and email. I have a dynamic IP address and I am unwilling to pay the extra for a static IP. I was thinking I could probably get around the DNS issue if I ran my own name server and used something like no-ip to set auto-updated nameserver addresses for my registered domains, eg: On the registrar: john-hunt.com (and my other domains) nameservers = johnns1.noip.com & johnns2.noip.com johnns1.noip.com, johnns2.noip.com -> my dynamic IP Which will make sure that the nameservers for my domains are always pointing to my machine at home. I will run BIND or something similar on the home machine to actually serve up the DNS records. The real problem I have is that I don't quite know how I'd configure BIND (or tinydns or whatever) to accept and apply updates when my IP address changes.. I can think of a way to bodge it (poll & ping johnns1.noip.com to get my IP address, then grep on the zonefiles and reload every 5 minutes..) but that doesn't feel very solid. Does anyone have any experience in this area? I had a look at no-ip's enhanced services but they want $25 for hosting records for every domain (and I have quite a few).

I try to register my DHCP Clients to my Samba 4 based domain controller (DC). For this I followed the guide [Configure DHCP to update DNS records with BIND9](https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_with_BIND9) . I've searched around the internet without success. But there ist an issue with the Generic Security Service Application Program Interface (GSSAPI ) I don't know how to solve. So can someone help me with the following GSSAPI Error? start_gssrequest tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = No credentials found with supported encryption types (filename: /tmp/dhcp-dyndns.cc). Here is my keytab file: ktutil -k /etc/dhcpduser.keytab list /etc/dhcpduser.keytab: Vno Type Principal Aliases 2 aes256-cts-hmac-sha1-96 dhcpduser@PROD.CORP.INT 2 aes128-cts-hmac-sha1-96 dhcpduser@PROD.CORP.INT 2 arcfour-hmac-md5 dhcpduser@PROD.CORP.INT 2 des-cbc-md5 dhcpduser@PROD.CORP.INT 2 des-cbc-crc dhcpduser@PROD.CORP.INT **System Information** - Raspberry Pi 3 Model B - Raspian Stretch - Samba Version 4.7.4 - BIND Version 9.11.2 - BIND9 built by make '--prefix' '/usr/local/bind9' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr/include/gssapi' '--with-libtool' '--with-dlopen=yes' '--enable-threads' '--enable-largefile' '--with-gnu-ld' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing' 'CFLAGS=-DDIG_SIGCHASE' 'CFLAGS=-O2' **Config Files** - BIND9 [named.conf](https://pastebin.com/HW88rwbe) - Samba [named.conf](https://pastebin.com/zi7Fm27T) - Samba [smb.conf](https://pastebin.com/i1fmj56T) If more information needed, feel free and ask me, I'll do my best to provide them. Greetings Ronny