Forum Discussion

gilgongo's avatar
gilgongo
Dialled in
19 days ago

Dynamic DNS has suddenly stopped working?

For several years, I've had a box on my LAN that does a regular query to find out what our public IP address is, like this (I have a couple of things that depend on this info):

dig +short myip.opendns.com @resolver1.opendns.com

Last week, it started returning an IP that resolves to "connected-by.global-layer.com" which is a completely different IP to the one my router is using (and not the one that, for example https://whatismyipaddress.com/ reports).

Does anyone know what's happening? Have Virgin changed something?

 

5 Replies

Sort By
  • gilgongo's avatar
    gilgongo
    Dialled in
    19 days ago

    As a workaround, I think I can change the script to ssh into an external machine and doing a "who" to return my actual IP (not tried it yet). But why do I need to do this when it was working fine before? Maybe I missed some announcement or other?

  • Client62's avatar
    Client62
    Alessandro Volta
    19 days ago

    Using dig +short myip.opendns.com @resolver1.opendns.com
    in Ubuntu returns the correct Public IP for our VM connection.

    • Akua_A's avatar
      Akua_A
      Icon for Forum Team rankForum Team
      16 days ago

      Hi gilgongo 

      Welcome back to our forums, and sorry to hear you were having issues with your Dynamic DNS. We are, however, glad that Client62 was able to assist with this. Please do not hesitate to contact us if you need any further help, and we will be happy to assist. 

      Thanks,

  • gilgongo's avatar
    gilgongo
    Dialled in
    19 days ago

    Weird. I get 213.152.162.5 - which isn't even a Virgin IP.  I have no idea why this is.

    inetnum:        213.152.162.0 - 213.152.162.63
netname:        GLOBALLAYER
descr:          Global Layer B.V.
country:        NL
descr:          ****************************************************
descr:          Alblasserdam datacenter - The Netherlands
descr:          IP space for European Unmanaged Dedicated Servers
descr:          For abuse, please e-mail only: abuse@global-layer.com
descr:          Abuse messages will be handled within 24 hours time
descr:          ****************************************************
admin-c:        GL6540-RIPE
tech-c:         GL6540-RIPE
status:         ASSIGNED PA
remarks:        INFRA-AW
mnt-by:         GLOBALLAYER
created:        2015-06-20T21:22:22Z
last-modified:  2015-06-20T21:22:22Z
source:         RIPE # Filtered

person:         Global Layer
address:        Postbus 190
address:        2950AD Alblasserdam
address:        Netherlands
phone:          +31 78 20 20 228
nic-hdl:        GL6540-RIPE
mnt-by:         GLOBALLAYER
created:        2011-08-04T20:36:25Z
last-modified:  2024-06-27T09:18:45Z
source:         RIPE # Filtered

% Information related to '213.152.162.0/24AS49453'

route:          213.152.162.0/24
descr:          Global Layer network
origin:         AS49453
mnt-by:         GLOBALLAYER
created:        2016-08-11T11:27:53Z
last-modified:  2016-08-11T11:27:53Z
source:         RIPE

     

    • gilgongo's avatar
      gilgongo
      Dialled in
      19 days ago

      Oh OK - as part of another thing, I was using a proxy config with iptables to route stuff over an interface that was also being tunnelled via Global Layer to the outside world. So that was causing the issue and I'd not put 2+2 together.

      Panic over, but thanks @client62 for your help!