DNS does not resolve correctly on virgin media

[Sorinc03]

Hi All,

I am an engineer on the Chase UK product at JPMorgan and we’re seeing an issue with a domain we use: link.go.chase. This resolves correctly on other ISPs. And if you open link.go.chase/emNK, it should redirect you to the Apple App Store or Google Play Store (if on Android).

On Virgin Media, the resolution is:

cache1.service.virginmedia.net 194.168.4.100

On any other network, the resolution is:

ns1.jpmchase.net 169.88.8.8 - this also allows the cname to resolve correctly and thus the link to work without any SSL certificate issues.

Please advise how to proceed.

[Roger_Gooner]

The DNS resolution is fine.

This is using VM's DNS server.

C:\>nslookup link.go.chase 194.168.4.100
Server:  cache1.service.virginmedia.net
Address:  194.168.4.100

Non-authoritative answer:
Name:    chase-uk.customlinks.appsflyer.com
Addresses:  52.211.34.199
          34.241.91.143
          34.249.210.9
Aliases:  link.go.chase

This is using Google's DNS server.

C:\>nslookup link.go.chase 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    chase-uk.customlinks.appsflyer.com
Addresses:  52.211.34.199
          34.249.210.9
          34.241.91.143
Aliases:  link.go.chase

[Sorinc03]

Spoiler

Something I forgot to mention is that for some reason, it’s not happening to everyone. I’m on Virgin Media and I get the same thing as you. But another one of my coworkers is not getting the correct resolution. Unclear if they have something like websafe turned on, but the issue does appear to be on Virgin Media’s end

[newapollo]

Hi @Sorinc03 

I've moved your posts to the Security Matters Forums.

VM Staff don't tend to read the Natter Forums.

EDIT The link you provided took me to the ios app store. I don't use websafe.

[用心棒]

Unlikely to be a Web Safe or a Virgin Media issue judging from the information provided thus far.

It is unclear why the DNS service for the network is being highlighted as an issue or why the authoritative resolver is referred to. Can you explain some more of what your concerns are here because AFAICS resolvers are correctly resolving the URL; as demonstrated by @Roger_Gooner earlier post?

What does your co-work see when browsing to link.go.chase/emNK and when running the following commands:

nslookup link.go.chase

and

curl -IL link.go.chase/emNK

Post the redacted results here.

-- 
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer and solved, or use  Kudos to say thanks