DNS not updated

[Patosan]

Hello

Domain: tripcomputer.co.uk

I updated the IP address for this domain a few weeks ago to be 82.11.175.22. When I try to access from a remote machine, I sometimes get this IP but sometimes get the previous IP (82.12.233.17). I know it can take a couple of days to update the DNS, but not a few weeks.

wget output on remote PC:

wget http://tripcomputer.co.uk/test.htm
--2024-09-24 04:53:21-- http://tripcomputer.co.uk/test.htm
Resolving tripcomputer.co.uk (tripcomputer.co.uk)... 82.11.175.22
Connecting to tripcomputer.co.uk (tripcomputer.co.uk)|82.11.175.22|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 60 [text/html]
Saving to: ‘test.htm.1’
test.htm.1 100%[===================>] 60 --.-KB/s in 0s
2024-09-24 04:53:21 (7.78 MB/s) - ‘test.htm.1’ saved [60/60]

A couple of minutes later:

wget http://www.tripcomputer.co.uk/test.htm
--2024-09-24 04:55:45-- http://www.tripcomputer.co.uk/test.htm
Resolving www.tripcomputer.co.uk (www.tripcomputer.co.uk)... 82.12.233.17
Connecting to www.tripcomputer.co.uk (www.tripcomputer.co.uk)|82.12.233.17|:80...

 

[sandy]

HI there I am 99% sure this is something happening on your host machine and has zero to do with DNS... but Il just ask out dev crew to be sure.. regards

 

[sandy]

Hi again'
' yes, confirmed, it could well be something you have configured on DNS either on your machine or router, but has zero to do with the domains DNS provider.

 

[Patosan]

Thank you for your reply.

There is nothing in the hosts file on the machine.

I was investigating this because my Let's Encrypt update is failing. Looking at the Let's Encrypt log, it looks like they are also getting the wrong IP address:


{
"identifier": {
"type": "dns",
"value": "www.tripcomputer.co.uk"
},
"status": "invalid",
"expires": "2024-10-01T18:51:07Z",
"challenges": [
{
"type": "http-01"
"url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/407915799526/wNlEfQ",
"status": "invalid",
"validated": "2024-09-24T18:51:11Z",
"error": {
"type": "urn:ietfarams:acme:error:connection",
"detail": "82.12.233.17: Fetching http://www.tripcomputer.co.uk/.well-known/acme-challenge/J8eLxDkvDeS_bGfdJJ7QDuZMh5IMN3qpfZj6VtFBRXo: Timeout during connect (likely firewall problem)",
"status": 400
},
"token": "J8eLxDkvDeS_bGfdJJ7QDuZMh5IMN3qpfZj6VtFBRXo",
"validationRecord": [
{
"url": "http://www.tripcomputer.co.uk/.well-known/acme-challenge/J8eLxDkvDeS_bGfdJJ7QDuZMh5IMN3qpfZj6VtFBRXo",
"hostname": "www.tripcomputer.co.uk",
"port": "80",
"addressesResolved": [
"82.12.233.17"
],
"addressUsed": "82.12.233.17"
}
]
}
]
}

 

[Patosan]

The nameservers for the domain were:
ns1.zoneedit.com
ns2.zoneedit.com

I have just changed them to:
dns1.zoneedit.com
dns2.zoneedit.com
dns3.zoneedit.com

To see if that helps

 

[sandy]

hi again
looks good at present:
wget http://tripcomputer.co.uk
--2024-09-25 00:51:08-- http://tripcomputer.co.uk/
Resolving tripcomputer.co.uk (tripcomputer.co.uk)... 82.11.175.22
Connecting to tripcomputer.co.uk (tripcomputer.co.uk)|82.11.175.22|:80... connected.

 

[Patosan]

Still not working for me:

wget http://www.tripcomputer.co.uk/test.htm
--2024-09-25 05:09:02-- http://www.tripcomputer.co.uk/test.htm
Resolving www.tripcomputer.co.uk (www.tripcomputer.co.uk)... 82.12.233.17
Connecting to www.tripcomputer.co.uk (www.tripcomputer.co.uk)|82.12.233.17|:80...

Let's Encrypt also still trying to use the old IP address

I tried a few dns checking websites and they all returned the new IP address.

I did find this site that reports that tripcomputer.co.uk is down:

Free Website Down Checker | Is Site Down For Everyone ☑

Our tool helps you find whether the website you are trying to browse is down or not. Check if the website is down just for you or everyone around the globe.

sitechecker.pro

Unfortunately it doesn't tell you which IP it is trying. It reports my other sites as being live.

 

[sandy]

i do see it resolving at present:
"

Welcome to Trip Computer"​

regards

 

[Patosan]

Yes the DNS lookup returns the correct IP address for most computers. It returns the old IP address for whatever server the Let's Encrypt update uses. I think it must also be returning the old IP address for the server used by the Website Down Checker as it always says the site is down, but says my other sites are up.
It works on all the computers I have access to except for one remote server that sometimes gets the new IP address and sometimes gets the old one.

 

[sandy]

perhaps for those machines, can you flush the DNS cache...

 

[Patosan]

I could do that for my remote server, but I don't have access to the Let's Encrypt server or whatever is used by the website checker site.

Not sure if you did anything, but the automatic certificate update by Let's Encrypt worked on 26 September, which was the main thing I was worried about.

 

[sandy]

we did nothing on our side... most likely some type of caching issue...