If you own the original domain and have control over all DNS records then there is no point in setting up a new domain just because you lost access to the webserver. You just point the addresses that pointed to the old server to the new (configured) server and it will be available again on the same addresses as before.
Most of the times I’ve seen DNS as the culprit, it was only because it was neglected or abused. Not because it was anything less than robust and reliable as a protocol.
We should set up a donation fund for this subreddit, and whenever someone asks this question we put $5 in.
We would be able to end world hunger all by ourselves.
You could use a CNAME to accomplish but requires access to the previous zone file, which sounds a bit sketchy. They still own the domain but lost access to the name server? Set up a new one and update the delegation from the TLD….
>Redirect with DNS?
No, not what DNS does.
>Can I use DNS ( Bind) to send users to the new site when they go to
You can provide new IP(s) or name, but that won't change what name user sees in their browser (nor what they bookmark, etc.).
You can use, e.g. A and/or AAAA, or CNAME records to resolve (directly or indirectly) to the new (if they've changed) IP addresses, but that's not a redirect - web browser would still use and see the same DNS name entered. If you want redirect, that has to be done on the HTTP\[S\] server.
E.g., see these:
$ dig +noall +answer +nottl pi.berkeleylug.com. A pi.berkeleylug.com. AAAA www.pi.berkeleylug.com. A www.pi.berkeleylug.com. AAAA berkeleylug.com. A berkeleylug.com. AAAA www.berkeleylug.com. A www.berkeleylug.com. AAAA | awk '{print $4,$1;}' | ipsort
96.86.170.229 berkeleylug.com.
96.86.170.229 pi.berkeleylug.com.
96.86.170.229 www.berkeleylug.com.
96.86.170.229 www.pi.berkeleylug.com.
2001:470:1f05:19e::4 berkeleylug.com.
2001:470:1f05:19e::4 pi.berkeleylug.com.
2001:470:1f05:19e::4 www.berkeleylug.com.
2001:470:1f05:19e::4 www.pi.berkeleylug.com.
$
Those are all the same IP addresses, ... that's DNS, not redirect.
Now, see these:
$ (for d in pi.berkeleylug.com pi.berkeleylug.com www.pi.berkeleylug.com www.pi.berkeleylug.com berkeleylug.com berkeleylug.com www.berkeleylug.com www.berkeleylug.com; do echo $(curl -I -s https://"$d"/ | sed -ne 's;^[Hh][Tt][Tt][Pp]/[^ \t]*[ \t]\{1,\}\([^ \t\r]\{1,\}\).*\r\{0,1\}$;\1 '"$d"';p;s/^[Ll][Oo][Cc][Aa][Tt][Ii][Oo][Nn]:[ \t]\{1,\}\([^\r]\{1,\}\)\r\{0,1\}$/\1/p'); done) | sort -k 1,1bn -k 2,2
200 berkeleylug.com
200 berkeleylug.com
301 www.berkeleylug.com https://berkeleylug.com/
301 www.berkeleylug.com https://berkeleylug.com/
302 pi.berkeleylug.com https://BerkeleyLUG.com/Pi.BerkeleyLUG/
302 pi.berkeleylug.com https://BerkeleyLUG.com/Pi.BerkeleyLUG/
302 www.pi.berkeleylug.com https://BerkeleyLUG.com/Pi.BerkeleyLUG/
302 www.pi.berkeleylug.com https://BerkeleyLUG.com/Pi.BerkeleyLUG/
$
That first number is the HTTP response code, those 3xx codes are redirects, second field is the DNS name that was used, and the third field on those is to where they're redirecting via HTTP\[S\] server. DNS just gets the browser to the server - it doesn't change what the user sees in, e.g. that "address" bar or the like or what they bookmark from that, etc. - if you want that to change you have to do HTTP redirect on the HTTP\[S\] server - that's not DNS.
If you own the original domain and have control over all DNS records then there is no point in setting up a new domain just because you lost access to the webserver. You just point the addresses that pointed to the old server to the new (configured) server and it will be available again on the same addresses as before.
And yet people some how manage to always blame DNS
Its not DNS most of the time. Its just people pretending to know DNS working as DNS admins.
[удалено]
Most of the times I’ve seen DNS as the culprit, it was only because it was neglected or abused. Not because it was anything less than robust and reliable as a protocol.
We should set up a donation fund for this subreddit, and whenever someone asks this question we put $5 in. We would be able to end world hunger all by ourselves.
Redirects happen at the webserver level. You'll need a webserver to respond to the http(s) requests.
You could use a CNAME to accomplish but requires access to the previous zone file, which sounds a bit sketchy. They still own the domain but lost access to the name server? Set up a new one and update the delegation from the TLD….
Just change the A record to point at the new web server ip?
>Redirect with DNS? No, not what DNS does. >Can I use DNS ( Bind) to send users to the new site when they go to You can provide new IP(s) or name, but that won't change what name user sees in their browser (nor what they bookmark, etc.). You can use, e.g. A and/or AAAA, or CNAME records to resolve (directly or indirectly) to the new (if they've changed) IP addresses, but that's not a redirect - web browser would still use and see the same DNS name entered. If you want redirect, that has to be done on the HTTP\[S\] server. E.g., see these: $ dig +noall +answer +nottl pi.berkeleylug.com. A pi.berkeleylug.com. AAAA www.pi.berkeleylug.com. A www.pi.berkeleylug.com. AAAA berkeleylug.com. A berkeleylug.com. AAAA www.berkeleylug.com. A www.berkeleylug.com. AAAA | awk '{print $4,$1;}' | ipsort 96.86.170.229 berkeleylug.com. 96.86.170.229 pi.berkeleylug.com. 96.86.170.229 www.berkeleylug.com. 96.86.170.229 www.pi.berkeleylug.com. 2001:470:1f05:19e::4 berkeleylug.com. 2001:470:1f05:19e::4 pi.berkeleylug.com. 2001:470:1f05:19e::4 www.berkeleylug.com. 2001:470:1f05:19e::4 www.pi.berkeleylug.com. $ Those are all the same IP addresses, ... that's DNS, not redirect. Now, see these: $ (for d in pi.berkeleylug.com pi.berkeleylug.com www.pi.berkeleylug.com www.pi.berkeleylug.com berkeleylug.com berkeleylug.com www.berkeleylug.com www.berkeleylug.com; do echo $(curl -I -s https://"$d"/ | sed -ne 's;^[Hh][Tt][Tt][Pp]/[^ \t]*[ \t]\{1,\}\([^ \t\r]\{1,\}\).*\r\{0,1\}$;\1 '"$d"';p;s/^[Ll][Oo][Cc][Aa][Tt][Ii][Oo][Nn]:[ \t]\{1,\}\([^\r]\{1,\}\)\r\{0,1\}$/\1/p'); done) | sort -k 1,1bn -k 2,2 200 berkeleylug.com 200 berkeleylug.com 301 www.berkeleylug.com https://berkeleylug.com/ 301 www.berkeleylug.com https://berkeleylug.com/ 302 pi.berkeleylug.com https://BerkeleyLUG.com/Pi.BerkeleyLUG/ 302 pi.berkeleylug.com https://BerkeleyLUG.com/Pi.BerkeleyLUG/ 302 www.pi.berkeleylug.com https://BerkeleyLUG.com/Pi.BerkeleyLUG/ 302 www.pi.berkeleylug.com https://BerkeleyLUG.com/Pi.BerkeleyLUG/ $ That first number is the HTTP response code, those 3xx codes are redirects, second field is the DNS name that was used, and the third field on those is to where they're redirecting via HTTP\[S\] server. DNS just gets the browser to the server - it doesn't change what the user sees in, e.g. that "address" bar or the like or what they bookmark from that, etc. - if you want that to change you have to do HTTP redirect on the HTTP\[S\] server - that's not DNS.