DNS Problem

All other technical assistance queries (General technical issues, IPv6. P2P, News groups, etc)
stu
Posts: 27
Joined: Thu Dec 07, 2006 7:31 pm
Location: Wollongong

DNS Problem

Post by stu » Tue Jul 01, 2008 10:26 pm

Dear exetel

i have found a problem with your dns servers or at least 1 of them
i have been trying to download updates for my vmware ESX server using vmware update manager.
The address this service uses is (download3.vmware.edgesuite.net)
i checked my firewall logs as the downloads were not working and found the service was connecting to the wrong address
it keep trying to connect to 220.233.2.168 or 220.233.2.169
in my current config i run a local dns server for my internal domain and use your dns servers as fowarders (for all other domains)
this has been fine for years ......

Anyway i have now switched to a telstra fowarder tonight and now my esx updates are downloading fine ...because im getting correct resolution
for the following address (download3.vmware.edgesuite.net)
see below the first result show my local dns answering with the correct address
and the second test show me querying your dns server and getting false responses

Your comments are welome
Regards
Stu

********* my local dns server *************************
Default Server: mainserver.hq.illawarrawifi.com
Address: 10.1.1.10

> download3.vmware.edgesuite.net
Server: mainserver.hq.illawarrawifi.com
Address: 10.1.1.10

Non-authoritative answer:
Name: a398.d.akamai.net
Addresses: 72.247.247.168, 72.247.247.177
Aliases: download3.vmware.edgesuite.net
*********************************************************
*********** now test the same dns name against the exetel dns server ************
> server 220.233.0.3
Default Server: mx2.exetel.com.au
Address: 220.233.0.3

> download3.vmware.edgesuite.net
Server: mx2.exetel.com.au
Address: 220.233.0.3

Non-authoritative answer:
Name: a398.d.akamai.net
Addresses: 220.233.2.168, 220.233.2.169
Aliases: download3.vmware.edgesuite.net
*****************************************************************************************
>

James D

Re: DNS Problem

Post by James D » Tue Jul 01, 2008 11:36 pm

I have asked one of the sysadmins to have a look and reply

stu
Posts: 27
Joined: Thu Dec 07, 2006 7:31 pm
Location: Wollongong

Re: DNS Problem

Post by stu » Sat Jul 05, 2008 8:07 pm

i just checked again tonight and this problem has not been resolved. ??

ymo
Posts: 295
Joined: Sat Sep 10, 2005 4:36 pm
Location: Wollongong NSW

Re: DNS Problem

Post by ymo » Sat Jul 05, 2008 9:57 pm

It makes sense that resolving that address on your Exetel service returns a different answer to that from other DNS servers. Exetel has its own link to the Sydney Akamai cache which might explain why you get Exetel addresses (220.233.x.y). There could however be a problem with this particular example Akamai addressing...

Here is what I get from work (Wollongomg Uni):

Non-authoritative answer:
download3.vmware.edgesuite.net canonical name = a398.d.akamai.net.
Name: a398.d.akamai.net
Address: 202.158.212.144 (cache144.akamai.aarnet.net.au)
Name: a398.d.akamai.net
Address: 202.158.212.138 (cache138.akamai.aarnet.net.au)

and from home I get the same as you:

Non-authoritative answer:
Name: a398.d.akamai.net
Addresses: 220.233.2.168, 220.233.2.169
Aliases: download3.vmware.edgesuite.net

Notice my work DNS lookups differ from your working example.

P.S. I checked two other sites that use Akamai - http://www.microsoft.com and http://www.emusic.com. Both work from home but have different Akamai domains:

microsoft -> lb1.www.ms.akadns.net
emusic -> e607.r.akamaiedge.net

stu
Posts: 27
Joined: Thu Dec 07, 2006 7:31 pm
Location: Wollongong

Re: DNS Problem

Post by stu » Sat Jul 05, 2008 10:24 pm

One large problem with your theory 220.233.2.168, 220.233.2.169 are both from the exetel customer access block
ie: these addresses should be issued to extel client to access the internet with.

stu
Posts: 27
Joined: Thu Dec 07, 2006 7:31 pm
Location: Wollongong

Re: DNS Problem

Post by stu » Wed Jul 09, 2008 11:48 am

this problem has still not been resolved .... i just checked again using a telstra dns server vs the exetel dns server for the
host download3.vmware.edgesuite.net

results

****telstra****

C:\Program Files\Support Tools>nslookup
Default Server: lon-resolver.telstra.net
Address: 203.50.2.71

> download3.vmware.edgesuite.net
Server: lon-resolver.telstra.net
Address: 203.50.2.71

Non-authoritative answer:
Name: a398.d.akamai.net
Addresses: 72.247.247.177, 72.247.247.168
Aliases: download3.vmware.edgesuite.net

>

***** exetel ******


C:\Program Files\Support Tools>nslookup
Default Server: lon-resolver.telstra.net
Address: 203.50.2.71

> server 220.233.0.3
Default Server: mx2.exetel.com.au
Address: 220.233.0.3

