thebeltzfamily's profile

New Poster

 • 

4 Messages

Tue, Jun 2, 2020 10:00 AM

Comcast DNS servers 75.75.75.75 and 75.75.76.76 can not resolve dv.teleperformanceusa.com

The above Comcast DNS servers work just fine to resolve anything else, but they do not seem to be able to resolve "dv.teleperformanceusa.com".   it should resolve to 208.80.225.197

 

They should be doing a recursive lookup against nin-exdns-01.teleperformanceusa.com (216.152.208.183) or nin-exdns-02.teleperformanceusa.com (216.152.208.137)

 

This is causing issues for me to not be able connect to work unless I use alternate DNS providers.

Responses

New Poster

 • 

4 Messages

1 y ago

That is very strange.   Very definately does not resolve for me.

 

> server 75.75.75.75
Default Server: cdns01.comcast.net
Address: 75.75.75.75

> dv.teleperformanceusa.com
Server: cdns01.comcast.net
Address: 75.75.75.75

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to cdns01.comcast.net timed-out
>

BruceW

Gold Problem Solver

 • 

22.3K Messages

1 y ago


@thebeltzfamily wrote: ... "dv.teleperformanceusa.com".   it should resolve to 208.80.225.197 ...

In South-Central PA, 75.75.75.75 seems working correctly, but 75.75.76.76 does not:

 

C>nslookup dv.teleperformanceusa.com  75.75.75.75
Server:  cdns01.comcast.net
Address:  75.75.75.75
Non-authoritative answer:
Name:    dv.vdiext.teleperformanceusa.com
Address:  208.80.225.197
Aliases:  dv.teleperformanceusa.com

C>nslookup dv.teleperformanceusa.com  75.75.76.76
Server:  cdns02.comcast.net
Address:  75.75.76.76
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to cdns02.comcast.net timed-out

C>tracert -4 75.75.75.75
Tracing route to cdns01.comcast.net [75.75.75.75] over a maximum of 30 hops:
  1    40 ms    10 ms     9 ms  router1 [192.168.1.1]
  2    29 ms    20 ms    17 ms  96.120.9.181
  3    27 ms    33 ms    18 ms  96.108.119.45
  4     *       23 ms    22 ms  96.110.25.9
  5    41 ms    34 ms    41 ms  be-33-ar01.pittsburgh.pa.pitt.comcast.net [69.139.168.185]
  6    35 ms    51 ms    30 ms  162.151.21.114
  7    39 ms     *       31 ms  dns-sw02.summitpark.pa.pitt.comcast.net [69.139.167.234]
  8    42 ms    43 ms    43 ms  cdns01.comcast.net [75.75.75.75]
Trace complete.

C>tracert -4 75.75.76.76
Tracing route to cdns02.comcast.net [75.75.76.76] over a maximum of 30 hops:
  1    21 ms    10 ms    10 ms  router1 [192.168.1.1]
  2    28 ms    30 ms    20 ms  96.120.9.181
  3    36 ms    28 ms    29 ms  96.108.119.45
  4    30 ms    26 ms    20 ms  96.110.24.214
  5    29 ms    19 ms    19 ms  96.110.25.65
  6    36 ms    28 ms    37 ms  be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
  7    40 ms    30 ms    29 ms  be-31641-cs04.pittsburgh.pa.ibone.comcast.net [96.110.42.173]
  8     *       28 ms    28 ms  be-1411-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.142]
  9    43 ms    33 ms    33 ms  be-302-cr12.ashburn.va.ibone.comcast.net [96.110.32.101]
 10    33 ms    35 ms    35 ms  be-1412-cs04.ashburn.va.ibone.comcast.net [96.110.32.213]
 11    43 ms    47 ms    43 ms  be-1402-cr02.ashburn.va.ibone.comcast.net [96.110.32.182]
 12     *       35 ms    32 ms  ae-0-0-ar02-d.ashburn.va.ndcasbn.comcast.net [68.86.90.250]
 13    52 ms    43 ms    44 ms  et-8-2-as04-d.ashburn.va.ndcasbn.comcast.net [162.151.67.170]
 14    34 ms    35 ms    34 ms  eth-2-4-ss01a-d.ashburn.va.ndcasbn.comcast.net [162.151.66.146]
 15    64 ms     *       44 ms  dns-sw01.ashburn.va.ndcasbn.comcast.net [162.151.198.50]
 16    44 ms    37 ms    39 ms  cdns02.comcast.net [75.75.76.76]
Trace complete.
EG

Expert

 • 

86.7K Messages

1 y ago

Hmmmm..... This is not a solution, just a FWIW. It resolves to the first IP address here in northern N.J. using the 75.xxx DNS;

 

Tracing route to dv.vdiext.teleperformanceusa.com [208.80.225.197]
over a maximum of 30 hops:

 

1 2 ms 3 ms 2 ms 192.168.1.1
2 10 ms 12 ms 19 ms 96.120.73.93
3 15 ms 15 ms 11 ms 68.85.119.97
4 11 ms 11 ms 11 ms 96.110.60.101
5 12 ms 12 ms 12 ms 96.108.142.253
6 16 ms 17 ms 29 ms be-98-ar03.plainfield.nj.panjde.comcast.net [68.85.35.37]
7 14 ms 16 ms 15 ms be-31123-cs02.newark.nj.ibone.comcast.net [96.110.42.37]
8 23 ms 16 ms 15 ms be-1201-cr01.newark.nj.ibone.comcast.net [96.110.36.86]
9 32 ms 20 ms 13 ms be-10203-cr02.newyork.ny.ibone.comcast.net [68.86.85.186]
10 15 ms 14 ms 19 ms be-10368-pe01.111eighthave.ny.ibone.comcast.net [68.86.84.218]
11 * * * Request timed out.
12 * * * Request timed out.
13 19 ms 16 ms 17 ms lsv2-agw1.inet.qwest.net [63.235.42.101]
14 65 ms 65 ms 67 ms slc2-edge-05.inet.qwest.net [67.14.134.70]
15 67 ms 67 ms 66 ms 209.180.86.90
16 67 ms 66 ms 67 ms 208.80.225.197

 

Trace complete.

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!tick

New Poster

 • 

4 Messages

1 y ago

I work for Teleperformance, we don't have this issue with any other ISP with our home agents but we have it consistently with Comcast's DNS servers.  

 

I have Comcast as a home internet provider and have the issue as well.    

andyross

Silver Problem Solver

 • 

6.8K Messages

1 y ago

Works here in the Chicago area. If you do a tracert to the DNS servers, the next-to-last hop will give a clue as to where it actually located. The two addresses are generic and will be routed to the closest DNS servers.

New to the Community?

Start Here