• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

lynx nonexistant.tld redirects to Plesk Default Page????

UweP

Regular Pleskian
Hi. I have installed a link checker on my wordpress installation. This link checker though, doesnt find some links as broken because somehow requests to for example http://nonexistant.tld get somehow redirected or reach somehow a plesk default page the author of the link checker plugin says to the plugin it seems like it successfully connected to http://nonexistant.tld (no redirect). Any idea what could be causing this?
 
Last edited:
Hi UweP,

please make it easier for us to understand your issue: Link to the wordpress plugin - page and include log - files for investigations, because we can only guess what happens on your server, which is a bad idea for investigations. An explanation like "it seems like" will only lead to guessing and not to investigaitions to solve your issue.
 
also a ping nonexistant.tld gives me:
PING nonexistant.tld.freakyonline.de (176.9.83.139) 56(84) bytes of data.
64 bytes from baby.freakyonline.de (176.9.83.139): icmp_req=1 ttl=64 time=0.017 ms
64 bytes from baby.freakyonline.de (176.9.83.139): icmp_req=2 ttl=64 time=0.019 ms
64 bytes from baby.freakyonline.de (176.9.83.139): icmp_req=3 ttl=64 time=0.025 ms
64 bytes from baby.freakyonline.de (176.9.83.139): icmp_req=4 ttl=64 time=0.024 ms
 
PING nonexistant.tld.freakyonline.de (176.9.83.139) 56(84) bytes of data.

Please don't try to ping a subdomain, configured as "nonexistant.tld.freakyonline.de", because the result will always redirect to the main - domain "freakyonline.de" ( 176.9.83.139 ) due to the case that the reverse DNS is set as "freakyonline.de. A 86400 176.9.83.139". You current DNS setting at your provider Hetzner is your primary nameserver and a ping to anything with "freakyonline.de" will therefore be redirected to your server named as "baby.freakyonline.de" with the IP "176.9.83.139".

You already contacted the author of the plugin ( https://wordpress.org/support/topic/not-finding-a-fake-broken-link ) and gave him FTP and WP-Admin - access - so he will investigate the issue for you.


Please be aware that this forum is related to PLESK issues/problems/solutions/suggestions.
 
he already investigated and told me about the plesk page showing. the problem is this:
root@baby ~ # ping nonexistant.tld
PING nonexistant.tld.freakyonline.de (176.9.83.139) 56(84) bytes of data.
64 bytes from baby.freakyonline.de (176.9.83.139): icmp_req=1 ttl=64 time=0.015 ms
64 bytes from baby.freakyonline.de (176.9.83.139): icmp_req=2 ttl=64 time=0.021 ms
64 bytes from baby.freakyonline.de (176.9.83.139): icmp_req=3 ttl=64 time=0.026 ms

as u can see i didnt ping the subdomain of my domain, but instead it somehow reached baby.freakyonline.de and i have no idea how or why. maybe it's not plesk related but i thought maybe someone could help me.
 
Hi UweP,

how did you configure your resolv.conf ( etc/resolv.conf ) from bind ( nameserver ) on your server?
 
resolv.conf:
### Hetzner Online AG installimage
# nameserver config
nameserver 213.133.100.100
nameserver 213.133.98.98
nameserver 213.133.99.99

I didn't configure anything bind (nameserver) as i dont use it. i use the nameservers from my hosting provider.
 
though the nameserver runs. but i just stopped it tried it again and it's still doing the same. but i use different nameservers. none of the resolv.conf entries point to my server.
 
Hi UweP,

could you please post your /etc/hosts - file, to see, if there are any misconfiguration(s)?

The program "ping" uses the locally configured adresses in your host - file, while "host" and "nslookup" for example use nameservers. If you use "ping" on your own server, it will redirect you to 127.0.0.1, or the additional configured adresses. Non - existent domains, which can't be resolved through a nameserver, will be redirected to your local IP and its depending ipv4 and ipv6 adresses.


Your plugin should find the non - existent link to "http://www.nonexistant.tld/", because this link goes into the nirwana, while "http://w-shadow.com/no-such-page-here/" is an existing link.
The link "...tutorials/nonexistant" is being redirected by wordpress to the wordperss - 404 - error - page, because your worpress - settings are set this way for 404 - pages.
I don't get redirected to any "Plesk default page" at all.
 
### Hetzner Online AG installimage
# nameserver config
# IPv4
127.0.0.1 localhost
#
# IPv6
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
176.9.83.139 baby.freakyonline.de baby
 
No. Only the server itself finds the plesk page when trying to reach nonexistant urls.
 
# IPv4
127.0.0.1 localhost
#

The correct usage is:
PHP:
127.0.0.1    localhost.localdomain    localhost
You could as well uncomment the IPv6 - parts, if you don't use IPv6 on your server.

Apart from that, some reviews from "https://wordpress.org/support/view/plugin-reviews/broken-link-checker" point to issues/problems as described and complain as well about enormous MySQL - queries and high server loads while using this plugin.


The plugin seems to use the "-L" - option, when checking an URL, which means, that it allows curl to follow a link with the http status code 302 ( moved temporarily ), instead of stopping the request and answering with a false positive.
 
Back
Top