> download3.vmware.edgesuite.net
Server: mx2.exetel.com.au
Address: 220.233.0.3

DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: a398.d.akamai.net
Addresses: 220.233.2.169, 220.233.2.168
Aliases: download3.vmware.edgesuite.net

>

ymo
Posts: 295
Joined: Sat Sep 10, 2005 4:36 pm
Location: Wollongong NSW

Re: DNS Problem

Post by ymo » Wed Jul 09, 2008 3:19 pm

stu wrote:One large problem with your theory 220.233.2.168, 220.233.2.169 are both from the exetel customer access block
ie: these addresses should be issued to extel client to access the internet with.
Not all 220.233.x.y numbers are customer numbers. Look at http://www.exetel.com.au (220.233.0.9) for an example.

Have you created a fault ticket at https://helpdesk.exetel.com.au/ ?

stu
Posts: 27
Joined: Thu Dec 07, 2006 7:31 pm
Location: Wollongong

Re: DNS Problem

Post by stu » Wed Jul 09, 2008 4:21 pm

your not adding any value to this issue as you are not one of the exetel sys admins.

austdata
Posts: 629
Joined: Wed Apr 25, 2007 12:38 am
Location: Melbourne

Re: DNS Problem

Post by austdata » Wed Jul 09, 2008 4:36 pm

stu wrote:your not adding any value to this issue as you are not one of the exetel sys admins.
That he's not an Exetel System Administrator doesn't diminish his input if he is right.

Your curt attitude however, is another matter altogether.

Mike
The views I present here are not necessarily those from my brain.
Exetel's support number outside Sydney: 1300 788 141 NOTE: I do not work for Exetel.

SysAdmin

Re: DNS Problem

Post by SysAdmin » Wed Jul 09, 2008 4:48 pm

stu wrote:your not adding any value to this issue as you are not one of the exetel sys admins.
Well allow me to nail this one shut, then. :)

220.233.0.0/16 is mostly, not wholly a customer ip block.

220.233.2.168 and .169 are both Akamai servers and, as such, not something we have control over with respect to updates. That said I have forwarded this thread over to the relevant parties for forwarding to Akamai.

Andrew

edwar64896
Posts: 13
Joined: Mon Jan 30, 2006 7:25 pm

Re: DNS Problem

Post by edwar64896 » Tue Aug 12, 2008 4:06 pm

HI. I am experiencing the same issue.

maps.google.com and www.abc.net.au resolve to 220.233.3.168 and .169

both IP addresses are, as of this moment, unpingable from my account (220.233.83.72)

If anyone is able to assist with this, it would brighten my day up.

cheers,

Mark.

SysAdmin

Re: DNS Problem

Post by SysAdmin » Tue Aug 12, 2008 4:11 pm

edwar64896 wrote:HI. I am experiencing the same issue.
You're not, actually. :)
maps.google.com and http://www.abc.net.au resolve to 220.233.3.168 and .169

both IP addresses are, as of this moment, unpingable from my account (220.233.83.72)

If anyone is able to assist with this, it would brighten my day up.
I'm connected via the same router as you at the moment and I can get to both sites. I suspect that this may be an issue at your end but just in case, can you do a traceroute (tracert from a windows command prompt) to those sites and see how far you get?

Andrew

edwar64896
Posts: 13
Joined: Mon Jan 30, 2006 7:25 pm

Re: DNS Problem

Post by edwar64896 » Tue Aug 12, 2008 4:22 pm

[root@phones ~]# traceroute www.abc.net.au
traceroute to www.abc.net.au (220.233.2.169), 30 hops max, 40 byte packets
1 router.greenside.local (172.23.1.1) 1.761 ms 1.704 ms 3.812 ms
2 * * *
3 254.0.233.220.exetel.com.au (220.233.0.254) 45.958 ms 47.383 ms 48.584 ms
4 234.0.233.220.exetel.com.au (220.233.0.234) 50.327 ms 51.976 ms 53.472 ms
5 2.4.96.58.exetel.com.au (58.96.4.2) 55.606 ms 57.208 ms 58.515 ms
6 57.1.96.58.exetel.com.au (58.96.1.57) 60.749 ms 39.947 ms 41.561 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


I'm on 0394352130 if you think a Vox discussion might be of more assistance...

cheers,

Mark.

SysAdmin

Re: DNS Problem

Post by SysAdmin » Tue Aug 12, 2008 4:31 pm

edwar64896 wrote:[root@phones ~]# traceroute http://www.abc.net.au
traceroute to http://www.abc.net.au (220.233.2.169), 30 hops max, 40 byte packets
1 router.greenside.local (172.23.1.1) 1.761 ms 1.704 ms 3.812 ms
Thanks. I've asked a network engineer to look into this for you.

Andrew

edwar64896
Posts: 13
Joined: Mon Jan 30, 2006 7:25 pm

Re: DNS Problem

Post by edwar64896 » Tue Aug 12, 2008 4:39 pm

appreciate it.

thanks,

Mark.

Post Reply