Menu
Reply
  • 38
  • 1
  • 2
tfboy
On our wavelength
320 Views
Message 1 of 6
Flag for a moderator

DNS update issue - is it VM?

I'm trying to get to the bottom of an apparently really slow DNS update.

I run my own Linode and yesterday, I migrated all my services to a new machine.

Last night, I updated the DNS entries to point to the new IP. Most of the domain names have updated, but a few still appear with their old IPs.

I've rebooted my PC, flushed the DNS cache, rebooted my router (an old one running DD-WRT firmware).

From what I can tell, it appears VM uses Google's 8.8.8.8 DNS server.

doing an nslookup without specifying any particular DNS (so it default to my router's local IP, 192.168.0.254), I get the old IP - ************. If I use the command line on my router and do a ping from there, same thing, the old IP.

If I use nslookup on my PC and specify 8.8.8.8 as the DNS, it reports the correct new IP (139.162.198.198).

C:\Users\Xavier>nslookup
Default Server:  bx-router
Address:  192.168.0.254

> xavelec.co.uk
Server:  bx-router
Address:  192.168.0.254

Non-authoritative answer:
Name:    xavelec.co.uk
Addresses:  2a01:7e00::f03c:91ff:fee5:c451
          88.80.187.216

>
>
> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> xavelec.co.uk
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    xavelec.co.uk
Addresses:  2a01:7e00::f03c:91ff:fee5:c451
          139.162.198.198

>

I've just noticed that the IPv6 is in fact correct, it's just the IPv4 that's the problem.

I've spoken to other people who aren't on VM to try from their end and it's OK.

So where is this all going wrong?

 

 

 

[MOD EDIT: Personal and private information has been removed from this post. Please do not post personal or private information in your public posts. Please review the Forum Guidelines]

0 Kudos
Reply

Helpful Answers
  • 16.11K
  • 1.34K
  • 3.27K
Superuser
Superuser
587 Views
Message 2 of 6
Flag for a moderator
Helpful Answer

Re: DNS update issue - is it VM?

virginmedia has their own DNS servers 194.168.4.100 194.168.8.100 possible still updating across all servers
----------------------------------------------------------
If someone's helped you out say thanks by clicking on the thumbs up. If someone's solved your problem, why not mark their message as an Accepted Solution
0 Kudos
Reply

All Replies
  • 16.11K
  • 1.34K
  • 3.27K
Superuser
Superuser
588 Views
Message 2 of 6
Flag for a moderator
Helpful Answer

Re: DNS update issue - is it VM?

virginmedia has their own DNS servers 194.168.4.100 194.168.8.100 possible still updating across all servers
----------------------------------------------------------
If someone's helped you out say thanks by clicking on the thumbs up. If someone's solved your problem, why not mark their message as an Accepted Solution
0 Kudos
Reply
  • 21.64K
  • 779
  • 3.1K
Superuser
Superuser
293 Views
Message 3 of 6
Flag for a moderator

Re: DNS update issue - is it VM?

give it 3 days and report back
0 Kudos
Reply
  • 2
  • 0
  • 0
thisisfeeds
Settling in
275 Views
Message 4 of 6
Flag for a moderator

Re: DNS update issue - is it VM?

+1 thanks for sharing!

  

 

0 Kudos
Reply
  • 7.2K
  • 173
  • 420
Forum Team
Forum Team
158 Views
Message 5 of 6
Flag for a moderator

Re: DNS update issue - is it VM?

Hi tfboy,

 

Thanks for getting in touch, how have things been since you posted last. 

 

Fingers crossed things are all updated correctly now. 

 

I have double checked your connection from this side and all seems to be fine from here. 

 

Keep us updated. 

 

Emma


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
  • 38
  • 1
  • 2
tfboy
On our wavelength
138 Views
Message 6 of 6
Flag for a moderator

Re: DNS update issue - is it VM?

Hi Emma,

It seems to have settled down now and is as expected. Not sure exactly what was the cause of the issue, but it's resolved. Thanks.

0 Kudos
Reply