我的设置将本地networking上的未定义主机redirect到自定义404页面; 所以对于invalidhostname.subdomain.example.com ， bind9服务器将redirect到nginxProxy.subdomain.example.com 。 （本身redirect到另一台服务器上托pipe的404页面）
它符合本地未定义主机名称的预期 。
但是，当涉及到askljdaksjdad.com ， nslookup ， host ， dig所有正确的返回NXDOMAIN ，但google-chrome ， curl和wget都从我的子域提供自定义404页面。 它发生在networking上的多台Linux机器上。
configuration文件的相关部分是：
在绑定服务器上： /etc/bind/zones/forward.subdomain.example.com
subdomain.example.com IN SOA bind01.subdomain.example.com. nitin.subdomain.example.com ( 64 ; serial 604800 ; refresh (1 week) 86400 ; retry (1 day) 2419200 ; expire (4 weeks) 604800 ; minimum (1 week) ) NS ns02.subdomain.example.com. NS bind01.subdomain.example.com. $ORIGIN subdomain.example.com. ;* CNAME nginxProxy *.subdomain.example.com. CNAME nginxProxy nginxProxy A 192.168.1.200
在nginxProxy上： /etc/nginx/conf.d/default.conf
server { # Server:port pair that this instance of nginx is running on and should listen to for incoming connections(IP address or name) # Add "default_server" before the end of the line if this is the default server/role listen nginxProxy.subdomain.example.com:80; # Set name of the virtual server server_name subdomain.example.com *.subdomain.example.com www.subdomain.example.*; # Address of target/upstream VM/server that hosts the actual service. set $target http://web.subdomain.example.com:8080/404/error.html; # Location configuration location / { # resolver directive needed here if using variables with server names for proxy_pass directive; as nginx doesn't like calling the unix resolver after configuration. resolver 192.168.1.210; proxy_pass $target; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_http_version 1.1; proxy_set_header Connection ""; proxy_buffering off; client_max_body_size 0; proxy_read_timeout 36000s; proxy_redirect off; } }
那么我在这里错过了什么？ 这不是预期的行为，对吧？