0

NextDNS resolves to Portuguese POP for US user

I have a couple limelight (now edgio) related FQDNs that randomly but quite frequently get resolved to a trans-atlantic pop in Portugal instead of Virginia.  This affects multiple LL domains and it does not matter how I query NextDNS, nor if I use my profile-id or none. For example:

dig @dns.nextdns.io +https g003-vod-us-cmaf-prd-ll.cdn.peacocktv.com

; <<>> DiG 9.18.27 <<>> @dns.nextdns.io +https g003-vod-us-cmaf-prd-ll.cdn.peacocktv.com

; (4 servers found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48149

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

 

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 1232

;; QUESTION SECTION:

;g003-vod-us-cmaf-prd-ll.cdn.peacocktv.com. IN A

 

;; ANSWER SECTION:

g003-vod-us-cmaf-prd-ll.cdn.peacocktv.com. 3302 IN CNAME peacockvod-2.s.llnwi.net.

peacockvod-2.s.llnwi.net. 52 IN A 193.126.117.58

 

;; Query time: 3 msec

;; SERVER: 170.39.224.134#443(dns.nextdns.io) (HTTPS)

;; WHEN: Fri Jun 28 13:58:52 EDT 2024

;; MSG SIZE  rcvd: 124

 

A couple more domains all with the same problem:

g003-vod-us-cmaf-prd-ll.cdn.peacocktv.com
x-live-espn-stgec.uplynk.com
emt.live.ll.ww.aiv-cdn.net
uplynkbu-dis-sport.s.llnwi.net

The problem responses IP addresses always are 193.126.117.50 or 193.126.117.58.

1 reply

null
    • richard.11
    • 2 mths ago
    • Reported - view

    My post has gotten mangled pretty good. Attaching this example image instead. The smart ecs looks close enough but the 193.x IP is far away.

    Other affected names include the following. All of these resolve to something on limelight one way or the other. 

      g003-vod-us-cmaf-prd-ll.cdn.peacocktv.com
      x-live-espn-stgec.uplynk.com
      emt.live.ll.ww.aiv-cdn.net
      uplynkbu-dis-sport.s.llnwi.net

Content aside

  • 2 mths agoLast active
  • 1Replies
  • 36Views
  • 1 Following