strange addresses in system-log, is it normal?

Discussion in 'General' started by jjsjjs, Dec 7, 2021.

Tags:
  1. jjsjjs

    jjsjjs Member

    Hi,

    just to ask if strange addresses, which have nothing to do with my server, popping up in system-log is normal?
    example:
    Code:
    named[471]: address not available resolving 'ns1.first-ns.de/A/IN': 2001:67c:1011:1::53#53
Dec 7 14:48:27  named[471]: address not available resolving 'ns1.first-ns.de/AAAA/IN': 2001:67c:1011:1::53#53
Dec 7 14:48:27 named[471]: address not available resolving 'ns1.first-ns.de/A/IN': 2a02:568:0:2::53#53
Dec 7 14:48:27 named[471]: address not available resolving 'ns1.first-ns.de/AAAA/IN': 2a02:568:0:2::53#53
Dec 7 14:48:27 named[471]: address not available resolving 'ns1.first-ns.de/A/IN': 2001:668:1f:11::105#53
Dec 7 14:48:27 named[471]: address not available resolving 'ns1.first-ns.de/AAAA/IN': 2001:668:1f:11::105#53
Dec 7 14:48:27 named[471]: address not available resolving 'ns1.first-ns.de/A/IN': 2a02:568:fe02::de#53
Dec 7 14:48:27 named[471]: address not available resolving 'ns1.first-ns.de/AAAA/IN': 2a02:568:fe02::de#53
Dec 7 14:48:27 named[471]: address not available resolving 'ns1.first-ns.de/A/IN': 2003:8:14::53#53
Dec 7 14:48:27 named[471]: address not available resolving 'ns1.first-ns.de/AAAA/IN': 2003:8:14::53#53
Dec  7 14:48:27 named[471]: SERVFAIL unexpected RCODE resolving '1.0.0.127.bl.blocklist.de/A/IN': 46.252.24.212#53
Dec  7 14:49:38 named[471]: address not available resolving 'dns03.manitu.de/A/IN': 2001:4c80:64:360::7:0#53
Dec  7 14:49:38 named[471]: address not available resolving 'dns03.manitu.de/AAAA/IN': 2001:4c80:64:360::7:0#53
Dec  7 14:49:38 named[471]: address not available resolving 'dns03.manitu.de/A/IN': 2a00:1828:1000:1148::2#53
Dec  7 14:49:38 named[471]: address not available resolving 'dns03.manitu.de/AAAA/IN': 2a00:1828:1000:1148::2#53
Dec  7 14:49:38 named[471]: address not available resolving 'dns03.manitu.de/A/IN': 2a00:1828:1000:1149::2#53
Dec  7 14:49:38 named[471]: address not available resolving 'dns03.manitu.de/AAAA/IN': 2a00:1828:1000:1149::2#53
Dec  7 14:49:38 named[471]: address not available resolving '_.dnsbl.manitu.net/A/IN': 2a03:4000:5c:d89::1#53
    Is something not good configured or is it a bad bot trying to getting access ?

    Thanks for a bit of insight.
     
    jjsjjs, Dec 7, 2021
    #1
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Can that host resolve those names? Check with
    Code:
    host ns1.first-ns.de
host dns03.manitu.de
    If those do not work (and command host is installed) try troubleshooting name service, my signature has link to DNS tutorial.
     
    Taleman, Dec 8, 2021
    #2
  3. jjsjjs

    jjsjjs Member

    Those commands give me this:
    Code:
    ns1.first-ns.de has address 213.239.242.238
ns1.first-ns.de has IPv6 address 2a01:4f8:0:a101::a:1
and
dns03.manitu.de has address 217.11.50.200
dns03.manitu.de has IPv6 address 2a00:1828:1000:1150::2
    similar if I do that on my own pc as via putty logged in as root.
    It has nothing to do with my server or VPS provider. I have no idea where this is coming from.
     
    jjsjjs, Dec 8, 2021
    #3

Share This Page