GoDaddy redirect to IP

Help
21

This is screenshot of my GoDaddy DNS management page.
As you can see the records for subdomains, blog.antonio-art.es for example are not editable.
There is no record for web.antonio-art.es as I deleted the forwarding.

DNSrec
DNSrec1123×794 40.2 KB

1 Like
22

Looks pretty normal. I usually use CNAMEs, but A records are fine. Unfortunately you must wait for GoDaddy to clear the forward ip 184.168.131.241. All those records will likely switch to 34.102.136.180 (parked) within an hour. You may need to log out and log back in to see the change. I use GoDaddy forwarding allot.

For example, my openacme.com forwards to openacme.org.

23

Your obras subdomain is correct and it’s possible to ping that ip address.

Create such an A record with your ip 45.76.32.225

PS: Ah, may not work. That’s photoalbum.godaddy.com.

24

He needs to be careful. If he creates the A record before the parking script completes, GoDaddy gets really confused.

25

Yes @JuergenAuer obras is a GoDaddy service.

Once “the parking script completes” I do not know how to create a record for web.antonio-art.es without using GoDaddy interface.

26

You don’t need a forward then. @JuergenAuer’s direction of adding your A record is perfect at that point. You can modify any of them once they’re parked.

1 Like
27

You have to use the GoDaddy interface.

There should be a new button to create a new entry.

1 Like
28

@JuergenAuer

Do you have me on ignore? I just want to know.

@antonio.filigranas

He may not be able to see my posts. :worried:

1 Like
29

Is two hours waiting time also common with this issue @griffin?

Strengthens my opinion about GoDaddy :wink:

2 Likes
30

Now your configuration is correct:

Host Type IP-Address is auth. ∑ Queries ∑ Timeout
web.antonio-art.es A 45.76.32.225 Amsterdam/North Holland/Netherlands (NL) - Choopa Hostname: 45.76.32.225.vultr.com yes 1 0
AAAA yes
www.web.antonio-art.es Name Error yes 1 0

And there is a correct nginx - answer.

1 Like
31

I’ve seen it take 20 hours. :pensive:

I think @JuergenAuer has me ignored. :worried:

It looks like @antonio.filigranas added an A record though:
web.antonio-art.es. 3599 IN A 45.76.32.225

Should be OK soon. I’ve only had issues when I’ve overlapped A records and CNAME records that have forwarding attached.

The starfield certificate is still being served for https for web.antonio-art.es, which is the concern. Not out of the woods yet.

1 Like
32

I added an A record.
I do not know if I waited long enough.
I do not know if I should put web or web.antonio-art.es as the server. (The other subdomains show only the subdomain, so I did that too).

1 Like
33

Seems to be working!

web.antonio-art.es. 3600 IN A 45.76.32.225

2 Likes
34

Just the subdomain only.

2 Likes
35

Your configuration is now correct, see the last check result

36

Try this though:

https://web.antonio-art.es

Could be my cache.

38

Connection refused is to be expected if @antonio.filigranas only runs a server on port 8108.

@antonio.filigranas For issuing a Let's Encrypt certificate, you'll need to have a HTTP virtualhost running on port 80. You could use the internal temporary webserver of certbot for that with the --standalone plugin, if you don't want your own webserver running on port 80.

2 Likes
39

I’m still getting the GoDaddy starfield cert. That’s probably my cache though.

edit:

cache cleared. https now unreachable as expected for me.

port 80 serving default nginx. port 8108 correct.

1 Like
40

Thank you all!
Now I have the default answer from nginx on web.antonio-art.es

I could not create a record for a specific port, so I need to rethink about port 80 (I changed to 8108 because the high number of robot accesses on port 80).

Then I will try certbot again. I let it here by now. Soon midnight here.
Thanks again.

2 Likes
41

As written: There is already a correct nginx answer:

Domainname Http-Status redirect Sec. G
• http://web.antonio-art.es/ 45.76.32.225 GZip used - 384 / 612 - 37,25 % 200 Html is minified: 129,94 % 0.033 H
small visible content (num chars: 273)
Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org . Commercial support is available at nginx.com . Thank you for using nginx.
• https://web.antonio-art.es/ 45.76.32.225 -2 1.047 V
ConnectFailure - Unable to connect to the remote server
• http://web.antonio-art.es/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.76.32.225 GZip used - 125 / 162 - 22,84 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0 404 Html is minified: 109,46 % 0.033 A
Not Found
Visible Content: 404 Not Found nginx

https doesn't work, that's expected.

But /.well-known/acme-challenge/random-filename works.

So

certbot --nginx

should be the next step.

PS: Reopened 2020-10-20, so it's possible to add a solution.

3 Likes